Running a Simulation

You can select the physics simulation model to run, and you can configure the execution options.

See Also
Configuring the Pre-Execution Options
Configuring the Post-Execution Options
  1. From the Applications section of the action bar, click Physics Simulation and drop it on the process diagram.
  2. Double-click Physics Simulation .
  3. From the Physics Simulation editor that appears, select the Execute tab.
  4. Do either of the following to select the object to simulate:
    • Select Content, and select the physics simulation object to run.
    • Select Parameter, and choose an object parameter representing the physics simulation object to run or create a new physics simulation object parameter.
  5. Optional: Select individual analysis cases:
    1. Select Select analysis cases to run.
    2. From the table, select individual analysis cases to run.
    3. Specify the configuration used to compute each analysis case:

      On the cloud only: The available configurations depend on the type of analysis case.
      On premises only: Enter the desired number of cores used to run each analysis case.

    If you do not select this option, the adapter runs all the analysis cases that are set as current in the simulation scenario. Analysis cases cannot be parameterized.

    Warning: Do not select individual analysis cases if the process will change the physics simulation object parameter to represent different simulations as it runs.

  6. Choose the number of physical Cores to be used to run the physics simulation.
  7. Select a solve Mode:
    OptionDescription
    Single-Solve Runs and saves the simulation. You can access the results after the simulation runs.
    Iterative (Low disk usage)

    Runs the simulation without saving. Each time this activity runs, the simulation runs and saves only output parameter values and result images (if options to generate images are selected). Full simulation results are not available.
    Iterative (High disk usage)

    Duplicates the simulation, creates a new branch, runs the simulation, and saves the results.

    Saving a copy helps you retain a history of the physics simulation after each iteration; however, the save operation increases memory and disk space consumption and decreases performance.

    You can use Collaborative Lifecycle Management to explore the evolution information of a duplicated simulation object.

    If a model parameter is mapped with an activity parameter in the Pre-Execution or Post-Execution tab, it is recommended to use publications.
  8. If you selected Iterative (High disk usage), do the following:
    1. Enter the Copy prefix for the copy of the simulation. You can also use parameter values for the Copy prefix. For example: ${Run_Number}.
    2. Optional: Create an object parameter that refers to the copy of the simulation.
    3. Optional: Select Delete simulation result to retain only the model and scenario contexts of the simulation.
  9. Optional: Do the following to generate an image file of each field plot created by the simulation. You can use the images to compare the output from different simulations in Results Analytics, for example.
    1. Select Generate images for each field plot.
    2. Enter the prefix for each field plot.
    3. Enter the camera view to be used to generate the images.
  10. Optional: To generate an image file of the history plots created by the simulation, select Generate images for history plot, and enter the name of the file.
    Automation Process Composer combines all the history curves into a single image file.
  11. Optional: To upload the images generated from these options to the content of this activity, select Upload generated images as content of this activity.

    Warning: Selecting this option with parallel optimization can cause failures and impact performance.

  12. Optional: For additional control over the performance, click Advanced and do the following:
    1. Select Run in persistent session mode to improve performance for a process iterating on the same 3DOrchestrate Station. Performance is improved by keeping the physics simulation loaded between invocations of the adapter; for example, between runs of a DOE, optimization, or loop.

      Note: If you run the Physics Simulation adapter with any of the flow adapters and select this option, the jobs run in parallel.

    2. Specify the Number of standard error messages to log to minimize the volume of standard error messages that Automation Process Composer writes to the job log.
    3. Specify the Number of standard output messages to log to minimize the volume of standard output messages that Automation Process Composer writes to the job log.
    4. Enter any shareable licenses that are required to run the batch utility. Separate multiple licenses with semicolons; for example, SMU.prd; DRD.prd.

      If you selected Run in persistent session mode, Automation Process Composer releases the licenses after all the iterations have completed.

      The batch utility tries to check out licenses in the order in which they are listed. If the first license listed is available, the batch utility starts running; if the first license is not available, the batch utility checks if the second license is available. As a result, not all the listed licenses may be checked out. The adapter tries multiple times if a license is not available.
  13. Optional: Select the shareable licenses required to run the simulation. For more information, see Shareable Licenses.
  14. Optional: If you use Simulation tokens for licensing, select Use embedded license for simulation to run simulations from Automation Process Composer using embedded tokens only. Embedded token licensing lets you run one simulation at a time and with the maximum number of cores specified for embedded licensing for your role. For more information, see About Embedded Licensing.

    You can specify the use of Simulation tokens for licensing from the Execution preferences for Simulation Process Modeling.

  15. Click Ok to save your changes and to close the Physics Simulation editor.