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

Revision history [back]

click to hide/show revision 1
initial version

There is no way for generic components to be aware of the specific characteristics of your hardware / sensors, so yes, if you have a specific platform, and the ROS installation was not provided by the OEM / mfg, it's likely covariances (and similar properties) will be blank/zero/empty.

Seeing as the HSR is a platform, I'd be surprised though if some other user / group has not figured those out already. You might want to ask around on a HSR-focused forum or support channel. Those values may not be exactly right for your specific robot, but they would provide a good starting point.

There is no way for generic components to be aware of the specific characteristics of your hardware / sensors, so yes, if you have a specific platform, and the ROS installation was not provided by the OEM / mfg, it's likely covariances (and similar properties) will be blank/zero/empty.blank/zero/empty (unless whoever wrote the sensor/hw drivers has done work to identify them, and has configured those components to also publish them).

Seeing as the HSR is a platform, I'd be surprised though if some other user / group has not figured those out already. You might want to ask around on a HSR-focused forum or support channel. Those values may not be exactly right for your specific robot, but they would provide a good starting point.