ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

yakirari's profile - activity

2016-11-09 13:19:43 -0500 received badge  Notable Question (source)
2016-11-09 13:19:43 -0500 received badge  Famous Question (source)
2014-06-16 16:48:41 -0500 received badge  Student (source)
2014-06-16 16:39:51 -0500 received badge  Popular Question (source)
2014-01-06 21:12:18 -0500 asked a question Loosing diagnostic messages

Hi, In our application we use the diagnostic_updater::Updater to send diagnostic messages using a callback definition through Updater::add (Add a DiagnosticTask embodied by a name and method to the DiagnosticTaskVector) version. We also use forced updates (force_update()). We see after each message the callback is being called.

We use rostopic echo to listen to the diagnostic topic, however we notice that not all messages arrive. The seq field is also fragmented on the missing messages. Is this something we are missing in the implementation or the usage (should we use some buffer or window size or is there some other mechanism to assure messages arrive)? Please advise. Thanks!

2013-12-05 07:46:16 -0500 answered a question Hardware requirement for starters?

Hi, I think it depends what you want to use the Kinect for and what other sensors you plan to use. If you want on board processing of the point clouds (RGBD etc...) for 3d reconstruction, I think you would need at least an I5-I7 like CPU, a strong GPU (>1G) and SSD (if you want to save more than a few seconds of data on the disk for debugging). If you need it for navigation, basically you need the best PC you can buy.

However, if you only want to read data, and process it somewhere else (or run some light algorithm on it), even an atom dual core can be O.K.