-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create api for visualization #3225
Comments
Object Recognition
|
Detection Area
|
This was referenced Feb 8, 2023
@tkhmy autowarefoundation/autoware_adapi_msgs#26 |
Closed
7 tasks
7 tasks
I think we need to have an api that publish current max velocity. And put in under this topic |
This was referenced Mar 6, 2023
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Description
Now Autoware doesn't have a visualization API. Here we define the visualization API for services. The visualization interface for debugging should be defined as component interface internally, see here for it.
Purpose
Clarify the interface for visualization.
Possible approaches
Define these interfaces.
Vehicle
Some information can be obtained from vehicle status. 3D model of the vehicle if necessary.
pointcloud map
Pointcloud map may be enough for debugging. Do you have a use case to show in your service?
Vector map
Provide polygons instead of
visualization_msgs/msg/MarkerArray
. The design is application dependent.Active traffic signal
Use RTC status to get the decision of traffic signal. See here for details.
For image recognition result and v2x input, create internal interface for debugging later.
Definition of done
The text was updated successfully, but these errors were encountered: