The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Velodyne does not provide identically formatted information for all their models. Mostly for that reason, the driver design includes translating the information it needs into a common YAML format. See the design review discussions for details.
The gen_calibration.py script will generate the desired YAML file from your device-specific db.xml.
The params/32db.yaml included with the driver was generated in that way from an example 32E device. Several other 32E devices seemed to share the same calibration. I don't know if they are all the same, or just some of them. It seems reasonable to assume that using your specific calibration will improve accuracy, or at least not hurt. Please try it and report your results here.
The best way to measure accuracy I know is to find some features in the real world that stand out clearly, physically measure their distances, and compare with the generated point cloud. Rviz has a tool to determine the coordinates of specific points in a cloud.
The Velodyne has no RGB camera like that on the Kinect, so camera calibration does not apply.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
