Automatic Conversion of Operator Implementations

You can delete operator implementations in old models (see Removing an Individual Operator Implementation) or replace them automatically with implementation casts. Automatic replacing applies to the entire database, not to individual components.

Rules for Automatic Conversion

The following conditions have to be fulfilled for an operator implementation to be converted automatically.

The operator implementation must not contain any other quantization than Auto (addition, subtraction, MIN, MAX and MUX).
Note
This is the only condition which has to be fulfilled for automatic conversion for MIN, MAX and MUX operators.
The operator (+, -, *, /) output must be connected to primitive elements.
It must not be unconnected or connected to a component or operator or hierarchy.
If an implementation cast is connected to the operator (+, -, *, /) output, something other than No implementation has to be selected for this implementation cast in the combo box next to the Use Implementation Type option in the implementation editor.
The operator (*, /) implementation must not contain any special pre-shift.
If the operator is a division operator and the Allow zero in phys. interval option is activated in the operator implementation, the following rules also apply for the denominator input:
1. The denominator input must be connected to primitive elements.
  It must not be unconnected or connected to a component or operator or hierarchy.
2. If an implementation cast is connected to the denominator input, something other than No implementation has to be selected for this implementation cast in the combo box next to the Use Implementation Type option in the implementation editor.

Note
This is the only condition which has to be fulfilled for automatic conversion for MIN, MAX and MUX operators.

If one of these conditions is not fulfilled in any implementation of the component, the relevant operator has to be converted manually.