Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Best practice: tf::Listener should be a global or local variable?

asked 2015-06-03 16:03:08 -0500

Stephane Caron
5 ●3 ●3 ●5

Hi there,

I'm wondering: do tf::Listener or tf::Broadcaster variables take time to fire-up (e.g. because of topic subscription)?

It would be more convenient for me to declare a new tf::Listener whenever I need to lookup a tf (i.e. as a local variable), but I wonder if there are some performance issues in doing this.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2015-06-03 19:17:24 -0500

tfoote

58457 ●128 ●550 ●526 http://www.ros.org/

It's best for the tf::Listener or tf::Broadcaster to be members of a persistent class. They both require continuous operation. Broadcasters need to be remain constructed for as long as you're broadcasting. And listeners need time to receive messages before they are useful.

edit flag offensive delete link

add a comment

Question Tools

1 follower

Stats

Asked: 2015-06-03 16:03:08 -0500

Seen: 231 times

Last updated: Jun 03 '15

Best practice: tf::Listener should be a global or local variable? edit

1 Answer

Question Tools

Stats

Related questions

Best practice: tf::Listener should be a global or local variable?