Custom Merging Global Parameters
Custom Merging Global Parameters
This figure shows the global parameters window for the example above. You can see that:
|
DATABASE_EXTENT_BINARY
DATABASE_EXTENT_SSSTAT, LOAD_BODY |
Cards only exist in one of the 2 models so there is no problem. |
|
AIRBAG_REFERENCE_GEOMETRY, CONTROL,
DATABASE_ASCII DATABASE_BINARY |
Cards exist in both models and so there are duplicate cards which is causing a problem. |
Resolving clashes using the global "Action" popup menu
The problems arise because the default action for all the types is to copy from both models ( Copy from M1 and M2 ). This can be changed for all types, or for each individual type by using the action popup. The actions are self explanatory except for the last two. The Copy from M1 (or M2 if not in M1) card is only in the first model or is in both models. If will take a card from the first model if the the card is only in the second model it will be taken from the second model. This is useful if you want to make sure that all control cards are copied from both models. They will be taken from both but the control cards in the first model will take precedence over the control cards in the second model.
As appropriate actions are chosen for each type (or all types) the will be replaced by . The figure above shows the same model after actions have been chosen to fix problems.
Summary or detailed information on a problem with each type is available by using the information popups.