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

[Collision monitor] Publish collision_monitor state on a ROS topic. #3496

Closed
kaichie opened this issue Mar 21, 2023 · 3 comments
Closed

[Collision monitor] Publish collision_monitor state on a ROS topic. #3496

kaichie opened this issue Mar 21, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@kaichie
Copy link
Contributor

kaichie commented Mar 21, 2023

Feature request

Feature description

Publish collision_monitor state on a ROS topic.

Currently, the collision_monitor package only prints the Action state on the terminal, it will be useful to publish this as a message so that other parts of the system can use this information.

Implementation considerations

The proposed feature should add a new publisher that publishes the state as a ROS topic. Depending on the level of details required, it should at least publish:

  • action_type (<int> DO_NOTHING=0, STOP=1, SLOWDOWN=2, APPROACH=3)

and/or more of the following fields:

  • velocity: the requested velocity that the current state is reporting
  • polygon_name: the name of the polygon that is currently activated
  • points: the points of the polygon that is currently activated

If more information is required beyond the action_type, we probably want to create a new nav2 msgs and also update the Action struct to store more of these informations.

@SteveMacenski SteveMacenski added the enhancement New feature or request label Mar 21, 2023
@SteveMacenski
Copy link
Member

Sounds reasonable!

I don't think velocity is as important as the cmd_vel is going to contain that velocity as the normal output. The polygon name might be helpful context, I agree!

@BriceRenaudeau
Copy link
Contributor

This issue isn't closed?

@SteveMacenski
Copy link
Member

Thanks!

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

No branches or pull requests

3 participants