-
Notifications
You must be signed in to change notification settings - Fork 197
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
Add Tf2 versions of lookupTransform, lookupVelocity, setTransform #728
base: rolling
Are you sure you want to change the base?
Conversation
Signed-off-by: kyle-basis <[email protected]>
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.
@tfoote do you mind to take a look ?
tf2/include/tf2/buffer_core.h
Outdated
TF2_PUBLIC | ||
geometry_msgs::msg::VelocityStamped lookupVelocity( | ||
const std::string & tracking_frame, const std::string & observation_frame, | ||
const TimePoint & time, const tf2::Duration & averaging_interval) const; | ||
|
||
/** \brief Lookup the velocity of the moving_frame in the reference_frame | ||
* \param reference_frame The frame in which to track |
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.
update docs
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.
I think I've fixed this
Only test fails are due to linting - do y'all have a script to fix this automatically? |
I think you can run |
Linting fixed - not sure why tf2_rospy is failing on jenkins, though |
This PR implements #726 - see there for initial discussion.
Some notes:
*Tf2
.lookupVelocity
- tf2 doesn't have a dual vector type that I can find, and I didn't really want to implement a newVelocity
for this PR. I'm happy to back that part of the change out - the function can be moved wholesale intotf2_ros
when the time comes, instead, as it's not part ofBufferCoreInterface
.toMsg
into one reimplementation - it really shows that the interface is wrong here in the first place - the helper methods that should be used would cause a depedency loop.child_frame_id
- I think I did the correct thing, but it might be worth introducing somehow.I'm unable to actually run the tests - I get an error oncolcon build