How xiaoliangabc/lidar_camera_calibration works
Project Type and Purpose
• This is a ROS‐based calibration toolkit (“lidar_camera_calibration”) that performs both intrinsic (camera) and extrinsic (LiDAR‐camera) calibration using a chessboard target. It consists of multiple ROS nodes written in C++ (with optional MATLAB integration) and supporting configuration/visualization assets.
File Structure Analysis
• Top‐level:
• CMakeLists.txt, package.xml ⇒ ROS package boilerplate
• README.md ⇒ high‐level overview
• Directories:
• launch/ ⇒ ROS launch files for each calibration stage
• src/ ⇒ C++ node implementations:
– data_generate.cc
– camera_calibration.cc
– lidar_chessboard_detector.cc
– lidar_camera_calibration.cc
– manual_calibration.cc
– rviz_command_button.cc
• /lidar_camera_calibration/ ⇒ node headers & utility functions
• /cppoptlib/ ⇒ embedded optimization library (solvers)
• cfg/, param/ ⇒ dynamic‐reconfigure & YAML params
• rviz/, matlab/ ⇒ RViz layouts & MATLAB script for intrinsic calibration
• Key patterns:
• ROS publisher/subscriber + dynamic reconfigure
• Modular node per calibration stage
• Optimization library (cppoptlib) used for two‐stage extrinsic calibration
Main Components
• ROS Master
• Nodes:
1. data_generate (collects image + LiDAR cloud pairs)
2. camera_calibration (intrinsic; C++ wrapper or MATLAB script)
3. lidar_chessboard_detector (plane detection in point clouds)
4. lidar_camera_calibration (auto‐optimization of extrinsics)
5. manual_calibration (GUI‐assisted fine‐tuning via rqt_reconfigure)
6. rviz_command_button (custom RViz plugin for “Save”/“Next” buttons)
• Topics & Data Flows:
• /camera/image_raw ⇒ camera images
• /velodyne_points (or configured) ⇒ LiDAR clouds
• Custom “cloud+image” pairing channel to data_generate
• Detected chessboard models ⇒ files or parameters
• Final calibration parameters ⇒ saved to data/result
• Supporting Services:
• dynamic_reconfigure server for tuning parameters
• ROS parameter server (YAML files under param/)
• External Tools:
• MATLAB / MATLAB Runtime (for intrinsic calibration)
• RViz (visualization) & rqt_reconfigure (parameter tweaking)
Relationships and Interactions
• data_generate subscribes to image & cloud ⇒ publishes paired file paths
• camera_calibration reads images from disk or via launch ⇒ outputs intrinsics
• lidar_chessboard_detector subscribes to point clouds ⇒ publishes detected plane info & renders point sets in RViz
• lidar_camera_calibration reads both chessboard models (camera & LiDAR) ⇒ runs two‐stage optimization via cppoptlib ⇒ outputs extrinsics
• manual_calibration overlays point cloud on image in RViz ⇒ dynamic_reconfigure callback updates transform in real time
Architectural Patterns & Design Principles
• Loose coupling: each ROS node handles one stage
• Publisher/Subscriber for asynchronous data flow
• Parameterization via YAML + dynamic_reconfigure
• Reuse of a generic optimization library (cppoptlib) for solver algorithms
• Separation of concerns: visualization (RViz) vs. computation (nodes) vs. UI (rqt buttons)