While implementing a costmap plugin for work that behaves similar to the StaticLayer, I noticed a (possibly) missing return; in StaticLayer::incomingUpdate() for when the current frame and the incoming update's frame do not match. I say possibly because the logging seems to indicate that this is necessary, but this omission could also be intentional.
Basic Info
Info
Please fill out this column
Ticket(s) this addresses
(add tickets here #1)
Primary OS tested on
(Ubuntu, MacOS, Windows)
Robotic platform tested on
(Steve's Robot, gazebo simulation of Tally, hardware turtlebot)
Does this PR contain AI generated software?
(No; Yes and it is marked inline in the code)
Description of contribution in a few bullet points
Description of documentation updates required from your changes
Future work that may be required in bullet points
For Maintainers:
[ ] Check that any new parameters added are updated in docs.nav2.org
[ ] Check that any significant change is added to the migration guide
[ ] Check that any new features OR changes to existing behaviors are reflected in the tuning guide
[ ] Check that any new functions have Doxygen added
[ ] Check that any new features have test coverage
[ ] Check that any new plugins is added to the plugins page
[ ] If BT Node, Additionally: add to BT's XML index of nodes for groot, BT package's readme table, and BT library lists
While implementing a costmap plugin for work that behaves similar to the
StaticLayer, I noticed a (possibly) missingreturn;inStaticLayer::incomingUpdate()for when the current frame and the incoming update's frame do not match. I say possibly because the logging seems to indicate that this is necessary, but this omission could also be intentional.Basic Info
Description of contribution in a few bullet points
Description of documentation updates required from your changes
Future work that may be required in bullet points
For Maintainers: