Map metal temperatures from WEM to component models
Learn how to map metal temperatures from a Whole Engine Model (WEM) to component models. This workshop covers rotational periodicity mapping, axisymmetric mapping, alignment tools, merged mapping solutions, and automatic generation of Nastran and ANSYS outputs.
Introduction
With the merge results functionality, temperatures can be:
- Mapped from multiple source solutions.
- Updated selectively for specific components.
- Appended to an existing mapped solution.
Solving a mapping solution generates a BUN file, and depending on the selected options can automatically create structural solutions or solver input files.
In this tutorial, you will:
- Set up rotational periodicity mapping.
- Define axisymmetric mapping constraints.
- Use the mapping alignment tool.
- Create a merged mapping solution.
- Automatically generate Nastran and ANSYS input files.
- Automatically generate an ANSYS solution with temperature constraints applied.
Open the source model and inspect
Inspect source solutions and understand which temperatures will be mapped.
Open the target model and inspect
Review geometry differences and plan mapping strategy.
Create mapping constraints in the source model
Define rotational periodicity and axisymmetric mapping zones.
Create a mapping solution in the target model
Reference source bun file and define mapping alignment.
Create a merged mapping solution
Update the previously mapped solution by replacing the temperatures of disk 2 using results from a second thermal analysis. When creating the merged mapping solution, reference the first Solution 1 mapping solution.
Inspect generated structural outputs
Review automatically generated solver inputs and reference fields.
Additional notes
Understand additional mapping options and best practices.
- Additional output formats for thermal solver and Abaqus are available.
- If you forget to add a mapping zone in the source model, you do not need to re-solve the solution. Simply add the required mapping constraint to the source model and write the XML input file without running the solve again. The new mapping zones will then appear and can be referenced in the target mapping solution.
- You can define an angular offset for rotational periodicity mapping constraints. Use this option when the source and target models contain cyclic sectors at different angular positions.















