Ask Your Question
2

Diagnostic Updater Constructor and Nodelets

asked 2011-10-20 07:55:51 -0600

Chad Rockey gravatar image

I'm having a really difficult time using Diagnostic Updater. In general, the DiagnosedPublisher constructor is very strict and requires:

DiagnosedPublisher (const ros::Publisher &pub, diagnostic_updater::Updater &diag, const diagnostic_updater::FrequencyStatusParam &freq, const diagnostic_updater::TimeStampStatusParam &stamp)

which FrequenceyStatusParam requires: FrequencyStatusParam (double *min_freq, double *max_freq, double tolerance=0.1, int window_size=5)

and TimeStampStatusParam optionally requires: TimeStampStatusParam (const double min_acceptable=-1, const double max_acceptable=5)

And even worse, the diagnostic_updater::Updater seems to make its own Nodehandle, so you'll have to call init before declaring it.

It seems to be impossible to have one of these as a global variable outside of a class (example, in a C++ file with just a main and a few functions wrapping a non-ROS library). The only reasonable approach here seems to be keeping the diagnostics declarations within main and running with a while(ros::ok()){ros::spinOnce();} loop.

It also seems extremely difficult to initialize a DiagnosedPublisher member inside of a nodelet in an initialization list. This needs access to the nodehandle, but you cannot call getMTNodeHandle() or getMTPrivateNodeHandle() until the onInit() function in the nodelet.

Does anyone have a experience running diagnostics in these situations (or even better an example script and nodelet that use diagnostics)?

It's also possible that there are less-strict alternatives that I did not see looking through the API.

Thanks for your help.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
3

answered 2011-10-20 10:03:04 -0600

joq gravatar image

Did you try allocating it as a new class member pointer inside your onInit()?

edit flag offensive delete link more

Comments

Thanks Jack! The eventual, super easy solution was to use a boost shared pointer, and reset or make shared in the onInit. This is what I get for learning Java first years ago. ;)
Chad Rockey gravatar imageChad Rockey ( 2011-10-25 09:53:39 -0600 )edit

Your Answer

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

Add Answer

Question Tools

Stats

Asked: 2011-10-20 07:55:51 -0600

Seen: 506 times

Last updated: Oct 20 '11