Disrupting Packages Using Discrete Events

In addition to failing packages by defining failure distributions, you can also fail packages via discrete events.

The field # Packages failed by events accepts discrete change signals (produced, for example, by a Discrete Change element). Discrete change signals have associated with them an instruction, which can be Add or Replace.

Note: If no barriers are specified (i.e., Number ofBarriers is specified as "none"), the # Packages failed by events field is grayed out, since it is not applicable in this case.

This field only accepts discrete change signals which are dimensionless and positive, and have associated with them an Add instruction (Replace instructions are not permitted and will result in a run-time error). Multiple signals can be specified by separating the various entries with a semi-colon.

When a signal is received by the Source, the specified number of packages is instantaneously disrupted (both outer and inner barriers are failed). When packages are failed, the number of unfailed packages is automatically adjusted accordingly (i.e., GoldSim treats this discrete change like another failure mode.)