Appending data from a solver input file to a FEM or Simulation file

In the Abaqus, ANSYS, LS-DYNA, Simcenter Nastran, and MSC Nastran environments, you can select the Append Merge option from the Import Behavior list in the File Append dialog box to import, append, and merge data from an input file (the source file) into a FEM or Simulation file (the destination file). You can use the Append Merge option to import portions of an input deck or an incomplete input deck into an existing model, as long as the missing portions of the input file already exist in the destination file in Pre/Post.

In Simcenter Samcef, you can use the Append Merge option to import portions of a Nastran input deck into a Simcenter Samcef model. For more information, see Import Nastran data to a current Simcenter Samcef model.

For example, you can use the Append Merge option to import:

• Elements from an input deck into a destination FEM file that already contains nodes.

• Group definitions that reference nodes and elements that exist only in the destination FEM file, not in the solver input file.

• Loads and constraints into a destination file that already contains a mesh. This is useful, for example, if you need to import boundary conditions from custom load generation software into the Pre/Post Simulation file.

• A Nastran CBAR element whose orientation node is defined in the destination FEM file.

• A Nastran CORD1x coordinate system entry for which some or all of its defining nodes exist only in the destination FEM file, not the solver input file.

Ability to create a new solution

In the File Append dialog box, you can use options in the Create Solution list to control whether the source solver input file data is appended into a new solution in Pre/Post.

• Select No if you do not want to create a new solution. All loads and boundary conditions are placed in the appropriate containers in the Simulation Navigator, but they are not referenced in the current solution. Any appended modeling objects are also not referenced in the current solution.

• Select Yes to create a new solution. All loads and boundary conditions are placed in the appropriate containers in the Simulation Navigator and referenced in the current solution. Any applicable, appended modeling objects are also referenced in the new solution.

Controlling how conflicts in data are handled

You can use the options in the Merge Conflict Resolution Options group to specify how Pre/Post should handle conflicts between the data in the source solver input file and the data in the destination FEM or Simulation file. These options control how the software handles conflicts between:

• Nodes

• Materials

• Physical properties

• Element physical property data (in the Nastran environment only)

You can:

• Select Ignore File Data if you do not want to append an entity from the solver input file when it conflicts with an existing entity in the Pre/Post destination file. For example, if both the source solver input file and destination Pre/Post file have a material with an ID of 15, Pre/Post does not append the material from the solver input file.

• Select Modify Using File Data to replace the node, material, or physical property data in the Pre/Post destination file with the data from the source solver input file.In the Nastran environment, you can also use this option to replace element physical property data in the destination file with element physical property data from the source Nastran input file. For more information, see Managing element conflicts when appending a Nastran input file.

• Select Append File Data to specify a numerical offset to increment the label (ID) when conflicts occur. With this option, Pre/Post uses the offset to change the ID of the entity in the source input file during the append. The software also updates any references to that entity in the source file. For example, if you append a CBAR element that originally references nodes 1 and 2, those nodes are renumbered with an offset of 1000 because of a conflict and the software updates the CBAR element to reference nodes 1001 and 1002.

Pre/Post does not modify other types of data in the destination FEM or Simulation file, such as:

• Solution attributes.

• Values in existing loads, boundary conditions, simulation objects, or modeling objects.

• The content of existing Pre/Post groups.

• Elements and coordinate systems.

Requirements for merging entities

• To merge entities, the solver environment specified in the FEM file in Pre/Post and the in currently active solution in the associated Simulation file must be the same. For example, if Simcenter Nastran is the specified solver environment for the FEM file, Simcenter Nastran must also be the specified solver environment for the active solution.

• Pre/Post appends only those entities that are valid for the type of file that is active. For example:If you use the Append Merge option when the FEM file is the work and displayed part, Pre/Post imports and appends only those entities, such as elements, that are valid for the analysis type specified for the destination FEM file. For example, If the analysis type in the active FEM file is axisymmetric structural, Pre/Post imports and appends only axisymmetric structural elements from the source solver input file to the destination FEM file.If you use the Append Merge option when the Simulation file is the work and displayed part, Pre/Post imports and appends only those entities, such as loads, boundary conditions, or output requests, that are valid for the analysis type of the active solution in the destination Simulation file. All FEM entities that are valid for the specified analysis type, such as elements and physical property tables, are imported and appended. For example, if the analysis type in the active solution is structural, Pre/Post imports and appends only structural loads to the destination Simulation file.Note: If there is no active solution in the Simulation file, Pre/Post assumes that the analysis type specified in the FEM file is the solution type.

• Pre/Post appends only those entities that are valid for the active solution type. For example:If the analysis type in the active FEM file is axisymmetric structural, Pre/Post imports and appends only axisymmetric structural elements from the source solver input file to the destination FEM file.If the analysis type in the active solution is structural, Pre/Post imports and appends only structural loads to the destination Simulation file.Note: Regardless of the analysis type, Pre/Post appends the Nastran SET command as the Pre/Post group.

• When you are appending and merging data from Simcenter Nastran and ANSYS input files, the specified analysis type and the setting of the 2D Solid Option in the destination FEM file do not get altered. Pre/Post only appends and merges elements that are supported in the analysis type of the destination FEM file. For example, Pre/Post does not append and merge thermal elements into a structural analysis FEM file.

• If you select Yes from the Create Solution list, you should create a new solution that has an analysis type and 2D Solid Option setting that is consistent with the data in the source solver input file.

• If you select No from the Create Solution list and there is an active solution in the destination Simulation file, you should ensure that entities you are appending and merging are consistent with the analysis type and 2D Solid Option setting of that active solution.

• If you select No from the Create Solution list and there is not an active solution in the destination Simulation file, you should ensure that entities you are appending and merging are consistent with the analysis type and 2D Solid Option setting of the Pre/Post FEM file.

Merge behavior depends on the type of entity that you are merging

With the Append Merge option, the software divides entities into three categories, depending on whether an entity retains its ID (label) when it is imported into Pre/Post.

• Entities that retain their ID (label) when they are imported into Pre/Post are considered to be category 1 entities. With a category 1 entity, if the software detects a conflict with an existing ID in the model, it does not append the entity from the solver input file. Pre/Post appends a category 1 entity to the Pre/Post FEM or Simulation file only if an ID conflict does not occur.Category 1 entities include:Coordinate systemsNodes (as defined by GRID and SPOINT entries)Physical properties tablesMaterialsRegionsFor example, if both the solver input file you are appending and the active FEM file both contain a node with an ID of 101, you can use the Merge Conflict Resolution Options to ignore source file data, modify destination file data or append source file data.If the label conflict occurs during the append process, the software issues a message in the Information window.

• Entities that do not retain their IDs when you import them into Pre/Post are considered to be category 2 entities. Pre/Post always appends category 2 type entities to the FEM or Simulation file but does not include them in a specific solution or step. You can add category 2 entities to specific solutions or steps as you need to.Category 2 entities are typically defined by case control commands and include:Loads and constraintsDegree-of-freedom setsSimulation objectsModeling objectsGroupsOutput requestsFor example, if you use the Append Merge option to import and append a solver input file that contains only PLOAD2 entries, Pre/Post imports those entries as a new pressure load. The software places that pressure load in the Loads container in the Simulation Navigator. You can then drag and drop the pressure load directly into the appropriate solution or step.

• Entities that retain their IDs when they are imported but for which you cannot control any ID conflicts are considered to be category 3 entities. For these entities, if Pre/Post detects a conflict with an existing ID, the software does not append the entity from the solver input file. Pre/Post appends these entities to the Pre/Post FEM or Simulation file only if an ID conflict does not occur.Category 3 entities include:Coordinate systemsRegionsFor example, if both the source solver input file and the active FEM file contain a coordinate system with an ID of 101, Pre/Post does not append the coordinate system.If the label conflict occurs during the append process, the software issues a message in the Information window.

Where do I find it?

Application	Pre/Post
Prerequisite	A FEM or Simulation file as the displayed part and work part and Simcenter Nastran, MSC Nastran, ANSYS, Abaqus, LS-DYNA, or Simcenter Samcef as the specified solver
Menu	File→Append

How do I

Append a solver input file to a FEM and Simulation file

Learn more

Appending a solver input file

Appending an entire solver input file to a FEM or Simulation file

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Appending data from a solver input file to a FEM or Simulation file, Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });