Runtime Workflow
The runtime workflow uses prebuilt Docker images and precompiled binaries for the worker and client. Both the worker and client must be running; the viewer is optional.
The Quickstart section provides end-to-end examples that follow this workflow.
Workflow overview
Calibration runs independently of this workflow. See Calibration for details.
1. Create a map (GIS pipeline)
Use the GIS pipeline to generate a USD map from OpenStreetMap or CityGML source data:
See the GIS Pipeline guide for full instructions.
2. Start the worker
From the package root on the worker host:
This starts the Digital Twin worker along with the Iceberg catalog, S3 bucket (MinIO), and supporting infrastructure.
3. Create a configuration file
Use the configuration builder APIs to author or modify simulation YAML files:
See the Config Builder API for parameter details.
4. Run the simulation
The simulation management API supports starting, stopping, pausing, resuming, and querying simulation status.
Database exploration
After a simulation completes, use these scripts to inspect and extract results:
Next steps
- EM Simulations — step-by-step batched EM quickstart
- RAN Simulations — step-by-step batched RAN quickstart
- Development Workflow — modify source and rebuild when prebuilt binaries are not sufficient