Core/Universe Planning meeting 2022/04/06 #2510

mitsudome-r · 2022-04-06T13:40:46Z

mitsudome-r
Apr 6, 2022
Maintainer

Chaired by Ryohsuke

Review new discussion threads:

Documentation Updates

Go over previous action items:
- https://autowarefoundation.github.io/autoware-documentation/main/design/autoware-concepts/
- Goal should be enhanced
  - To what extent we implement logically functional components(Use cases) @mitsudome-r can prepare a draft next week
  - To what extent it should be real-time. @daniel to come up with a first draft

@xmfcx to prepare autoware_msgs design for Universe to be reviewed
- Fatih will create PRs for each message package.

Comments:

Kenji: if we are working on documentation, we should create an issue in the repo. @mitsudome-r to create an issue.
Logically functional components:
- We may detail out the testing method (simulator, real vehicle, log data)
- We should also think about the feature based evaluation (e.g. traffic light recognition accuracy)
Realtime framework
- What does it mean by "Autoware provides overrun handling to limit the resource use for each component "?
  - We should have a profiling to measure the resource that is "needed" for each component. If it exceeds the presumed limit, it should make sure that it does not distract other components.
  - What if the task is critical task? We need to have good analysis on what would be a safety critical processing pipeline.
- Message delivery.
  - We already have a topic monitoring tool to see if the message is delivered in time. Maybe we can start from there.
- For profiling and deadline miss detection, we might have to have a common implementation across all the packages.

Review key issues (if any)