pgorczak's profile - activity

Correct! As long as you're using the devel space, catkin generates the file you mentioned via a cmake macro. When it is

The less command does not receive the color control chars because it is not a terminal. Not sure if you can pipe output

I could get the latest version to install on OS X Yosemite with brew install pcl --HEAD

Some more discussion in a related question.

On OS X Yosemite, the normal brew install pcl failed as well for me. Adding --HEAD did the trick again.

Having the same issues here. "niReg -l" still lists libXnVFeatures.so and libXnVHandGenerator.so as "compiled with OpenNI 1.0.0.22" when installing ros-groovy-openni-tracker (so these come with the system dependency libopenni-nite-dev). For a listing of the output see Kel Guerin's post.

As a side note, after uninstalling rospkg, rosinstall and rosdep using pip, I had to reinstall the system packages python-rospkg, python-rosinstall and python-rosdep (with apt-get install --reinstall).

Are you sure the camera is running? Try to have openni_launch openni.launch up at the time you run openni_tracker. If the camera is working properly, you should be able to see an image with image_view. If you walk around in front of it, openni_tracker should give output then.

Hi andyw, I was able to find a workaround for the "oparation invalid" issue which you can find in my updated post (the one you linked to).

First I'll try to elaborate a bit on the already mentioned points:

1. Basic Linux and especially Ubuntu
   • Getting used to using the windows and workspaces relevant shortcuts (in Unity, hold SUPER/WINDOWS)
   • Knowing what apt-get does and how it works
   • Knowing how to set up ssh connections using keys
2. Using the terminal
   • Getting familiar with TAB completion and history
   • Know the basic shortcuts CTRL+C, CTRL+ALT+T, CTRL+SHIFT+T, CTRL+(+|-|0)

What also helped me:

1. Having a basic knowledge of threads and their hazards (especially relevant for C++)
2. Getting familiar with version control systems and their underlying concepts
   • git, subversion and mercurial are all used in ROS repositories
   • Focus on one and use it for your projects (git works best for me)

The first exception is not harmful as you can see here.

When I am using roslaunch openni_launch openni.launch, I also get messages like:

[ERROR] [1346317018.377804268]: Tried to advertise a service that is already advertised in this node [/camera/depth_registered/image_rect_raw/compressedDepth/set_parameters]
[ERROR] [1346317018.384694527]: Tried to advertise a service that is already advertised in this node [/camera/depth_registered/image_rect_raw/compressed/set_parameters]
[ERROR] [1346317018.413763705]: Tried to advertise a service that is already advertised in this node [/camera/depth_registered/image_rect_raw/theora/set_parameters]
(...)
[ WARN] [1346317020.499849507]: Camera calibration file (...)/rgb_A00364A06244047A.yaml not found.
[ WARN] [1346317020.500131130]: Using default parameters for RGB camera calibration.
[ WARN] [1346317020.500289570]: Camera calibration file (...)/depth_A00364A06244047A.yaml not found.
[ WARN] [1346317020.500426152]: Using default parameters for IR camera calibration.

Still, everything works just fine (image_view and rviz) so those shouldn't be the issue.

I think running only image_view like in your first edit and still getting the freeze pretty much rules out a performance issue--at least concerning rviz. I think (I'm not sure though) the point cloud only gets computed when you subscribe to the points topic which would mean there is pretty much nothing going on computationally when you just display an image with image_view.

You could also try a different Kinect device or make sure your Kinect works e.g. on Windows with the OpenNI examples to make sure there is no problem with the device itself.

And my last question would be: What is your version of ROS and your operating system (version)? I'm using ubuntu 12.04 with fuerte and it worked with the OpenNI-packages I got with sudo apt-get install ros-fuerte-openni-camera.

You could try the driver from openni_camera_deprecated just to see if it gives you different output or some hints on what's going on.

Kinect launch file using openni_camera/OpenNINodelet (deprecated version of the driver):

<launch> 
    <node pkg="nodelet" type="nodelet" name="openni_manager" output="screen" respawn="true" args="manager"/>
    <node pkg="nodelet" type="nodelet" name="openni_launch" args="load openni_camera/OpenNINodelet openni_manager" respawn="true">
        <!--<param name="rgb_frame_id" value="camera_rgb_optical_frame" />-->
        <!--<param name="depth_frame_id" value="camera_depth_optical_frame" />-->
        <param name="depth_registration" value="true" />
        <param name="image_mode" value="VGA_30Hz" />
        <param name="depth_mode" value="VGA_30Hz" />
        <param name="debayering" value="EdgeAwareWeighted" />
        <param name="depth_time_offset" value="-0.055" /> <!-- Taken from TurtleBot's kinect.launch -->
        <param name="image_time_offset" value="0" />
    </node>
</launch>

I've also run into that ticket but I think there is some confusion between the "timeout" error and the "operation is invalid" one. Everyone getting the latter one is actually getting past the part where the timout error might occur. But still, I hope someone dealt with it already...