Source model preparation
For SolidWorks® Simulation users:  INP model considerations

In SolidWorks® Simulation a FEM model exported to INP can contain only one load step and surface loads are typically preprocessed and exported as nodal forces. For this reason, to generate a complete optimization-ready FEM model with

• arbitrary number of load cases, and/or
• arbitrary number of surface regions

one needs to export several INP files. ProTOp can then combine several INP files into a single FEM model, ready for optimization. In order to enable combining several INP files into one model, the INP files have to be named by using the special notation described below.

Naming of INP files to get a single optimization model

In order to combine several INP files into a single model, export several INP files and name them by adhering to the following naming patterns:

• anyname.inp - this should be the file containing the first load case; the anyname is arbitrary.
• anyname_LC_i.inp - these should be the names of the files containing load cases 2, 3, ... (one load case per file); the i should be an arbitrary but unique mark; any number of these files is allowed.
• anyname_EXPGEO_i.inp - these should be the names of the files containing loads applied to surfaces that we want to use by model configuration tools (one surface per file); the i should be an arbitrary but unique mark; any number of these files is allowed.

It is important to note that all loaded nodes within an *_EXPGEO_*.inp file are assumed to define a single surface region that may or may not be simply connected. This means that each such file defines exactly one surface region.

Another important issue is mesh consistency. Combining several INP files into a single optimization model can only be done if the FE meshes in all INP files are consistent. Inconsistent meshes will result in a failure.

NOTE. Because several INP files have to be imported to build a complete optimization model, special attention is required to assure that the FE meshes in all INP files are consistent.

Example

In order to prepare a model named Bracket, which contains 2 load cases and 3 surface regions, the exported INP files might be named as follows:

• Bracket.inp
• Bracket_LC_2.inp
• Bracket_EXPGEO_1.inp
• Bracket_EXPGEO_2.inp
• Bracket_EXPGEO_3.inp

Assuring FE mesh consistency across all INP files

In order to assure that all INP files of an optimization problem will have consistent FE meshes, the following procedure should be followed:

• Create your model and define all loads that will appear either in any load case or in any configuration surface definition
• Export one INP file per load case and one INP file per surface definition as follows:
  • Use the Suppress option to suppress all loads that does not belong to the current load case or surface definition
  • Export the INP file; this file will contain loads belonging only to the current load case or surface definition
  • Name the exported INP file by using either the load case pattern _LC_ or the surface pattern _EXPGEO_

It is important to note, that an added/removed/changed load necessitates to export all the INP files again, because such a change may cause remeshing of the model.

NOTE. To assure mesh consistency, all loads need to be defined prior beginning the export of individual INP files and must not be changed during this process.

Limitations of the importer

The following options are supported by ProTOp when importing from INP files created by SolidWorks® Simulation.

Part

• Single 3D Deformable Multi Solid Body

Connections

• Component contacts
  • Bonded, Global contact, Compatible mesh

Property

• Material
  • Linear Elastic Isotropic
  • Density, Uniform Distribution
• Material Assignment
  • Solid Body

Load

• External Loads
  • Force
  • Torque
  • Pressure
  • Gravity
  • Centrifugal Force
  • Temperature
• Fixtures
  • Fixed Geometry
  • Roller/slider (no Roller)

Mesh

• 3D Stress Family
  • 10-node quadratic tetrahedron