`maciej@CIT-MACIEJ-U:~/ros/src/cam_lidar_calibration$ roslaunch lidar_camera_calibration find_transform.launch
... logging to /home/maciej/.ros/log/e47b7c64-62f2-11ea-bdc4-1cbfce10fd3f/roslaunch-CIT-MACIEJ-U-28257.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
process[find_transform-1]: started with pid [28287]
Size of the frame: 4096 x 3072
Limits: -2.5 to 2.5
Limits: -4 to 4
Limits: 0 to 1.7
Number of markers: 2
Intensity threshold (between 0.0 and 1.0): 0.0004
useCameraInfo: 0
Projection matrix:
[6450.6245, 0, 2181.8992, 0;
0, 6454.645, 1507.1038, 0;
0, 0, 1, 0]
MAX_ITERS: 100
Lidar_type: Velodyne
initial rotation: 1.57 -1.57 0
initial translation: 0 0 0
[ INFO] [1583861555.387857303]: Reading CameraInfo from configuration file
`
As advised in #79 i made sure that the name of the topic in the find_transform.launch is correct. My topics:
maciej@CIT-MACIEJ-U:~/ros$ rostopic list /cam0/camera_info /cam0/image_raw /cam0/image_raw/compressed /cam0/image_raw/compressed/parameter_descriptions /cam0/image_raw/compressed/parameter_updates /cam0/image_raw/compressedDepth /cam0/image_raw/compressedDepth/parameter_descriptions /cam0/image_raw/compressedDepth/parameter_updates /cam0/image_raw/theora /cam0/image_raw/theora/parameter_descriptions /cam0/image_raw/theora/parameter_updates /diagnostics /lidar_camera_calibration_rt /rosout /rosout_agg /scan /velodyne_nodelet_manager/bond /velodyne_nodelet_manager_cloud/parameter_descriptions /velodyne_nodelet_manager_cloud/parameter_updates /velodyne_nodelet_manager_driver/parameter_descriptions /velodyne_nodelet_manager_driver/parameter_updates /velodyne_nodelet_manager_laserscan/parameter_descriptions /velodyne_nodelet_manager_laserscan/parameter_updates /velodyne_packets /velodyne_points
mac137
commented
4 years ago
as in the title. The output below:
`maciej@CIT-MACIEJ-U:~/ros/src/cam_lidar_calibration$ roslaunch lidar_camera_calibration find_transform.launch ... logging to /home/maciej/.ros/log/e47b7c64-62f2-11ea-bdc4-1cbfce10fd3f/roslaunch-CIT-MACIEJ-U-28257.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://CIT-MACIEJ-U:37839/
SUMMARY
PARAMETERS
NODES / find_transform (lidar_camera_calibration/find_transform)
ROS_MASTER_URI=http://localhost:11311
process[find_transform-1]: started with pid [28287] Size of the frame: 4096 x 3072 Limits: -2.5 to 2.5 Limits: -4 to 4 Limits: 0 to 1.7 Number of markers: 2 Intensity threshold (between 0.0 and 1.0): 0.0004 useCameraInfo: 0 Projection matrix: [6450.6245, 0, 2181.8992, 0; 0, 6454.645, 1507.1038, 0; 0, 0, 1, 0] MAX_ITERS: 100 Lidar_type: Velodyne initial rotation: 1.57 -1.57 0 initial translation: 0 0 0 [ INFO] [1583861555.387857303]: Reading CameraInfo from configuration file `
As advised in #79 i made sure that the name of the topic in the find_transform.launch is correct. My topics:
maciej@CIT-MACIEJ-U:~/ros$ rostopic list /cam0/camera_info /cam0/image_raw /cam0/image_raw/compressed /cam0/image_raw/compressed/parameter_descriptions /cam0/image_raw/compressed/parameter_updates /cam0/image_raw/compressedDepth /cam0/image_raw/compressedDepth/parameter_descriptions /cam0/image_raw/compressedDepth/parameter_updates /cam0/image_raw/theora /cam0/image_raw/theora/parameter_descriptions /cam0/image_raw/theora/parameter_updates /diagnostics /lidar_camera_calibration_rt /rosout /rosout_agg /scan /velodyne_nodelet_manager/bond /velodyne_nodelet_manager_cloud/parameter_descriptions /velodyne_nodelet_manager_cloud/parameter_updates /velodyne_nodelet_manager_driver/parameter_descriptions /velodyne_nodelet_manager_driver/parameter_updates /velodyne_nodelet_manager_laserscan/parameter_descriptions /velodyne_nodelet_manager_laserscan/parameter_updates /velodyne_packets /velodyne_pointsand in my find_transform.launch file I have:
remap from="/image_raw" to="/cam0/image_raw"/>any help would be hugely appreciated