-
Notifications
You must be signed in to change notification settings - Fork 17
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
handeye_server error tf2.ExtrapolationException: Lookup would require extrapolation into the future #2
Comments
Hi @pinakjani, thanks for the report! This is most likely due to [this line], which just hardcodes an offset. It was a quick hack to make it work, and it worked too well because I forgot to replace it with a proper implementation 🙈 The problem with using The proper way would be to replace it with a Would you feel like trying it out and creating a PR? |
Hi @marcoesposito1988 😃 , Thanks for your reply. Yes sure I will give it a try as you suggested and also test it with hardware and put in a PR. |
Hi @marcoesposito1988 , |
I am having this problem as well! Glad to see there is some work here I can refer to :) [handeye_server-2] [ERROR] [1733770289.002378773] [bam_BAMGPU.handeye_server]: Failed to get the tracking transform: Lookup would require extrapolation into the future. Requested time 1733770287.427184 but the latest data is at time 1733770287.243116, when looking up transform from frame [base_link] to frame [charuco_frame] |
Hi @marcoesposito1988,
I am running easy_handeye2 on ROS2 Humble with actual hardware. I have made the setup as suggested in the Readme launch files.
However, I see a tf2 extrapolation error as:
[handeye_server-12] tf2.ExtrapolationException: Lookup would require extrapolation into the future. Requested time 1691770862.861832 but the latest data is at time 1691770862.819078, when looking up transform from frame [dx400/base_link] to frame [dx400/ee_gripper_link]
The error narrows down to this function:
easy_handeye2/easy_handeye2/easy_handeye2/handeye_sampler.py
Line 87 in c788191
If I change the time argument to 0 sec in all the lookup_transform functions like below, It works fine. Is there a better fix of this error?
Thanks
The text was updated successfully, but these errors were encountered: