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
The first line in the log here is shown for reference, it is what a normal ROS log message looks like. The following lines come from tf2/src/buffer_core.cpp. In that file you can see it is using something called "logWarn()", but apparently this is not connected to the normal ROS logging when used via the older TF API.
[INFO] [WallTime: 1374596992.623081] No target received yet.
Warning: Invalid argument passed to canTransform argument target_frame in tf2 frame_ids cannot be empty
at line 122 in /tmp/buildd/ros-hydro-tf2-0.4.5-0precise-20130721-0218/src/buffer_core.cpp
The text was updated successfully, but these errors were encountered:
This is important to me because rosconsole log messages can be made to tell you what node is emitting the error message. Since everything in the whole system uses TF (and thus now TF2), I have no idea where this error is coming from.
Error: Invalid argument passed to canTransform argument target_frame in tf2 frame_ids cannot be empty
at line 122 in /home/tfoote/work/geometry_experimental/src/geometry_experimental/tf2/src/buffer_core.cpp
[ERROR] [1376692168.915507885]: Invalid argument passed to lookupTransform argument target_frame in tf2 frame_ids cannot be empty
Showing rosconsole working properly for the
I've explicitly changed libtf2.so to link against rosconsole_bridge.so but I'm still not getting the output on rosout. @isucan any suggestions?
The first line in the log here is shown for reference, it is what a normal ROS log message looks like. The following lines come from tf2/src/buffer_core.cpp. In that file you can see it is using something called "logWarn()", but apparently this is not connected to the normal ROS logging when used via the older TF API.
The text was updated successfully, but these errors were encountered: