Simulation runs represent individual executions of a simulator routine. When you trigger a simulation, CDF creates a run that tracks the execution status and results. You can list, filter, and retrieve runs, as well as access the input and output data for each run.Documentation Index
Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
Use this file to discover all available pages before exploring further.
What simulation runs are
A simulation run is a single execution instance of a simulator routine. It captures the configuration used, the inputs provided, the outputs produced, and the execution status (e.g., pending, running, completed, failed). Each run is a record of what happened during that execution.Executing and monitoring runs
You trigger simulations by creating or starting runs. Once a run is in progress, you can poll its status to monitor completion. After a run finishes, you can retrieve the output data and use it in downstream workflows or analytics.Simulation runs can be long-running. Use status polling or notifications to track progress instead of blocking until completion.
Key operations
- Create and start: Trigger new simulation runs.
- List and filter: Find runs by status, routine, or other criteria.
- Retrieve: Get run details, including inputs and outputs.
- Access data: Read input and output data associated with each run.