Field entities store spatially varying values, which can later be realized (mapped) to the element and node data of a new target mesh.

Field mapping can be used to:
  • Transfer temperature result data in an analysis results file from a thermal analysis to a structural model (a different mesh to that of the thermal model) as nodal temperature loads. (Continuous field)
  • Transfer displacement values in an analysis results file from a coarse structural analysis to a detailed structural model (sub modeling based on enforce displacement from a global model) as nodal enforced displacement. (Continuous field)
  • Transfer temperature or pressure values in a .csv file ( x,y,z, temperature) to a structural model as nodal temperature loads or element pressure loads. (Discrete field)
  • Transfer pressure data in an analysis deck from an existing model to a new structural model (different mesh) as element pressures. (Continuous field)
  • Transfer two-dimensional parametric data (u,v, data value) in a .csv file to a 3D surface model. Data vales can be temperature or pressure. Mapping is done in a parametric system. (Continuous field)
  • Transfer property ID, material orientation, and/or load data in an analysis input deck from an existing model to a new structural model (different mesh). (Continuous field)
  • Transfer 2D/axis-symmetric model temperate or pressure data to a new 3D model as temperate or pressure loads. (Continuous field)
  • Bar/Beam 1D to 2D/3D element mapping.
  • 3D to 2D/3D element mapping.
  • Mapping types (for discrete/.csv data only.)
  • Generic field mapping.
  • Reviewing and transforming source data.
  • Nodal force balancing using OptiStruct.

You can create field entities in the Model Browser, and edit their corresponding attributes in the Entity Editor. All fields are stored in the Field folder within the Model Browser.