-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Deprecates use of geometry_msgs/PoseArray for particle cloud in AMCL #2281
Conversation
cloud_msg->poses[i].position.y = set->samples[i].pose.v[1]; | ||
cloud_msg->poses[i].position.z = 0; | ||
cloud_msg->poses[i].orientation = orientationAroundZAxis(set->samples[i].pose.v[2]); | ||
cloud_with_weights_msg->particles[i].pose = (*cloud_msg).poses[i]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You deleted the population of the particle could poses / weights for the one that's keeping too... I thought you tested this in rviz?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then where is the particle cloud in that image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-read that code, its very clear that you're not populating the poses or the weights from just removing that full for statement
cloud_with_weights_msg->particles[i].pose = (*cloud_msg).poses[i];
cloud_with_weights_msg->particles[i].weight = set->samples[i].weight;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dumb mistake, does f21bed8 correct it?
Codecov Report
@@ Coverage Diff @@
## main #2281 +/- ##
==========================================
- Coverage 85.09% 84.94% -0.15%
==========================================
Files 258 258
Lines 12798 12780 -18
==========================================
- Hits 10890 10856 -34
- Misses 1908 1924 +16
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, waiting on CI!
You have a linting problem |
Still linting issues :-) |
Could I may be get the line numbers where my PR fails the lint test? Suggestions to prevent general lint issues are also welcome. I presume ROS2 uses |
If you go into the circle CI job that failed right below, it tells you very directly
Please lint locally, you'd catch this too with |
was incorrectly deleted in 0ca93b5
commandline tool used: ament_uncrustify --reformat src/navigation2/nav2_amcl/src/amcl_node.cpp
Originates from Not sure how to fix this .. |
Must have been a flaky run, but the other test build in release mode passed so we can skip it |
Thanks for the help! |
…os-navigation#2281) * removed geometry_msgs/PoseArray in AMCL, updated rviz configs * ParticleFilter -> ParticuleCloud * put back adding of weights and poses for particles was incorrectly deleted in 0ca93b5 * complies with linter's max line length ros-navigation#2281 (comment) * reformatted file using ament_uncrustify commandline tool used: ament_uncrustify --reformat src/navigation2/nav2_amcl/src/amcl_node.cpp
Basic Info
Description of contribution in a few bullet points
particlecloud_pub_
of typegeometry_msgs/PoseArray
particlecloud_pub_->on_activate()
andparticlecloud_pub_->on_deactivate()
Description of documentation updates required from your changes
PoseArray
Future work that may be required in bullet points
For Maintainers: