ROS TF claims tree disconnected, but clearly connected
Hi all
I am playing back some rosbag file. In RVIZ, I see the error message "No transform from [area_description] to frame [start_of_service]". TF view_frames agrees and shows the following:
However, when I export the rosbag file, /tf topic only, to .csv format, I can clearly see that there are 3 kinds of transformations in the rosbag file: 1. map -> start_of_service 2. start_of_service -> device 3. area_description -> start_of_service Whereas the left side is the value in "field.transforms0.header.frame_id", and the right side is the value in "field.transforms0.child_frame_id" in the resulting .csv file.
Now, the resulting graph is acyclic. If we choose start_of_service as root, this is clearly a valid tree. The question remains: Is ROS able to invert the transformations so to form a valid TF tree?
Apologies if this has been asked before. I was unable to find an answer on google or here.
Cheers! - ibd