docs(ad-api): add motion api

[isamu-takagi]

Signed-off-by: Takagi, Isamu [email protected]

Description

Add motion API.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• [x] I've confirmed the contribution guidelines.
• [x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The Reviewers must check the checkboxes below before approval.

• [ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• [ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[github-actions[bot]]

Documentation URL: https://autowarefoundation.github.io/autoware-documentation/pr-154/ Modified URLs:

• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/api/motion/accept_start/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/api/motion/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/api/motion/state/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/api/planning/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/api/planning/steering_factors/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/api/planning/velocity_factors/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/list/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/types/autoware_ad_api_msgs/msg/motion_state/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/types/autoware_ad_api_msgs/msg/steering_factor/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/types/autoware_ad_api_msgs/msg/steering_factor_array/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/types/autoware_ad_api_msgs/msg/velocity_factor/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/types/autoware_ad_api_msgs/msg/velocity_factor_array/
• https://autowarefoundation.github.io/autoware-documentation/pr-154/design/autoware-interfaces/ad-api/types/autoware_ad_api_msgs/srv/accept_start/

[tkhmy]

@isamu-takagi Hi sorry, I have a question, how do we handle when the module publish multiple steering factor? Like the INTERSECTION, it will have multiple steering factors among the path, should we use the UUID that build by the RTC in order to add/remove the steering factor from the array? https://github.com/tier4/tier4_autoware_msgs/blob/tier4/universe/tier4_rtc_msgs/msg/CooperateStatus.msg#L2

[isamu-takagi]

@tkhmy I don't think UUID is required. The nearest is enough for HMI, and UUID is rarely used for visualization. It may be combined with the RTC to provide advanced functionality, but it can also be added afterward.

[isamu-takagi]

All conversations are resolved. Please approve if there are no other comments.