Ask Your Question

dseifert's profile - activity

2017-09-11 12:33:38 -0500 received badge  Nice Answer (source)
2016-11-10 02:52:03 -0500 received badge  Enthusiast
2016-11-09 05:17:58 -0500 answered a question error with rostopic echo -p

This is a bug that was addressed in https://github.com/ros/ros_comm/issue... and should be fixed in ros-kinetic-ros-comm 1.12.6

2016-11-09 05:11:42 -0500 commented question error with rostopic echo -p

Same issue here.

2016-08-18 19:28:12 -0500 received badge  Good Answer (source)
2016-08-18 19:28:12 -0500 received badge  Enlightened (source)
2016-08-18 13:20:53 -0500 commented question Publisher sleeping forever

Maybe /use_sim_time is active but no bag is played? This would mean that time does not go forward and hence the sleep would never expire.

2016-08-18 10:58:33 -0500 received badge  Nice Answer (source)
2016-08-18 09:53:41 -0500 answered a question Last node handle goes out of scope but callbacks still work. Why?

If you look at https://github.com/ros/ros_comm/blob/... , the Subscriber keeps a copy/reference to the node handle. So as long as it exists, there is yet another referenced handle that will prevent the node to shut down.

2015-10-22 09:17:28 -0500 received badge  Teacher (source)
2015-10-20 03:18:37 -0500 commented question raise IOError("could not find %s on the ros package path" % msg_pkg_name). Ros is not capable to find a package in the ros_package_path

Did you source your workspace's setup.bash?

2015-10-20 03:13:07 -0500 commented answer How to set and access local parameters when launching a nodelet?

I would assume each nodelet is in a different namespace, and so would be the parameters.

2015-10-14 02:05:21 -0500 answered a question How to set and access local parameters when launching a nodelet?

To pass a parameter value to a nodelet, try either passing it as an argument on the command line when you run the executable that loads the nodelet (i.e. "_param:=value") or set the parameter using ros::param::set("~param", value).

In either case the nodelet should be able to access it using getPrivateNodeHandle().getParam("param", value).

2015-10-14 01:08:04 -0500 received badge  Supporter (source)