This guide will walk you through running your first simulation with the VaVAM driver policy, interpreting the results, and understanding the output structure.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/NVlabs/alpasim/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before starting, ensure you have completed the onboarding setup with all dependencies installed.Run your first simulation
Set up your environment
Run the setup script to compile protos, download an example driver model, and install the This will ensure you have a valid Hugging Face token and prepare your environment.
alpasim_wizard command line tool:Run the wizard
Execute the wizard to create necessary config files, download the scene (if necessary), and run a simulation:This creates a
tutorial/ directory with all necessary config files and runs the simulation.The wizard uses VaVAM as the default driver policy. The first run will download the required scene from Hugging Face.
Understanding the results
The simulation creates a comprehensive output structure in thetutorial/ directory:
Key directories
rollouts/
rollouts/
Contains logs of simulation behavior for each rollout, used to analyze AV behavior and calculate metrics. Organized as
rollouts/{scene_id}/{batch_uuid}/.Key files:rollout.asl: Messages exchanged within the simulation (useful for debugging)metrics.parquet: Per-rollout evaluation metrics{clipgt_id}_{batch_id}_{rollout_id}.mp4: Evaluation videos_complete: Marker file indicating successful rollout completion
aggregate/
aggregate/
Contains aggregated results across all rollouts:
metrics_results.txt: Formatted table of driving scores (mean, std, quantiles)metrics_results.png: Visual summary of driving quality metricsmetrics_unprocessed.parquet: Combined metrics from all rolloutsvideos/: Videos organized by violation type (collision, offroad, etc.)
Configuration files
Configuration files
Various YAML files provide insight into the simulation configuration:
wizard-config.yaml: Config used by the wizard after applying Hydra inheritancegenerated-user-config-{ARRAY_ID}.yaml: Expanded simulation configtrafficsim-config.yaml: Traffic simulation configurationgenerated-network-config.yaml: Service port mappings
Example directory structure
Basic debugging
The console contains logs from all microservices and is the first place to look when something goes wrong. If therollouts directory does not appear or other errors occur:
- Check the console logs to identify where the first errors occurred
- Review the
wizard-config.yamlfor configuration issues - Ensure all services started successfully
Try a different driver policy
Once you’ve successfully run your first simulation, try running with the Alpamayo-R1 model:The Alpamayo-R1 model is large (10B parameters). Ensure your GPU has sufficient capacity to run it.
Next steps
Customize simulations
Learn how to configure scenes, driver policies, and runtime parameters
Operations guide
Performance tuning, troubleshooting, and advanced usage