Jack O'Quin
Jack O'Quin
The basic concept seems good. But, especially for new `sensor_msgs` entries, the exact proposal deserves considerable review. We can do that here, but some discussion on `[email protected]` seems appropriate. Specifically,...
Opened a mailing list thread here: https://groups.google.com/forum/#!topic/ros-sig-drivers/QgCL__X5isw
How do you distinguish a front semi-circle (`-Pi/2 .. Pi/2`) from a rear semi-circle with the same angles?
That seems better. With the Velodyne driver we ended up using two parameters: `view_direction` and `view_width` (which is a 2D constraint). Some did not agree with that approach, but 360...
Why is `sensor_msgs` a better location than some new package name, like `marker_msgs`?
> I know there are other similar message out there but that's exactly a issue why I like to proposed a set of marker messages. ar_track_alvar_msgs are not supporting sensor...
+1 for the package name `fiducial_msgs`. I agree with Tully that "marker" already has other meanings within the ROS eco-system.
Where was `OdometryWithAcceleration` discussed? I can't find it.
The pull request above fixes one instance. I suspect there are more.
OK. All the more reason to update the tutorials and examples. They are badly out of date.