Simcenter 3D Solutions Assembly Label Manger for Vibro-Acoustic analysis
2020-05-21T12:43:09.000-0400
Samcef Desktop
Samcef Wind Turbines
Simcenter Nastran
Simcenter Samcef
Simcenter 3D
Simcenter 3D Solutions Marketing
TEA Pipe
BOSS Quattro
Simcenter Multimech
Teamcenter Share
CAESAM
Simcenter FLOEFD SC
Summary
Details
When perform vibro-acoustic responses, multiple fem components (e.g. structure, acoustic, microphones…) are defined in the assembly. Quite often there are ID (label) conflicts (for nodes, elements, properties, groups…) found among these components. ID offsets are required in these cases. However, the fem components are usually associated to the results files (structural response, mode set, frf set, ATV set…), offset the IDs incorrectly could lead to wrong results. Depends on the types of result file, there are two ways to offset the labels for the components.
If acoustic component is represented by an ATV set and labels for the acoustic component are offset, an ATVBULK card for the defined offsets will be exported to the input data file. This card reconnects the renumbered acoustic mesh to the ATV result file (op2 file).
Similarly, if structural component is represented by a mode set and labels for structural component are offset, Simcenter will write out a MDSBULK card for the defined offsets.
Please note that MDSBULK card only works for sc_h5 result file. If you have result files in other formats (op2, rst, odb…), make sure you first convert these result files to sc_h5 file format via Model and Load Pre-processing.
One drawback with this approach is, the binary result file (op2, sc_h5…) associated to the renumbered structural component can only be exported out as ASCII format using the Label Matching Strategy User Defined Mapping, instead of the binary format using Defined by the File.
For this reason, it is preferred to renumber the acoustic component instead of the structural component.
Label conflicts could be fixed automatically by select the option Automatically Resolve. It will automatically offset the labels for the last listed component in this case.
- Represent the fem components by the result files
If acoustic component is represented by an ATV set and labels for the acoustic component are offset, an ATVBULK card for the defined offsets will be exported to the input data file. This card reconnects the renumbered acoustic mesh to the ATV result file (op2 file).
Similarly, if structural component is represented by a mode set and labels for structural component are offset, Simcenter will write out a MDSBULK card for the defined offsets.
Please note that MDSBULK card only works for sc_h5 result file. If you have result files in other formats (op2, rst, odb…), make sure you first convert these result files to sc_h5 file format via Model and Load Pre-processing.
- For structural loads (op2, unv, sc_h5…) defined via Load Recipe
One drawback with this approach is, the binary result file (op2, sc_h5…) associated to the renumbered structural component can only be exported out as ASCII format using the Label Matching Strategy User Defined Mapping, instead of the binary format using Defined by the File.
For this reason, it is preferred to renumber the acoustic component instead of the structural component.
Label conflicts could be fixed automatically by select the option Automatically Resolve. It will automatically offset the labels for the last listed component in this case.