Ask Your Question

GUI does not show up in stereo calibration of flea3 cameras [closed]

asked 2013-12-04 14:11:13 -0500

Artem gravatar image

updated 2014-01-01 23:40:32 -0500

I am having a weird but familiar case. I have two PGR flea3 cameras. I can and have calibrated each of them separately. The problem is when I'm starting stereo calibration, the GUI does not pop up. Here is my launch file to brinup cameras

        <rosparam command="load" file="$(find stereo_cameras)/config/cameras.yaml" />
        <group ns="stereo">
                <node name="left" type="camera1394_node" pkg="camera1394" output="screen" required="true">
                      <remap from="camera" to="left" />

                <node name="right" type="camera1394_node" pkg="camera1394"  output="screen" required="true">
                      <remap from="camera" to="right" />

The launch file for calibration looks like this

    <arg name="size" default="8x6" />
        <arg name="square" default="0.108" />
        <arg name="approximate" default="0.01" />
        <node pkg="camera_calibration" type="" name="stereo_calibration"
                        ns="stereo" args="--size $(arg size) --square $(arg square) --approximate=$(arg approximate)"
                        output="screen" required="true">
                <remap from="left" to="left/image_raw" />
                <remap from="right" to="right/image_raw" />
                <remap from="left_camera" to="left" />
                <remap from="right_camera" to="right" />

Executing cameras_bringup.launch I have

    left (camera1394/camera1394_node)
    right (camera1394/camera1394_node)

auto-starting new master
process[master]: started with pid [11560]

setting /run_id to b9a0d960-5d51-11e3-beea-eca86bfc8b0d
process[rosout-1]: started with pid [11573]
started core service [/rosout]
process[stereo/left-2]: started with pid [11585]
process[stereo/right-3]: started with pid [11620]
[ WARN] [1386209134.899914621]: Comparing 00b09d0100af32c9 to 00b09d0100b74b85
[ WARN] [1386209134.900099256]: GUIDs do not match
[ WARN] [1386209134.900147869]: Comparing 00b09d0100af32c9 to 00b09d0100af32c9
[ INFO] [1386209134.951435715]: Found camera with GUID 00b09d0100af32c9
[ INFO] [1386209134.951697053]: camera model: Point Grey Research Flea3 FL3-U3-13S2C
[ WARN] [1386209134.952958893]: Comparing 00b09d0100b74b85 to 00b09d0100b74b85
[ INFO] [1386209134.989864418]: Found camera with GUID 00b09d0100b74b85
[ INFO] [1386209134.990097120]: camera model: Point Grey Research Flea3 FL3-U3-13S2C
[ INFO] [1386209135.002538371]: [00b09d0100af32c9] opened: 1280x960_mono8, 30 fps, 800 Mb/s
[ INFO] [1386209135.002863321]: camera calibration URL: package://flea3_camera/config/flea3l_calib.yaml
[ INFO] [1386209135.017054405]: [00b09d0100b74b85] opened: 1280x960_mono8, 30 fps, 800 Mb/s
[ INFO] [1386209135.017601128]: camera calibration URL: package://flea3_camera/config/flea3r_calib.yaml

and stereo_calibration.launch I get this


 * /rosdistro
 * /rosversion

    stereo_calibration (camera_calibration/


core service [/rosout] found
process[stereo/stereo_calibration-1]: started with pid [2657]
Waiting for service /stereo/left/set_camera_info ...
Waiting for service /stereo/right/set_camera_info ...

after that no calibration GUI shows up.

I am on hydro, ubuntu 12.04. The computer is new, I have not tried other cameras here. With other cameras and on a different machine such kind of problem occurred when cameras were not synchronised, that time adding approximate = 0.1 helped, but not here.

Does anyone have ideas what could be the issue?

Thanks in advance!

  • Edit Still haven't resolved it yet. It is weird that the same launch and config files work fine on my Macbook. I tend to believe it is a hardware issue, as I am using Intel NUC. Moreover on macbook I don't even use software approximation. What it could be?
edit retag flag offensive reopen merge delete

Closed for the following reason too localized by Artem
close date 2014-05-27 07:00:41


I just ran into this same problem. I guess it's not "too localized"...

Cerin gravatar imageCerin ( 2015-05-10 19:35:54 -0500 )edit

Btw, the problem for me was that my cameras were unsynchronized. To fix it I had to pass --approximate=0.1 to camera_calibration.

Cerin gravatar imageCerin ( 2015-05-10 20:32:59 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2014-05-27 05:53:29 -0500

Dani C gravatar image

updated 2014-05-27 05:55:29 -0500

I don't know if this can help:

edit flag offensive delete link more


Thanks .

Artem gravatar imageArtem ( 2014-05-27 07:00:01 -0500 )edit

Question Tools



Asked: 2013-12-04 14:11:13 -0500

Seen: 903 times

Last updated: May 27 '14