Skip to content

Conversation

BriceRenaudeau
Copy link
Contributor

@BriceRenaudeau BriceRenaudeau commented Apr 7, 2023

This is related to ros-navigation/navigation2#3519 change

Copy link
Collaborator

@AlexeyMerzlyakov AlexeyMerzlyakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the pull request description and reference to the original PR3519 from Nav2 where it related to, to have the proper history.

The "limit" is not a polygon type (as "Polygon" or "Circle"). It is new safety behavior (or action type, also used in the parameters and mentioned in the documentation), so please correct the description at migration guide.

Also, please add the LIMIT safety behavior (action type) to the CM's configuration page (configuration/packages/configuring-collision-monitor.rst).

@BriceRenaudeau
Copy link
Contributor Author

Thanks for your review.

Copy link
Collaborator

@AlexeyMerzlyakov AlexeyMerzlyakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@SteveMacenski SteveMacenski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 small changes and this LGTM for when I review / approve the main PR itself. Sorry for the delay

@SteveMacenski SteveMacenski merged commit 8c4ba70 into ros-navigation:master May 23, 2023
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

Successfully merging this pull request may close these issues.

3 participants