Contingency Options: Legacy Definitions
See Also
These options are all available on the Contingency Analysis dialog under the Contingency Options tab under the Legacy Definitions grouping. Legacy objects used with contingency analysis are strongly discouraged. They are still supported for older data that has not been converted to newer object structures that are more appropriate for the same modeling purpose, but they may no longer be supported in future versions of Simulator. It is highly encouraged that these legacy objects be converted. Global Actions can be converted to Remedial Actions. Contingency Blocks can be replaced with Injection Groups or Interfaces. The individual topics on these objects describe how to convert them.
A contingency block stores a list of contingency actions and has a name (or label) associated with it. A contingency block can then be called from a contingency record. This allows you to define a block of common actions you wish to have processed during several different contingencies, and then assign the block to each contingency instead of constantly redefining the same actions for each contingency. The Contingency Block Elements contains a combined list of all the contingency block elements for all contingency blocks.
Contingency Block Elements
Contains a combined list of all of the contingency block elements for all Contingency Block records.
Contingency Global Actions
A global action is an action that will automatically be processed as part of EACH contingency unless an Inclusion Filter is specified that allows defining with which contingencies the action will be included. Thus, if you have actions that are to be performed in every single contingency you define, you can insert it once in the global actions list, and Simulator will automatically use the defined action for every contingency it processes.