You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into this doing exact time syncs which dropped all the messages out of a node doing tf transform lookups in python, the looked up transforms had stamps that were slightly off from the stamp I requested to be looked up and I was putting them into output messages assuming they were the same.
I don't know if this is correct PyObject usage but a partial solution is here, I can turn it into a PR, cover ros::Duration conversion as well:
And there must be converters going the other direction from C++ to python with probably the same problem- but I didn't see them after a quick look. And maybe some other similar time converters exist in other packages?
The text was updated successfully, but these errors were encountered:
This converts the time into floating point in order to translate from python rostime to C++ rostime, and nanosecond precision is lost:
https://github.com/ros/geometry2/blob/noetic-devel/tf2_py/src/tf2_py.cpp#L150-L161
I ran into this doing exact time syncs which dropped all the messages out of a node doing tf transform lookups in python, the looked up transforms had stamps that were slightly off from the stamp I requested to be looked up and I was putting them into output messages assuming they were the same.
I don't know if this is correct PyObject usage but a partial solution is here, I can turn it into a PR, cover ros::Duration conversion as well:
lucasw@26feffa
And there must be converters going the other direction from C++ to python with probably the same problem- but I didn't see them after a quick look. And maybe some other similar time converters exist in other packages?
The text was updated successfully, but these errors were encountered: