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.
Data Mappers Reference
Data mappers allow you to map data from source meshes or tables to target mesh representations.

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.
  - Data Mappers Reference
    Data mappers allow you to map data from source meshes or tables to target mesh representations.
    - Data Mapper Reference by Type
      This section provides information on the actions and properties available for all types of mappers. The data mapper properties include source settings and mapped field specifications.
    - Target Reference
      This section provides information on the properties available for all types of mapping targets. A mapping operation can have several targets for each source.
    - Constraint Checks Reference
      Set up constraint checks to specify criteria for mapping. If you enable a constraint check, the mapper only maps field data to target points that pass the constraint check. You can specify alternate field values at target points that fail the constraint checks.
    - Field Functions Reference
      When you execute a data mapper, Simcenter STAR-CCM+ creates field functions that allow you to access the mapped data and to determine whether the mapping process was successful.
    - Specific CAE Properties
      Data mappers are created manually or by invoking a map-action on surfaces or volumes of imported models. The map-action dialog has special properties depending on the type of surfaces and the data type chosen for mapping.
  - 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.

Data Mappers Reference

Data mappers allow you to map data from source meshes or tables to target mesh representations.

The following sections provide information on all the properties and options available for data mappers.

You can set up data mappers under the Tools > Data Mappers node. The options available when you right-click the Data Mappers node allow you to create new mappers and to perform actions on all the existing data mappers at once:

Table 1. Action Menu
New Data Mapper	Creates a data mapper. Choose the mapper type based on the type of source from which you want to map data.
	Surface Data Mapper	Interpolates data from source surfaces to target surfaces, volumes, or beams.
	Volume Data Mapper	Interpolates data from source volumes to target surfaces or volumes.
	Beam Data Mapper	Interpolates data from a single source beam to a single or multiple target surfaces.
	Tabular Data Mapper	Interpolates data from an XYZ table to target surfaces, volumes, or beams.
	Parcel Data Mapper	Interpolates data from Lagrangian phases to mesh volumes.
	Boundary Samples Data Mapper	Interpolates data from boundary samples—sample parcels that impinge on a boundary.
Clear Mapped Fields	This action deletes any mapped fields and corresponding mapped data field functions generated by the mappers. If a mapped data field function is used by other objects in the simulation, such as scenes or reports, make sure that you remove any dependencies before using the Clear Mapped Fields option. If you do not remove the dependencies, any data associated with the mapped field function will be deleted but the mapped field function will not be removed from the simulation tree.
Pre-Register Mapped Fields	By default, mapped fields become available as field functions when you execute the corresponding mapping operation. Use this option to pre-register the mapped fields, that you specified for any data mappers, as field functions, so that they are immediately available to other simulation objects such as reports or scenes.