Martin Günther

> I looked at the source code, it looks like that the rosparam 'intensity' which can be given to the node upon lunching, is never used through out the source...

I'd recommend first repositioning the camera (or object) so that you look at it from an angle, not frontally. This might help getting more unique corner detections. For example, here...

This bug may be caused by #127.

The bug isn't just for empty comments, but seems to be *any* comments that are weirdly indented: ```text $ ros2 interface show actionlib_msgs/msg/GoalStatusArray --no-comments std_msgs/Header header builtin_interfaces/Time stamp int32 sec...

@SteveMacenski wrote: > I think having a message type for 2D segmentation from a typical 2D-AI segmentation algorithm would be valuable. It would be similar to image data but having...

To clarify: The field is `int64` in ROS1 kinetic and melodic, and `string` in ROS1 noetic and ROS2. About the mapping rules: It's easy to convert an `int64` into a...

> I'd say that in a setup where it bridges the old (int64) world and the new (string) world, it is fair to assume that IDs are (string-ified) numbers. Fair...

This happens for me too after I installed `ros-indigo-image-transport-plugins` via apt-get. And there's at least one other person with the same problem: http://answers.ros.org/question/243950/ros-libuvc_camera-stopped-working/ After removing *all* image transport plugins, `libuvc_ros`...

Actually, it turned out that this bug had a different cause in my case. I had written a syntactically invalid udev rule (forgot a comma), and this caused my webcam...

Correction: It wasn't my malformed udev rule; **it's actually running `libuvc_ros` with `ros-indigo-image-transport-plugins` installed that removes the video4linux device**! WTF? ### With `ros-indigo-image-transport-plugins` installed: ROS log: ``` [ INFO] [1484749169.134982418]:...