The Autoware Foundation
2026-04-13 ODD working group weekly meeting (284) #7013
diegoyabuki
started this conversation in
Working group meetings
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Attendees
Agenda/Minutes
Weekly Simulation Results
March 15, 2026
Urban-Dense catalog on branch "scenario-dev": 66/81 scenarios passed.
public road bus catalog on branch "main": 321/329 scenarios passed.
March 22, 2026
Urban-Dense catalog on branch "scenario-dev": 68/81 scenarios passed.
public road bus catalog on branch "main": 320/329 scenarios passed.
March 29, 2026
Urban-Dense catalog on branch "scenario-dev": 70/81 scenarios passed.
public road bus catalog on branch "main": 321/329 scenarios passed.
April 05, 2026
Urban-Dense catalog on branch "scenario-dev": 70/81 scenarios passed.
public road bus catalog on branch "main": 322/329 scenarios passed.
April 12, 2026
Urban-Dense catalog on branch "scenario-dev": 69/81 scenarios passed.
public road bus catalog on branch "main": 323/329 scenarios passed.
Updated Summary of Failures
Fixed failures
Ego did not back up: Ego did not back up as intended.
Could not initialize localization: Requested the service "/api/localization/initialize" 30 times, but was not successful.
Could not engage: The simulator attempted to request Autoware to engage, but was aborted because Autoware's current state is INITIALIZING | WAITING_FOR_ROUTE | PLANNING.
Ego collides with vehicle moving on target lane after right turn: Ego collides with vehicle running on lane after right turn.
Simulation timed out: "map" passed to lookupTransform argument target_frame does not exist.
Simulator health check failed: Test execution succeeds, but the simulator health check fails.
Autoware does not reach state WAITING_FOR_ROUTE: Simulator waited for the Autoware state to transition to WAITING_FOR_ROUTE, but time is up. The current Autoware state is INITIALIZING.
Autoware does not reach state WAITING_FOR_ENGAGE: Simulator waited for the Autoware state to transition to WAITING_FOR_ENGAGE, but time is up. The current Autoware state is PLANNING.
Expected failures
Ongoing failures
Excess deceleration: Failed with excess deceleration (Non-deterministic case).
Insufficient avoidance margin: Ego got too close to NPC/Pedestrian laterally.
Bicycle collides with ego: Bicycle NPC collides with ego.
Cannot perform avoidance: Ego could not avoid a stationary NPC.
Collision during avoidance: Ego collides with static obstacle during avoidance (insufficient lateral clearance).
Ego stuck outside drivable area: Drivable area looks appropriately enhanced, but EGO stops for "Outside (of) Drivable Area".
Vehicle collision: Ego collided with a vehicle NPC.
SIGSEGV in freespace planner: Freespace planner error after avoidance completion.
SIGABRT in start planner: Error in start planner (could be similar to SIGSEGV in freespace planner.
Ego cannot find path to depart from parking lot: Ego gets stuck in the parking lot.
Could not call clear_route API: Requested the service "/api/routing/clear_route" 30 times, but was not successful.
change_to_stop API not ready: Service "/api/operation_mode/change_to_stop" is not ready after 180 seconds.
Could not call change_to_stop API: Requested the service "api/operation_mode/change_to_stop" 30 times, but was not successful.
New failures
Obstacle cruise virtual wall temporarily shifted back: The virtual wall shifted back, causing ego to slow down.
MPT failure: Bad alloc in Model Predictive Trajectory stack.
MRM virtual wall: MRM comfortable stop wall keeps appearing during driving.
Trajectory topic timed out: /planning/trajectory topic is timeout. Set ERROR in diagnostics.
MRM comfortable stop triggered: /adapi/mrm_request/delegate diagnostic is in ERROR state.
Ego slowed down too much: Ego slowed down too much when following preceding vehicle.
velocity_limit API not ready: Service "/api/autoware/set/velocity_limit" is not ready after 180 seconds.
Trajectory topic rate MRM: Diagnostic "/autoware/planning/topic_rate_check/trajectory" error triggered MRM.
Inaccurate arrival position: Ego arrival position is too far from the destination point.
Invalid message request: Simulator failed with message "attempting to request a message part outside the valid range".
Scenario Results Since Last TSC
- 1x Ego stuck outside drivable area
- 3x SIGABRT in start planner
- 1x Ego stuck outside drivable area
- 1x SIGABRT in start planner
- 1x SIGSEGV in freespace planner
- 1x Ego stuck outside drivable area
- 1x SIGABRT in start planner
- 1x Ego stuck outside drivable area
This Week's Discussions
Admin
Task Progress
Detailed progress is tracked on our Github Project.
Roadmap Phase 3 ongoing tasks:
Formalization and documentation of scenario generation process: ongoing (Task)
ODD definition for Truck WG: ongoing (Task)
Roadmap Phase 4 ongoing tasks:
Map conversion of SafetyPool to SSv2 (NTU): ongoing (Task)
Scenario conversion of SafetyPool to SSv2: ongoing (Task)
Previous MoM
https://github.com/orgs/autowarefoundation/discussions/6980
Action Items
Documents
Tools
Web.Auto Evaluator
Web.Auto Scenario Editor
TIER IV account
Scenario Simulator V2
Administrative
Please check the ODD WG wiki page.
This and other AWF periodic meetings can be checked on the Autoware Foundation events calendar. You can also add your contact to the ODD WG meeting invitation group to receive invitations for future meetings.
ODD WG meetings are held weekly in the following single time slot.
Beta Was this translation helpful? Give feedback.
All reactions