*mergefile2

Merges a HyperMesh binary file into the current model, additionally applying Redundant Entity Management (REM).

Syntax

*mergefile2 key1=value1 key2=value2 ... keyN=valueN

Type

HyperMesh Tcl Modify Command

Description

Merges a HyperMesh binary file into the current model, additionally applying Redundant Entity Management (REM). REM is supported for properties, materials, connectors, components and parts/part assemblies.

Depending on the below settings, entity names or IDs in the incoming file may be renamed/renumbered with the least disruption possible.

Inputs

connectors.checkattribute=<value>
This determines if connector attributes are compared when deciding if they are the same. Possible values are true and false. This is optional and false is the default.
connectors.layercheck=<value>
This determines if connector layers are compared when deciding if they are the same. Possible values are true and false. This is optional and false is the default.
connectors.thicknesscheck=<value>
This determines if connector thicknesses are compared when deciding if they are the same. Possible values are true and false. This is optional and false is the default.
connectors.tolerance=<value>
This specifies the tolerance to use when deciding if connectors are the same.
dropincomingmodulehierarchy=<value>
This is for special cases that need to drop any incoming module hierarchy, but keep the contents. Possible values are yes and no. This is optional and no is the default.
filename=<value>
The full path and file name of the HM binary file to merge.
mergemode.comps=<value>
Specifies how to merge the attributes of components identified as the same. Possible values are keepexisting, keepincoming and keepboth. This is optional and keepboth is the default.
mergemode.connectors=<value>
Specifies how to merge the attributes of connectors identified as the same. Possible values are keepexisting, keepincoming and keepboth. This is optional and keepboth is the default.
mergemode.geometryandmesh=<value>
Specifies how to merge the contents of components identified as the same. Possible values are keepexisting, keepincoming and keepboth. This option is valid only in case that mergemode.comps is either keepexisting or keepincoming. When mergemode.comps is keepboth, there will be separate components anyway. This is optional and keepboth is the default when valid.
mergemode.mats=<value>
Specifies how to merge the attributes of materials identified as the same. Possible values are keepexisting, keepincoming and keepboth. This is optional and keepboth is the default.
mergemode.props=<value>
Specifies how to merge the attributes of properties identified as the same. Possible values are keepexisting, keepincoming and keepboth. This is optional and keepboth is the default.
mergemode.sensors=<value>
Specifies how to merge the attributes of incoming sensors identified as the same. Valid values are keepexisting, keepincoming and keepboth (default).
mergemode.sections=<value>
Specifies how to merge the attributes of incoming sections identified as the same. Valid values are keepexisting, keepincoming and keepboth (default).
respectincomingparentmodule=<value>
This is used to guide component conflict resolution. This is necessary when an incoming component belongs to a different part, in comparison with the same component in the session. In this case the conflict is resolved either by respecting the incoming parent part or the in-session one. Possible values are yes and no. This is optional and no is the default.

Example

To merge the file C:/temp/Rail2.hm, keeping all incoming data:

*mergefile2 filename=C:/temp/Rail2.hm mergemode.props=keepincoming mergemode.mats=keepincoming mergemode.comps=keepincoming mergemode.geometryandmesh=keepincoming

Errors

Incorrect usage results in a Tcl error. To detect errors, you can use the catch command:
if { [ catch {command_name...} ] } {
   # Handle error
}

Version History

14.0

2022.3 - Added new options mergemode.sensors and mergemode.sections.