In contrast to binary incompatibility, the system looks back to the penultimate cycle. In addition, two modifications (intervention1 and intervention2) can be defined whose intervention in the past is to be checked. If both have already intervened, then the incompatible modification must not intervene now. However, Intervention1 must have taken place before Intervention2. If intervention1 = intervention2, this corresponds to a binary incompatibility, but with an extended look back (including the penultimate cycle). A maximum of 40 ternary incompatibilities can be defined.
|
Display |
Identifier |
Values |
Description |
|
Intervention 1 |
Trigger modification 1 |
|
In contrast to the binary incompatibility, here it is looked back to the penultimate cycle. In addition, two modifications (intervention1 and intervention2) can be defined whose intervention in the past is to be checked. If both have already intervened, then the modification incompatible with them must not intervene now. However, intervention1 must have taken place before intervention2. If intervention1 = intervention2, then this corresponds to a binary incompatibility, but with an extended look back (including the penultimate round). |
|
|
|
|
|
|
|
|
List |
All modifications. |
|
Intervention 2 |
Trigger modification 2 |
|
|
|
|
|
|
|
|
|
|
List |
All modifications. |
|
Incompatibility |
Incompatible modification |
|
Modification that is not executed. |
|
|
|
|
|
|
|
|
List |
All modifications. |