Skip to content
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

Closed
3 of 5 tasks
isamu-takagi opened this issue Jan 25, 2023 · 4 comments
Closed
3 of 5 tasks

Create api for visualization #3225

isamu-takagi opened this issue Jan 25, 2023 · 4 comments
Assignees

Comments

@isamu-takagi
Copy link
Contributor

isamu-takagi commented Jan 25, 2023

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

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
  • pointcloud map
  • vector map
  • traffic signal
  • detection objects
  • detection area
  • trajectory

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

  • Create specification.
  • Create default implementation.
@isamu-takagi isamu-takagi transferred this issue from autowarefoundation/autoware.universe Jan 25, 2023
@tkhmy
Copy link

tkhmy commented Jan 31, 2023

Object Recognition

  • The message will be get from /perception/object_recognition/objects
  • Objects
    • UUID object_id
    • float existence_probability
    • ObjectClassification classification
      • uint8 label
      • float probability
    • PredictedObjectKinematics kinematics
      • initial_pose_with_covariance
      • initial_twist_with_covariance
      • initial_acceleration_with_covariance
      • predicted_paths
    • Shape shape
      • uint8 type
      • Polygon footprint
      • Vector3 dimensionsl

@tkhmy
Copy link

tkhmy commented Jan 31, 2023

Detection Area

  • Show the area of the autoware that currently looking at.
  • Most of the topic publish is in MarkerArray, I suggest we convert to Shape when in api

@isamu-takagi
Copy link
Contributor Author

@tkhmy autowarefoundation/autoware_adapi_msgs#26
I created a general shape message. I think it can be used for both visualization and detection areas.

@tkhmy
Copy link

tkhmy commented Feb 24, 2023

#3232 (comment)

I think we need to have an api that publish current max velocity. And put in under this topic
/api/planning/max_velocity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants