Add collision detector documentation#451
Add collision detector documentation#451SteveMacenski merged 11 commits intoros-navigation:masterfrom
Conversation
|
Done I believe. Sorry if it's not as verbose as you would wish but I really need to move on with this contribution; it took much more time than expected |
configuration/packages/collision_monitor/configuring-collision-monitor-node.rst
Outdated
Show resolved
Hide resolved
configuration/packages/collision_monitor/configuring-collision-monitor-node.rst
Show resolved
Hide resolved
|
otherwise LGTM in general, but I'll let @AlexeyMerzlyakov review as well when he's back from vacation |
SteveMacenski
left a comment
There was a problem hiding this comment.
I'll let Alexey approve the content of the subpages with the changes, but LGTM structurally
configuration/packages/collision_monitor/configuring-collision-monitor-node.rst
Outdated
Show resolved
Hide resolved
configuration/packages/collision_monitor/configuring-collision-detector-node.rst
Outdated
Show resolved
Hide resolved
configuration/packages/collision_monitor/configuring-collision-detector-node.rst
Outdated
Show resolved
Hide resolved
configuration/packages/collision_monitor/configuring-collision-detector-node.rst
Outdated
Show resolved
Hide resolved
|
One last thing from me - add an entry in the migration guide page for the new node to show off to the users! |
Added for Jazzy and Iron, so now we have to backport to Iron 😄 |
|
Just @AlexeyMerzlyakov 's comments left but I'm happy when he is |
AlexeyMerzlyakov
left a comment
There was a problem hiding this comment.
One nitpick comment and it is ready to-go
| ****************************************************** | ||
|
|
||
| In this `PR #3693 <https://github.com/ros-planning/navigation2/pull/3500>`_ A new node was introduced in the nav2_collision_monitor: Collision Detector. | ||
| It works similarly to the Collision Monitor, but does not affect the robot's velocity. It will only inform that data from the configured sources has been detected within the configured polygons via message to the ``collision_detector_state`` topic. No newline at end of file |
There was a problem hiding this comment.
... that might be used by any external module (e.g. switching LED or sound alarm in case of collision).
| ****************************************************** | ||
|
|
||
| In this `PR #3693 <https://github.com/ros-planning/navigation2/pull/3500>`_ A new node was introduced in the nav2_collision_monitor: Collision Detector. | ||
| It works similarly to the Collision Monitor, but does not affect the robot's velocity. It will only inform that data from the configured sources has been detected within the configured polygons via message to the ``collision_detector_state`` topic. No newline at end of file |
There was a problem hiding this comment.
| It works similarly to the Collision Monitor, but does not affect the robot's velocity. It will only inform that data from the configured sources has been detected within the configured polygons via message to the ``collision_detector_state`` topic. | |
| It works similarly to the Collision Monitor, but does not affect the robot's velocity. It will only inform that data from the configured sources has been detected within the configured polygons via message to the ``collision_detector_state`` topic that might be used by any external module (e.g. switching LED or sound alarm in case of collision). |
ros-navigation/navigation2#3500