-
From the top bar,
select , and then click the App Preferences
tab.
-
In the left-hand pane, select .
-
Expand the Execution options.
-
Select whether to Use fix seed and specify the
Number of seed.
Typically, you would set 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 set 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 simulation process level
setting.
Manually set the seed to a desired integer value in the corresponding 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.
-
Determine what level of messages you want processed for each job that runs. You
can define a threshold for the severity of messages you want to receive, and you
will receive information on that particular level, and all levels below it.
Processing more levels of log messages can impact how fast your simulation
process runs. From the Default logging level options,
select one of the following:
Option | Description |
---|
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. By default, this option is selected. |
Information |
These messages contain routine status or other informational items
that are not generally significant. |
Warning |
These messages indicate a condition that you should be aware of but
do not generally indicate a failure. |
Message |
These messages contain information pertinent to the app being run by
the adapter. Typically, these messages are related to the status of the
run. |
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. |
-
From the License mode options, select one of the
following licensing items:
- SimUnit credits
- SimUnit tokens
- Simulation tokens (On-premises only)
- Compute tokens (Cloud only)
The number of available credits or tokens appears next to each option.
If you use SimUnit credits or tokens and your study uses the physics simulation adapter, the
licensing cost of each design point decreases logarithmically as you add
design points. For more information about the different licensing options,
see the Simulation Licensing
Guide.
The preference selection is stored in CATSettings. To change the license mode
for a specific process while maintaining your preferences, see Setting Simulation Process Properties.
-
If you are connected to a cloud server, specify the License
pool.
The license pool manages the credits or tokens for jobs that are using 3DOrchestrate. The default license pool is the pool to which your rich client 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 cloud execution servers. See your system
administrator if you are unsure about which license pool to select.
-
Click OK to save the options and to exit the Preferences dialog box.
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.