Home
Interacting with CAE Software
Simcenter STAR-CCM+ can interact with a wide range of other computer-aided engineering (CAE) software. This interaction includes import/export of mesh and solution data as well as coupling capabilities for multiphysics simulations.
Data Mappers
In Simcenter STAR-CCM+, data mappers allow you to interpolate field data available either on a source mesh or on a source table to a target mesh representation, so that the mapped fields can be used for applying boundary or volume conditions on the target mesh.
Mapping Fields Using Data Mappers
The following workflow demonstrates how to manually create, set up and execute mapping operations, to interpolate field data between different mesh representations or between tabular data and target meshes.
Defining Constraint Checks
Optionally, enable constraint checks to specify criteria for mapping. Two constraint checks are available: the Proximity Constraint check, and the Normal Direction Constraint check, which is only available for surface-to-surface mapping. When you enable a constraint check, the mapper only maps field data to target points that pass the constraint check.

Share

Link: copied

Breadcrumb: copied

Interacting with CAE Software
Simcenter STAR-CCM+ can interact with a wide range of other computer-aided engineering (CAE) software. This interaction includes import/export of mesh and solution data as well as coupling capabilities for multiphysics simulations.
- File Import and Export
  Simcenter STAR-CCM+ allows you to import mesh and solution data from other CAE packages using files. You can also export such data from Simcenter STAR-CCM+ for use in external software.
- File-Based Coupling (through Imported CAE Model)
  File-based coupling is a method used to couple Simcenter STAR-CCM+ with another CAE code via external files stored in the computer memory.
- Rotor Blade Aeroelasticity
  Rotor Blade Aeroelasticity (RBA) simulations model the aerodynamic performance of elastic rotor blades using displacement and twist data from external files. You can create these data files in multi-body dynamics software such as RCAS, CAMRAD-II, DYMORE, and FLIGHTLAB. Typical RBA applications include urban air vehicle rotors, wind turbines, and helicopter rotors.
- Simcenter STAR-CCM+ to Simcenter STAR-CCM+ Co-Simulation
  Simcenter STAR-CCM+ allows you to couple two running simulations together in a co-simulation analysis. The Simcenter STAR-CCM+ to Simcenter STAR-CCM+ co-simulation capability targets analyses involving conjugate heat transfer (CHT), fluid-structure interaction (FSI), and exchange of any scalar or vector fields across the coupled boundaries or regions.
- Simcenter Nastran Co-Simulation
  For fluid-structure interaction (FSI) analyses, you can couple Simcenter STAR-CCM+ and Simcenter Nastran in a co-simulation analysis.
- Simcenter Amesim Co-Simulation
  Simcenter STAR-CCM+ allows for two-way co-simulation with Simcenter Amesim, which is used for modeling dynamic systems.
- FMU Co-Simulation
  Simcenter STAR-CCM+ allows you to import Functional Mock-up Unit (FMU) models for co-simulation. An FMU is a time-dependent model, typically representing a dynamic network, that is written according to the Functional Mock-up Interface (FMI) standard. The FMI standard is a software-independent standard that provides an interface for coupling simulation software.
- Abaqus Co-Simulation
  The co-simulation technique can be used to solve complex fluid-structure interaction (FSI) problems by coupling Abaqus and Simcenter STAR-CCM+. Mechanical and/or thermal fields can be exchanged across the fluid-structure interface.
- GT-SUITE Co-Simulation
  Simcenter STAR-CCM+ allows for two-way co-simulation with GT-SUITE, a multiphysics simulation tool from Gamma Technologies. GT-SUITE provides a modeling framework for the design and analysis of engineering systems, such as engines, vehicles, and thermal-hydraulic networks.
- Reacting Channel Coupling
  The Reacting Channel Coupling feature provides the ability for exchange of data between three-dimensional Simcenter STAR-CCM+ and the one-dimensional Plug Flow Reactor which uses the CVODE solver. You can use the Reacting Channel co-simulation model in Simcenter STAR-CCM+ to solve reacting flow simulations in tubular heat exchangers with channels that are long and thin.
- Generic Launcher
  Simcenter STAR-CCM+ provides a generic launcher for external applications that allows you to launch any application or file at a specified time interval during a simulation.
- Co-Simulation API
  Simcenter STAR-CCM+ provides an Application Programming Interface (API) that allows you to write partner code that exchanges data with a running Simcenter STAR-CCM+ simulation. As the partner code can be part of any other application that supports linking to a flat C library, the co-simulation API extends the range of co-simulation scenarios possible with Simcenter STAR-CCM+.
- Data Mappers
  In Simcenter STAR-CCM+, data mappers allow you to interpolate field data available either on a source mesh or on a source table to a target mesh representation, so that the mapped fields can be used for applying boundary or volume conditions on the target mesh.
  - Mapping Fields Using Data Mappers
    The following workflow demonstrates how to manually create, set up and execute mapping operations, to interpolate field data between different mesh representations or between tabular data and target meshes.
    - Mapping Data from Surface, Volume, or Beam Sources
      The steps for creating a data mapper to interpolate fields between different mesh representations are outlined in this section.
    - Mapping Tabular Data
      In Simcenter STAR-CCM+, you can define boundary or initial conditions using tabular data. If the table data is much coarser than the target mesh, create a tabular data mapper to interpolate the tabular data to the mesh.
    - Specifying the Target Mesh and Interpolation Method
      Set up mapping targets to specify the target mesh, the interpolation method, and other mapping options. A mapping operation can have one or more targets of type Surface, Volume, or Beam.
    - Mapping Parcel Data
      In Simcenter STAR-CCM+, you can map the data available on Lagrangian Phases on to volume meshes. For this, the data mapper requires inputs such as the source Lagrangian phase and source field functions. It only maps the data available via field functions. The data mapper creates output field functions corresponding to the input field functions. These output field functions are available on the target regions in the volume mesh.
    - Defining Constraint Checks
      Optionally, enable constraint checks to specify criteria for mapping. Two constraint checks are available: the Proximity Constraint check, and the Normal Direction Constraint check, which is only available for surface-to-surface mapping. When you enable a constraint check, the mapper only maps field data to target points that pass the constraint check.
    - Executing the Mapping Operation
      Execute the mapping operation manually, or set up automatic mapping at a specified frequency during the simulation run. Optionally, pre-register the mapped fields so that you can access the corresponding field functions before mapping occurs.
  - Data Mappers Reference
    Data mappers allow you to map data from source meshes or tables to target mesh representations.
  - Examples of Using Data Mappers
    This section provides two examples of multiphysics applications where you can use data mapping for explicit coupling.
- Coordinate Cell Clustering
  Simcenter STAR-CCM+ allows you to group mesh cells into clusters, based on their position with respect to a specified coordinate system, and provides a field index for querying values based on cluster. You can create threshold reports based on these clusters of cells.

Defining Constraint Checks

Optionally, enable constraint checks to specify criteria for mapping. Two constraint checks are available: the Proximity Constraint check, and the Normal Direction Constraint check, which is only available for surface-to-surface mapping. When you enable a constraint check, the mapper only maps field data to target points that pass the constraint check.

To enable constraint checks:

Select the relevant constraint checks, either [Target] > Proximity Constraint, or [Target] > Normal Direction Constraint, or both, and activate Enable.
When using a Proximity Constraint check, specify either an absolute or relative proximity tolerance. When using a Normal Direction Constraint check, specify the lower limit for the angle between the source and target normals.
For more information, see Constraint Checks Reference.

Mappers do not interpolate data to target points that fail the proximity or normalcy checks. At these points, you can specify constant alternate values for the scalar or vector fields that you specified for mapping. To assign alternate values to vector fields:

Select the [Target] > Alternate Value Specification node.
Click to the right of Vector Alternate Values.
Enter the three components of each function as a comma-separated list contained in round brackets. List all the functions as a comma-separated list in the same order as the selected field functions. Place the entire list in square brackets.
For example, to set the alternate value of Velocity to (1,0,0) and the Wall Shear Stress to (0,0,0):
- If the Selected Vector Fields are listed as [Velocity, Wall Shear Stress], then in the Vector Alternate Values type [(1,0,0),(0,0,0)]

To specify alternate values for scalar fields:

Click to the right of Scalar Alternate Values.
Enter the constant values for all the functions as a comma-separated list in the same order as the selected field functions. Place the entire list in square brackets.
For example, to set the alternate value of Local Heat Transfer Coefficient to 0 and the Local Heat Transfer Reference Temperature to 300:
- If the Selected Scalar Fields are listed as [Local Heat Transfer Coefficient, Local Heat Transfer Reference Temperature], then in the Scalar Alternate Values type [0.0,300].
For more information, see Alternate Value Specification Reference.