Ask Your Question

Faster ar_track_alvar

asked 2013-04-14 15:17:39 -0500

jorge gravatar image

I'm playing around with ar_track_alvar package. I use it both to initialize amcl and to localize the docking station.

It works fine, but is a terrible CPU-hunger. I have changed the code to limit its frequency, but even at 8 Hz it's always taking around 60% of CPU, and my navi stack is suffering CPU starvation (and the laptop eventually switch off!).

Any suggestion for reducing the CPU usage? Maybe I should try the non-kinect version, but really I need a good depth estimation.

Another idea i'm thinking about is to make it a nodelet and load on the kinect nodelet manager... not sure if this helps reducing CPU usage, but I'm afraid it can slow down the fake laserscan.

Thank you a lot.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2013-04-19 17:01:56 -0500

jorge gravatar image

Well, this is not a solution, but I added dynamic reconfiguration with an enable/disable switch that subscribes/unsubscribes to pointcloud topic, what at the same time stops the (also very CPU-hungry) depth image to pointcloud nodelet. My fork

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2013-04-14 15:17:39 -0500

Seen: 569 times

Last updated: Apr 14 '13