model assemble
Allows you to merge several models into one big model.
Format:
model assemble |
|---|
new_model_name = | a new model |
model_names = | an existing model |
prefix = | string |
suffix = | string |
translation = | location |
rotation = | orientation |
duplicate_parts = | dupl_part_action |
add_to_group_name = | a new or existing group |
Example:
model assemble & |
|---|
new_model_name = | model__1 & |
model_names = | crankshaft , model_1 & |
prefix = | "new_" & |
translation = | 10 , 10 , 10 & |
rotation = | 0 , 0 , 0 & |
duplicate_parts = | rename |
Description:
Parameter | Value Type | Description |
|---|
new_model_name | A New Model | The model into which the models specified by 'model_names' will be merged. |
model_names | An Existing Model | Specifies a list of existing models in Adams View, to be merged to create an assembled model. |
prefix | String | This parameter specifies the list of prefixes that are applied to all entities at the part level as they are assembled into a destination model. |
suffix | String | This parameter specifies the list of suffixes that are applied to all entities at the part level, as they are assembled into a destination model. |
translation | Location | Specifies the translations (relative to the global origin) that are applied to the parts, polylines, and notes beneath the source model before it is merged with the destination model. |
rotation | Operation | Specifies the rotations (about to the global origin) that are applied to the parts, polylines, and notes beneath the source model before it is merged with the destination model. |
duplicate_parts | Dupl_Part_Action | Specifies what to do when a part in the destination model has the same name as a part in the source model. |
add_to_group_name | A New or Existing Group | This parameter specifies a new or existing group into which Adams View will add all merged objects. |
Extended Definition:
1. The "model_names" lists the source of the objects being merged and the "new_model_name" names the destination model. The source models are not changed after the assemble operation.
You can specify a set of translations and rotations that are applied to the parts, polylines, and notes of each source model before it is merged with the assembled model.
If you specify that parts with the same name in both models (duplicate parts) are to be merged, then all of the children beneath the parts of the source model will be copied beneath the corresponding parts in the assembled model. Otherwise, the duplicate parts in the source model will be copied and renamed in the destination model.
MODEL MERGE VS. MODEL ASSEMBLE
Although the "model merge" and "model assemble" commands accomplish much the same thing, there are several differences between them. These differences are
a. If ground parts are not merged during a "model assemble", then they will be constrained to ground with an automatically created fixed joint. ("Ground" is what was originally ground in the the first model in the "model_names" list.)
The auto-created fixed joints for the ground parts are named "fixed_ORIGINAL_MODEL_NAME"; the markers are named, "fixed_i_ORIGINAL_MODEL_NAME" and "fixed_j_ORIGINAL_MODEL_NAME" with the J marker going to the assembled model's ground part and the I marker on the part that was once a ground.
b. In "model assemble", with the renaming of like-named parts, the ground parts for all but the first model in the list are renamed "ground_ORIGINAL_MODEL_NAME" (unless the prefixes/suffixes you specify are sufficient for distinguishing the ground names). In "model merge", ground parts are renamed only if their names conflict, and then they are renamed the same way as other parts (typically, "ground_2" or "ground_3").
c. As with "model copy", the "model assemble" command retains the Adams IDs for the first model; all others may be changed if there are conflicts.
d. With "model assemble", you may relocate and/or reorient any of the models, including the first one, as they are merged into the assembly.
e. With "model assemble", gravity forces are eliminated from all but the first model. If the first model has no gravity, then there will be no gravity in the assembly. In a "model merge", duplicate gravity forces are renamed (usually, something like "gravity_2").
f. The model assemble command is much faster than using the copy, merge strategy for creating an assembly of models. You will often see a four-fold improvement in performance by using "model assemble" instead of a "model copy", "model merge" sequence.
2. You may identify a model by typing its name or by picking it from the screen.
If the model is not visible on the screen, you must type the name.
You may also find it convenient to type the name even if the model is displayed.
You must separate multiple model names by commas.
If the model is visible in one of your views, you may identify it by picking on any of the graphics associated with it.
You need not separate multiple model picks by commas.
3. If you specify that duplicate parts are to be merged, then all the children beneath the parts of the source model will be copied beneath the corresponding parts in the destination model. Otherwise, the duplicate parts in the source model will be copied and renamed in the destination model.
4. The add_to_group parameter specifies a new or existing group into which Adams View will add all merged objects. All objects that were copied from the source model into the destination model will be added to the specified group.
Cautions:
1. The source entities are not changed by the assemble operation.