Custom Merging Basic Model Data
Custom Merging Basic Model Data
This figure shows the basic model data window. In this example there are problems with clashes in the types NODE, SHELL, SET_PART, PART, MATERIAL, SECTION, HOURGLASS, CONTACT, DEFINE CURVE, GROUP and ASSIGN MASS . Clicking on the question mark maps a menu from which or clashing items can be performed. Further pop-ups in this menu allow , , , and actions on individual items.
Resolving clashes using the basic "Action" popup menu
Just as in the global parameters window, actions can be used to solve the clash problems.
The actions available to resolve these, in the > popup menu, are, in more detail:
| 1 | The items will be taken from both models. The labels of all items in M1 (of this type) are renumbered to be above the item labels in M2 | |
| 2 | Copy from both. Inc M1 if needed | The items will be taken from both models. The labels of items in M1 (of this type) will be renumbered to be above the item labels in M2 only if there is a clash. If there is no clash the original label will be used |
| 3 | As 1. except models swapped. | |
| 4 | As 3. except models swapped. | |
| 5 | On clash copy only M1 | The items will be taken from both models except when there is a label clash. When this occurs only the item from M1 will be taken |
| 6 | . | As 5. Except item will be taken from M2 |
| 7 | . | Nothing will be renumbered. This is only possible if there are no clashes. |
As appropriate actions are chosen for each type (or all types) the will be replaced by . This figure shows the same model after actions have been chosen to fix problems. The action column shows what has been done in each case.