-
Notifications
You must be signed in to change notification settings - Fork 917
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
ROS1 recent feature port #613
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
de19931
navsat_transform diagram to address #550 (#570)
mabelzhang 07ee6c2
Fix frame id of imu in differential mode, closes #482
ayrton04 c954475
Added local Cartesian option to navsat_transform
ayrton04 b4017d2
Fix navsat_transform issue with starting on uneven terrain
ayrton04 b079b73
Fix typo in navsat_transform_node.rst (#588)
togaen 08d7fca
Fix sign error in dFY_dP in transfer function jacobian
ayrton04 fe2a8b0
Making repeated state publication optional (#595)
ayrton04 0009b57
PR feedback
ayrton04 a9b7fb2
Fixing build issues
ayrton04 792c6c6
Fixing stamp issues
ayrton04 c127759
Linting and uncrustifying
ayrton04 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Do you really want to set the clock? This would make it so that you always use the ROS clock and not the other options.
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.
If you launched a test with
use_sim_time
it would use ROS timeThere 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.
If you don't set it, it defaults to
RCL_SYSTEM_TIME
, right? And if I don't set this, the code throws an exception, because we end up comparing the current message time stamp (which is in ROS time) with this, which is in system time.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.
Wouldn't the tests automatically do that?
Also, is this not like ROS1? Does ROS time not == system time for a live system, and sim time in bags?
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.
Just linking this so we're talking about the same stuff. You obviously have been working with ROS2 a lot more than I have, so apologies if I have this wrong.
https://design.ros2.org/articles/clock_and_time.html
This is just like ROS1. The problem here is that if you don't provide constructor arguments, you'll get the second constructor signature here:
https://docs.ros2.org/foxy/api/rclcpp/classrclcpp_1_1Time.html
https://docs.ros2.org/foxy/api/rclcpp/classrclcpp_1_1Time.html#a683d5111f099d16532f10fcd82e8f5af
That means an uninitialized
rclcpp::Time
object will default toSYSTEM_TIME
, as I read it. And that was the issue: the newlast_published_stamp_
was not being initialized with a different constructor, so it was defaulting toRCL_SYSTEM_TIME
, but we later compared it to a message stamp, which is obviously going to be of typeRCL_ROS_TIME
. That throws an exception, causing all my tests to fail.In any case, tests are now all passing. 🥳