Execution

The execution options let you customize options such as using a fixed seed and the default logging level for the Automation Process Composer and Optimization Process Composer apps.

The preferences define the initial values for new simulation processes. You can control the values after you create the simulation process using the Simulation Process Properties.

Use fixed seed

Manually specifies the seed to an integer value in the Number of seed field. The seed is used to initialize a random number generator used in various adapters (for example, optimization genetic algorithms and stochastic methods). If this option is not selected, the seed is determined randomly.

Typically, you would specify the seed to be a fixed value when you run a process multiple items and remove the randomness to compare results consistently. You can also specify the seed value for individual process adapters that use this option (for example, optimization) using the adapter's editor. The adapter-level seed setting always overrides the level setting of the simulation process.

Default logging level

Determines the level of messages processed for each job executed. You can define a threshold for the severity of messages to receive information on that particular level and all levels below it. Processing more levels of log messages can impact how fast your simulation process executes.

The following levels are available:

  • Debug. These messages are intended for debugging system or adapter code. Typically, these messages are meaningful only to program developers. This level can produce a large quantity of messages that can affect system performance. This is the highest level. Selecting this option sends all five types of messages to your log file.
  • Information. These messages contain routine status or other informational items that are not generally significant.
  • Warning. These messages indicate a condition to be aware of, but generally do not indicate a failure.
  • Message. These messages contain information pertinent to the app run by the adapter. Typically, these messages are related to the status of the execution.
  • Error. These messages indicate an error condition caused by usage, operational data, or some other condition that can be corrected.
  • SysError. These messages indicate a software system failure. They may indicate that some part of the infrastructure has become unusable (for example, a database has gone down) or they may indicate a programming error. Report these errors to system administrators for analysis. This is the lowest level. Selecting this option sends only system error messages to your log file.

By default, This preference is selected.

License pool

If you are connected to a cloud server, specify the License pool.

This preference specifies the license pool that manages the execution tokens for jobs that are using 3DOrchestrate. The default license pool is the pool to which your native app is connected. If you select a license pool other than the default, the job execution uses the licensing tokens from the selected license pool; however, the job execution takes place on the private 3DOrchestrate station that is connected to the same license pool on which you submitted the job. Only the license pools to which you have access are listed.

This option is available only for execution servers on the cloud. See your system administrator if you are unsure about which license pool to select.

License Mode
Determines the licensing model to be used to check out tokens or consume credits:
  • SimUnit tokens
  • Simulation tokens (On-premises only)
  • Compute tokens (Cloud only)