Skip to content

Operational Design Domain working group

Jump to bottom
Diego Yabuki edited this page Mar 28, 2025 · 43 revisions

Operational Design Domain working group

The Operational Design Domain Working Group (ODD WG) is responsible for defining the Operational Design Domain, its use cases and test scenarios. This Working Group collaborates with the core autonomous driving development Working Groups to generate the following work products tailored to each application domain:

  • ODD definition: the conditions under which Autoware should operate safely
  • ODD use cases: specific operational situations that can happen within the intended ODD.
  • Test scenarios: sequences of events that compose an ODD use case. Test scenarios are tested weekly on TIER IV's CI/CD pipeline (Evaluator).

Working group leader(s)

  • @diegoyabuki Diego YABUKI (TIER IV)

Working group goals

The goals of the Operational Design Domain Working Group are:

  1. Establish the design process for defining Operational Design Domain and its scenarios
    • Investigate literature on ODD definition and ODD based development
    • Create and agree upon the ODD definition template
    • Design process for defining supporting scenarios for the ODD
    • Reach consensus on machine readable format of the scenarios
  2. Support the application domain Working Groups in the definition of ODDs and use cases
    • Fill in the ODD template with appropriate parameters
    • Investigate literature on ODD based development and Continuous Integration
  3. Create test scenarios based on the ODDs to be validated
    • Understand existing scenario examples and build a more comprehensive deck
    • Write all the necessary scenarios in the machine readable format
    • Conduct scenario simulation weekly and feedback the result to the relevant working groups

Current activities and how to contribute (WIP)

Achievements since July, 2020

Scenario Tool Summary

  • [Autoware Evaluator (CI/CD pipeline)]

    • Cloud based DevOps (integration of the development tools including the scenario editor and the scenario simulator below)
    • A product from TIER IV and offered for the official Autoware Foundation projects like Cargo Delivery and Public Road Bus, etc.
    • The user guide is available TIER IV document site
    • As it consumes AWS resource, the (batch) weekly execution of the scenario simulation is managed by the Software/ODD WG leads

  • [Scenario Simulator V2 (Scenario testing framework)]

  • The GUI Scenario editor

    • Web based GUI scenario editor freely available from TIER IV
    • You can create and export scenarios with this web interface
    • The user guide is available TIER IV document site

  • [TIER IV account]

    • The working group members who are interested in creating and testing scenarios are advised to create a free TIER IV account here. If you already have a TIER IV account, you cn skip this step.
    • Once you have created your TIER IV account, please let @Igata-ctrl know the e-mail address used for the registration and first/last names. After @Igata-ctrl registered your TIER IV account to the AWF ODD group in the Evaluator (CI/CD pipeline), you can go to AWF Autoware Evaluator page to see the simulation results, create/edit scenarios, etc.

Meeting minutes

See the discussions ith the meeting:odd-wg label. Dates are in (GMT+9:00) JST (Japan Standard Time).

Archived Meeting minutes from Gitlab

  • The ODD working group shared folder for discussion material is here. Please click the "ask for permission" button or contact Diego Yabuki if you do not have access to the folder and/or any of the files in there.

  • We have another shared folder to publicly share the discussion result, use cases, ODD definitions here

How to participate in the working group

Weekly meeting information

The ODD working group meets weekly on a fixed time slot. Depending on the circumstances of contributors, we can discuss new time slots or change to a flexible schedule.

  • ODD WG meetings are held in the following single time slot.

    • 7:00am, Monday (PDT) / 6:00am, Monday (PST) US Pacific Time
    • 10:00am, Monday (EDT) / 9:00am, Monday (EST) US Eastern Time
    • 4:00pm, Monday (CEDT) / 3:00pm, Monday (CEST) Poland time
    • 5:00pm, Monday (TRT) Turkey time
    • 10:00pm, Monday (CST) Taiwan time
    • 11:00pm, Monday (JST) Japan Time

To receive calendar invites to the working group's meetings, join the Operational Design Domain working group's meeting invite group. Being a member of this group will ensure you receive calendar invites for all working group meetings. However you do not need to be a member of this group to participate in meetings or working group activities.

You can also look at the Autoware Foundation's events calendar for when the upcoming meetings will be held. If you use Google Calendar, you can subscribe to this calendar directly to have it displayed alongside your own calendar events. To do this, click the "+ Google Calendar" link in the bottom right corner of that site. Note that this will not add the events to your own calendar, meaning you may not receive notifications about meetings starting soon. For those not using Google Calendar, you can add the calendar to your own by downloading it as an ICS file and importing that into your calendar software.

The Operational Design Domain working group may announce meetings on the ROS Discourse in the Autoware category. Keep an eye on that category for meeting announcements, then simply join the meeting to participate.

Discussion

Discussion for the Operational Design Domain working group happens in the following places.

Clone this wiki locally