Simulation Runs

Every time a simulation routine executes, a simulation run object is created. This object ensures that each execution of a routine is documented and traceable. Each run has an associated simulation data resource, which stores the inputs and outputs of a simulation run, capturing the values set into and read from the simulator model to ensure the traceability and integrity of the simulation data.

Simulation runs provide a historical record of the simulations performed, allowing users to analyze and compare different runs, track changes over time, and make informed decisions based on the simulation results.

When simulation run load balancing is enabled and the routine is not assigned to any particular simulator integration, the run initiates with status queued and any active simulator integration can claim it automatically. Without load balancing, the run initiates with status ready and is tied to the simulator integration specified on the routine.

Limitations:

• A retention policy is in place for simulation runs, allowing up to 100000 entries. When this limit is reached, the oldest runs are deleted to make room for new ones.
• The total size of all inputs for a simulation run can be a maximum of 50.00 KB.
• The total size of simulation run data sent by the connector can be a maximum of 100.00 KB.