Challenge Overview
A heterogeneous traffic simulation benchmark.
HetroD Challenge v1.0 focuses on generating realistic heterogeneous closed-loop traffic simulation in dense urban scenes.
The benchmark emphasizes mixed-agent interaction, vulnerable road-user safety, and type-balanced evaluation instead of vehicle-only performance.
- Closed-loop rollout generation for vehicles, two-wheelers, and pedestrians.
- Hidden test evaluation with official HetroD metrics.
- Submission deadline: September 5, 2026 AoE.
Prize
Awards and certificates for the top three teams.
Certificate included.
Certificate included.
Certificate included.
Public Package
Train and validation GT are public; test GT is hidden.
- Train: 5087 scenarios with ScenarioNet inputs.
- Validation: 955 scenarios with ScenarioNet inputs.
- Test: 955 ScenarioNet-compatible inputs with future targets masked.
Submission
Submit one zipped folder of test rollouts.
Each submitted pickle must contain all required agents from metadata.required_agent_ids and 80 future steps in global (x, y, z, yaw) coordinates.
Challenge Timeline
Submit before the final deadline.
Develop
Train + validation
Use the public split and the GitHub evaluator for local validation.
Submit
September 5, 2026 AoE
Zip the test rollout folder and fill out the Google submission form.
Score
Hidden test evaluation
The organizers compute the final score with hidden test GT.
Files
Public data and evaluator layout.
The public package contains ScenarioNet inputs and GT pickles for train and validation; the test package contains inputs only.
HetroD-Challenge-v1.0-public/
train/{gt,scenarionet}/
valid/{gt,scenarionet}/
test/input/
manifests/
split_summary.json
Evaluation Metrics
Type-balanced metrics for heterogeneous interaction.
The official score combines kinematic realism, safety, cross-type interaction, and a quality-gated coverage bonus.
1. Kinematic
Realism by type.
- Linear Speed
- Linear Acceleration
- Angular Speed
- Angular Acceleration
2. Safety
Collision and valid region behavior.
- Collision with 0.1 m annotation tolerance
- Type-aware valid region margin
3. Cross-type Interaction
Close-range heterogeneous behavior.
- Cross-type distance proximity to GT
- Cross-type time-to-proximity proximity to GT
4. Coverage
Multi-rollout occupancy diversity.
- Rasterized BEV occupancy
- Type-wise average
- Quality-gated bonus
Submission
Submit one folder of scenario-level PKL files.
The final zip should contain exactly one rollout pickle for every scenario listed in manifests/test.txt.
your_team_submission.zip
your_team_submission/
<scenario_id_0>.pkl
<scenario_id_1>.pkl
...
{
"agent_id": ..., # [num_agents]
"simulated_states": ..., # [32, num_agents, 80, 4]
}
scenario_idis the top-level inputid.agent_idshould usemetadata.required_agent_ids.simulated_statesmust contain exactly 32 rollouts and store future steps 11..90 as(x, y, z, yaw).
Leaderboard
Placeholder leaderboard for hidden test evaluation.
Official rankings will report only the overall score and four major metric groups.
| Rank | Team | Overall | Kinematic | Safety | Cross-type | Coverage |
|---|---|---|---|---|---|---|
| Oracle | GT Reference | 0.897 | 1.000 | 0.992 | 1.000 | 0.000 |
| 1 | Team Placeholder | - | - | - | - | - |
| 2 | Team Placeholder | - | - | - | - | - |
| 3 | Team Placeholder | - | - | - | - | - |