-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Added Loopback Simulator Package #4006
base: main
Are you sure you want to change the base?
Conversation
@smitdumore, your PR has failed to build. Please check CI outputs and resolve issues. |
I think there's something funky happening with the frames here. The timerCallback should be publishing map->odom, but its actually publishing the |
@smitdumore, your PR has failed to build. Please check CI outputs and resolve issues. |
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.
Still quite a few problems, but getting closer!
rclcpp::Publisher<sensor_msgs::msg::LaserScan>::SharedPtr scan_publisher_; | ||
|
||
// tf | ||
std::unique_ptr<tf2_ros::StaticTransformBroadcaster> tf_broadcaster_; |
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.
These aren't static transforms, they should be using the TransformBroadcaster
instead
|
||
// Publishing updated position of odom and base_link wrt map | ||
publishTransform(relocalization_pose_, "map", "odom"); | ||
publishTransform(init_pose_.pose.pose, "map", "base_link"); |
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.
The transform it should be publishing is odom->base_link, the map->base_link should never be published. That breaks the TF tree. Its map->odom and odom->base_link. I think that largely invalidates the code above.
- Given the initial pose (map->base_link)
- Find the current odom->base_link transform (or just have it stored from the previous iteration)
- Back out the map->odom that keeps odom->base_link constant
- Publish that map->odom
Hey! Checking back in here - anything I can help answer? |
Hey Steve, |
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: