Display the same fields tf_echo does on the command line but in an rqt widget:
The time of the transform and the approximate time which the transform was looked up is shown, so a transform that is not getting updated and falling behind in the buffer can be detected. In the above example the tf time is 0.0 because a static tf is being looked up.
Individual fields can be hidden with a right click context menu (though those are masked by the context menu of the line edit boxes), and whether they are hidden will be saved in .perspective files. The source and target frames are also saved and restored.
There are toolTips for each field, though I find getting them to pop up inconsistent.
The only error output is the transform time label turns red when the transform is unavailable, I'll possibly add another field (that also can be hidden) with more verbose exception output.
TF buffer cache time will also be made configurable.
I could make the frames also have a dropdown with all the known frames, but I'd like to also make it possible to type in anything and I'm not sure if those two can be combined smoothly.
https://github.com/lucasw/rqt_tf_echo/
---
[Visit Topic](
https://discourse.ros.org/t/rqt-tf-echo/4271/1) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
%0A>%20%0A>%20The%20time%20of%20the%20transform%20and%20the%20approximate%20time%20which%20the%20transform%20was%20looked%20up%20is%20shown,%20so%20a%20transform%20that%20is%20not%20getting%20updated%20and%20falling%20behind%20in%20the%20buffer%20can%20be%20detected.%20%20%20In%20the%20above%20example%20the%20tf%20time%20is%200.0%20because%20a%20static%20tf%20is%20being%20looked%20up.%0A>%20%0A>%20Individual%20fields%20can%20be%20hidden%20with%20a%20right%20click%20context%20menu%20(though%20those%20are%20masked%20by%20the%20context%20menu%20of%20the%20line%20edit%20boxes),%20and%20whether%20they%20are%20hidden%20will%20be%20saved%20in%20.perspective%20files.%20%20The%20source%20and%20target%20frames%20are%20also%20saved%20and%20restored.%0A>%20%0A>%20There%20are%20toolTips%20for%20each%20field,%20though%20I%20find%20getting%20them%20to%20pop%20up%20inconsistent.%0A>%20%0A>%20The%20only%20error%20output%20is%20the%20transform%20time%20label%20turns%20red%20when%20the%20transform%20is%20unavailable,%20I'll%20possibly%20add%20another%20field%20(that%20also%20can%20be%20hidden)%20with%20more%20verbose%20exception%20output.%0A>%20%0A>%20TF%20buffer%20cache%20time%20will%20also%20be%20made%20configurable.%0A>%20%0A>%20I%20could%20make%20the%20frames%20also%20have%20a%20dropdown%20with%20all%20the%20known%20frames,%20but%20I'd%20like%20to%20also%20make%20it%20possible%20to%20type%20in%20anything%20and%20I'm%20not%20sure%20if%20those%20two%20can%20be%20combined%20smoothly.%0A>%20%0A>%20https://github.com/lucasw/rqt_tf_echo/%0A>%20%0A>%20%0A>%20%0A>%20%0A>%20%0A>%20---%0A>%20%5BVisit%20Topic%5D(https://discourse.ros.org/t/rqt-tf-echo/4271/1)%20or%20reply%20to%20this%20email%20to%20respond.%0A>%20%0A>%20%0A>%20If%20you%20do%20not%20want%20to%20receive%20messages%20from%20ros-users%20please%20use%20the%20unsubscribe%20link%20below.%20If%20you%20use%20the%20one%20above,%20you%20will%20stop%20all%20of%20ros-users%20from%20receiving%20updates.%0A>%20______________________________________________________________________________%0A>%20ros-users%20mailing%20list%0A>%20ros-users@lists.ros.org%0A>%20http://lists.ros.org/mailman/listinfo/ros-users%0A>%20Unsubscribe:%20<http://lists.ros.org/mailman//options/ros-users>%0A>%20%0A>%20 "このメッセージに返信")
(text/plain)