Home
Thermal-Flow
Contains general thermal and flow solver related documentation, such as the verification test cases, monthly critical fixes, DMP guide, and knowledge base articles.
Thermal and flow DMP guide
Describes the general workflow for executing the simulation jobs using distributed memory parallel processing on clusters and the scheduler-dependent files required to submit the jobs to the scheduler.
Scheduler dependent files
TMG Executive Menu requires multiple scheduler dependent files to communicate with a scheduler.
Scheduler configuration file
The scheduler configuration file defines the name of the scheduler so that the TMG Executive Menu can locate it.

Thermal-Flow
Contains general thermal and flow solver related documentation, such as the verification test cases, monthly critical fixes, DMP guide, and knowledge base articles.
- TMG thermal-flow solvers
  Maya HTT develops and maintains a thermal solver and a flow solver, which are combined into the TMG thermal-flow solvers. These solvers are included and distributed with Simcenter 3D, NX, and Simcenter Femap. Older versions of TMG thermal-flow solvers are also included in NX I-deas.
- Thermal and flow verification test cases
  Contains verification test cases for the thermal and flow solvers.
- Monthly critical fixes
  Lists critical bugs that are fixed monthly for the thermal and flow solvers.
- TMG Executive Menu
  TMG Executive Menu is a standalone application that lets you execute processes on thermal-flow files and solutions independently of Simcenter 3D or Simcenter Femap.
- Thermal and flow DMP guide
  Describes the general workflow for executing the simulation jobs using distributed memory parallel processing on clusters and the scheduler-dependent files required to submit the jobs to the scheduler.
  - Parallel processing on a cluster
    Using distributed memory architecture, the TMG thermal-flow solvers support high performance computing (HPC) for large models on a multi-node cluster. These solvers use Distributed Memory Parallel (DMP) processing based on domain decomposition and the message passing interface (MPI).
  - Executing DMP simulations
    The following workflow describes running DMP simulations. The TMG thermal-flow solvers installation, TMG Executive Menu, and required scheduler dependent files must be all accessible by the nodes in the cluster.
  - Submit a DMP simulation
    You submit a DMP simulation from the TMG Executive Menu, which is on a machine that has access to the solution input XML file and the scheduler. It is preferable to use the head node of the cluster, which is accessible from all the nodes.
  - Scheduler dependent files
    TMG Executive Menu requires multiple scheduler dependent files to communicate with a scheduler.
    - Scheduler configuration file
      The scheduler configuration file defines the name of the scheduler so that the TMG Executive Menu can locate it.
    - Submit job script
      TMG Executive Menu submits contiguous jobs to the scheduler by calling the submit job script, which defines how the jobs are distributed in the cluster and the order in which they are executed.
    - Delete job script
      The delete job script sends the simulation ID for the scheduler to delete a job from the queue.
  - A host file
    The scheduler generates the mayampi.hosts file at runtime before running the jobs in parallel. This file includes a list of cluster nodes that will execute the jobs.
- Thermal-flow data exchange files
  The thermal and flow solvers in Simcenter 3D and Simcenter Femap create multiple thermal-flow data exchange files described on the following page.

Scheduler configuration file

The scheduler configuration file defines the name of the scheduler so that the TMG Executive Menu can locate it.

This file also defines the name and path of the submit and delete scripts that send jobs to a queue, which distribute the jobs in a sequential order to the cluster. The queue executes the jobs when the resources you requested become available.

TMG Executive Menu uses the following scheduler configuration file parameters to set up the parallel processing:

<scheduler label> identifies the unique name for each scheduler.
<script> identities the type of job script: submit or delete, and the full path and name of the scripts.
(Optional) <timeout> sets the duration and the number of times that the solution monitor attempts to locate the DMP license.
(Optional) <duration> sets the length of time allotted for the monitor to detect the DMP license before cancelling the operation.
(Optional) <retries> sets the number of times allotted for the monitor to detect the DMP license before cancelling the operation.

To define more than one scheduler queue, you set unique labels for each additional scheduler in the <scheduler label> parameter.

Example

In this example, two queues are defined by setting two unique scheduler names for the scheduler labels: ”MyDesktop” and ”MyCluster". Each of them have their own submit and delete scripts.

<?xml version=”1.0” encoding=”utf-8”?>
<scheduler_info>
<scheduler label=”MyDesktop”>
<script type="submit" path="c:/tmg/exe/start_slave.bat"/>
<script type="delete" path="c:/tmg/exe/delete_slave.bat"/>
</scheduler>
<scheduler label=”MyCluster”>
<script type="submit" path="/shared_nfs/scripts/run_parallel_slave.sh"/>
<script type="delete" path="/shared_nfs/scripts/delete.sh"/>
</scheduler>
<timeout>
<duration seconds=”30”/>
<retries number=”10”/>
</timeout>
</scheduler_info>