General Job Submission Script Requirements
When running a design study, the Design Manager server passes specific instructions to each design simulation. These instructions are communicated via files that are written to the temporary directory .mdxruntime that is located in the same directory as the project artifact directory. When a design simulation is submitted to the cluster scheduler, the Design Manager server executes the user job submission script in the temporary directory .mdxruntime/$project/$study/$design. The .mdxruntime/$project/$study/$design directory contains all the files that Design Manager requires to execute the design simulation.
The Design Manager server does not interact with the job scheduler on your cluster. For this reason, in the job submission script, you must read the following files from .mdxruntime/$project/$study/$design and redirect them to the Design Manager server:
- dm_design_execute_options.txt
This file contains additional command line options, such as license details, and other options that you define in the design study settings.
- dm_design_output_info.msg
This file contains the name of the log file that Design Manager expects to be available when the design simulation executes.
Within your job submission script, you must change to the job working directory and read these two files using the
cat
command.
Example
The following example shows a general job submission script for tcsh (Tenex-C-Shell):
|
This example script code checks for the files
dm_design_execute_options.txt and
dm_design_output_info.msg and assigns the content to two
independent variables. The STARTCASE
variable contains the
additional command line options and the CASELOG
variable contains
the name of the log file. These two variables are then used when calling Simcenter STAR-CCM+ at the end of the script.
Note | For other Unix shells, such as bash, you must modify the syntax accordingly. |