- From the search menu in the Top Bar, search for and select the simulation activity to modify.
- From the navigation pane, select Execution Options.
- From the Execution Options page
toolbar, select Edit.
- Choose from the available basic options in the Configure the Execution Run Options page:
- Cleanup: Choose whether to keep the files that the activity creates in the execution directory. If you choose to remove the
files, Process Composer deletes all of the files, folders, and subfolders in the execution directory.
- Execute this Activity: Choose whether to run this activity.
- Monitor Files: Choose whether to run a service on the 3DOrchestrate Station that is used by the Simulation Companion app. In most cases, you should accept the default option of False.
Use Fast-Flow Execution: Improve the performance of the subflows under a Process Composer (Native) process adapter. Fast-flow execution is available only for an empty activity or an activity containing an Optimization, DOE, Monte Carlo, or Loop process adapter. When the subflow contains function adapters that run rapidly (such as the Calculator, OS command,
or Excel adapters), this option improves performance by executing the
entire submodel on a single 3DOrchestrate Station. Executing the submodel on a single station reduces the amount of
network activity during distributed execution by the 3DOrchestrate. However, if an adapter in the subflow does not run rapidly (in less than one second), selecting
fast-flow execution is unlikely to improve performance. For example, if
the subflow contains an Abaqus adapter, selecting this option may limit
the availability of parallel computing resources and slow down the
execution of the subflow. In addition, you should select fast-flow
execution only when affinities do not prevent the function adapters in a
subflow from executing on a single station. Affinities: If you enter an affinity, your job will be dispatched
only to 3DOrchestrate Stations that have this affinity (as configured by your system administrator).
For example, you could have a 3DOrchestrate Station that is used to run Nastran that has been given an affinity of
Nastran. Predefined affinities include
the station name, OS type, OS name, OS version, and OS architecture. You
can enter an expression that refers to a parameter in the
Custom affinities field; for example,
${PARAMETER[Parameter
Name]}. By default, a 3DOrchestrate Station has no custom affinities. You use the Location
Group affinity to specify the working directory. When the
simulation activity runs, Process Composer generates output in a directory below the default working directory,
where the name of the directory is prefixed by the location group that you
entered.Simulation activities with the same location group will run
on the same 3DOrchestrate Station and generate output in same directory (under the working directory).
Conversely, activities with different location groups will generate
output in different directories and can run on different 3DOrchestrate Stations, provided there are no other affinities forcing them to use the same
station.
- Choose from the available advanced options in the Configure the Execution Run Options page.
- Maximum Run Time: Specify a limit (in seconds of wall-clock time), after which execution of the simulation activity will be terminated. In most cases, you should accept the default value of 0, meaning no time limit is enforced. However, if you are concerned the simulation activity will encounter issues that will not allow it to complete, you should specify a value that is much longer then the expected execution time (to prevent incorrect termination of the activity).
- Save Iteration History: Choose True to save the results of the execution (parameters) to the 3DOrchestrate database.
Max Batch Size: Configure the maximum number of parallel simulations that
will be submitted at one time while the activity is executing. For
example, if you run an activity containing a Design of Experiments
adapter that will run 100 simulations (where every design point is known
and can be run independently), Process Composer can submit them all of the simulations at one time and potentially
consume every available 3DOrchestrate Station. The maximum batch size activity option, with a default value of
four, protects against consuming all available stations.
However, you are not guaranteed that every algorithm will reach the maximum batch size. Most optimizers will not reach a high maximum batch size, and the actual batch size is often a function of the
number of design variables.
- When you have configured the simulation activity's execution options, click Done.
Process Composer stores the configuration.
|