Automatic Conversion of Operator Implementation: Results
If the implementation of an operator (except MIN, MAX, MUX) can be converted automatically,
the following happens.
- An implementation cast is created on every connection of the operator output.
- If the operator is a division operator and the Allow zero in phys. interval option is activated in the operator implementation, an implementation cast is created on the connection to the denominator input.
The implementation information of the following element is accepted for every implementation cast at
the output of an implemented operator.
This is not the case for the model type, this is always cont for implementation casts.
The implementation information (apart from the model type) from the previous element is accepted for implementation casts which were added at the denominator input of a division operator.
For implementations of the component in which the operator has no implementation, No implementation is selected for newly created implementation casts. |
The overflow handling is converted according to the following scheme:
| Interval Adaptation settings for implementation cast |
Operator Implementation | Limit to maximum bit length | Reduce Resolution | Keep Resolution |
Reduce resolution | X | X | |
Keep resolution and limit | X | | X |
Keep resolution and don't limit | | n/a | n/a |
Each row shows the settings set for the implementation cast to replace the corresponding setting of the operator implementation.
The operator implementation is removed.
Under certain conditions implementation casts would be created with the same implementation as the element connected to their output. In these cases, no implementation cast is inserted. |
If the implementation of an operator (except MIN, MAX, MUX) cannot be converted automatically,
the following happens.
An implementation cast is created on every connection of the operator output—even with components, operators etc. <No implementation> is selected for these implementation casts in all implementations of the component.
This implementation cast is given the relevant implementation information during manual conversion of the operator implementation.
If this kind of implementation cast already exists on one of these connections, no other implementation cast is added to this connection.
If the Allow zero in phys. interval option is activated in the operator implementation of a division operator, an implementation cast with <No implementation> is created on the connection of the denominator input.
If this kind of implementation cast already exists, another one is not added.
The operator implementation remains unchanged.
If the implementation of a MIN, MAX or MUX operator can be converted automatically, only the operator implementation is removed. No implementation cast is added.
If it is not possible to convert all operator implementations automatically in the database, the following message is issued:
Not all operator implementations could be replaced automatically. Please do the conversion manually.
Confirm this message with OK. The Operator Implementations window (see Searching for Operator Implementations) opens, it shows the components which contain the remaining operator implementations. You can now convert them manually, or remove them.
See also
Replacing Operator Implementations with Implementation Casts
Searching for Operator Implementations
Removing Operator Implementations