These settings are used to manage multiple simulations that are typically launched using Study Cases.
NOTE: When a simulation is launched with .NET code, where no Aurora UI is present, the settings to run Study Cases or Risk Iterations in parallel will be ignored. The study will run, but processing will take place sequentially instead.
This option ensures that all Study Cases and Risk Iterations are run one after another. No child processes will be launched as parallel processes if this box is selected.
This option splits up the selected Study Cases and processes them using parallel child processes to better make use of multiple processor cores. If no Study Cases are selected, the simulation will issue a warning and process the study sequentially.
This option splits up the number of requested Risk Iterations across the available processor cores. If a risk run is not enabled, this option will generate a warning and run the study sequentially.
This setting combines xmpSQL (.xdb) output from the parallel runs into a single database. If you are running parallel runs and this checkbox is empty, individual databases are created for each of the processes. Non-.xdb data types and individual databases are created for each iteration/study case (child process) in the specified location. A process number is appended onto the end of the database name. SQL Server output will automatically be placed in the same database.
Multiple Simulations
For further assistance, please contact Aurora Support.
Copyright© 1997-2024 Energy Exemplar LLC. All rights reserved.