update README
Browse files- calibration/README.txt +55 -8
calibration/README.txt
CHANGED
|
@@ -1,12 +1,59 @@
|
|
| 1 |
-
|
| 2 |
-
imu.yaml: IMU intrinsic
|
| 3 |
|
| 4 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 5 |
|
| 6 |
-
|
| 7 |
-
|
| 8 |
-
|
| 9 |
-
|
| 10 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 11 |
|
| 12 |
Intra-camera calibration and IMU-LiDAR can be inferred from the transformations above.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# File Format
|
|
|
|
| 2 |
|
| 3 |
+
cam<n>.yaml: Cameras intrinsics obtained from Kalibr (https://github.com/ethz-asl/kalibr)
|
| 4 |
+
- camera_matrix (3x3)
|
| 5 |
+
- distortion_coefficients ([k1, k2, k3, k4])
|
| 6 |
+
- distortion_model (equidistant, see https://github.com/ethz-asl/kalibr/wiki/supported-models)
|
| 7 |
+
- projection_matrix (3x4, same as camera matrix)
|
| 8 |
+
- rectification_matrix
|
| 9 |
+
- image_width, image_height
|
| 10 |
|
| 11 |
+
imu.yaml: IMU intrinsics obtained from Allen Variance ROS (https://github.com/ori-drs/allan_variance_ros)
|
| 12 |
+
- accelerometer_noise_density
|
| 13 |
+
- accelerometer_random_walk
|
| 14 |
+
- gyroscope_noise_density
|
| 15 |
+
- gyroscope_random_walk
|
| 16 |
+
- rostopic
|
| 17 |
+
- update_rate
|
| 18 |
+
|
| 19 |
+
cam-lidar-imu.yaml: Camera-LiDAR-IMU extrinsics obtained from DiffCal (https://github.com/ori-drs/diffcal)
|
| 20 |
+
- T_cam_lidar: 4x4 homogeneous matrix that converts points in lidar frame to camera<n> frame
|
| 21 |
+
- C_r_CL: translation (x,y,z) of T_cam<n>_lidar
|
| 22 |
+
- C_q_CL: rotation quaternion (x,y,z,w) of T_cam<n>_lidar
|
| 23 |
+
- C_r_CI: translation (x,y,z) of T_cam<n>_imu
|
| 24 |
+
- C_q_CI: rotation quaternion (x,y,z,w) of T_cam<n>_imu
|
| 25 |
+
- rostopic
|
| 26 |
|
| 27 |
Intra-camera calibration and IMU-LiDAR can be inferred from the transformations above.
|
| 28 |
+
|
| 29 |
+
# Base Frame
|
| 30 |
+
An artificial frame that is located at the bottom of the device with the x-axis forward (same direction as the front camera), y-axis to the left, and z-axis to the top. It is designed to make the visualisation of the sensor pose more intuitive.
|
| 31 |
+
|
| 32 |
+
The base frame is manually set with respect to the lidar as
|
| 33 |
+
T_base_lidar_t_xyz_q_xyzw = [0.0, 0.0, 0.124, 0.0, 0.0, 1.0, 0.0]
|
| 34 |
+
|
| 35 |
+
The processed (undistorted) point clouds from VILENS are provided in the base frame, not the lidar frame.
|
| 36 |
+
|
| 37 |
+
# Calibration sequences
|
| 38 |
+
There are three sequences recorded for calibration
|
| 39 |
+
- 2024-03-19
|
| 40 |
+
- 2024-06-29 (although imu calibration is done on 2024-06-27)
|
| 41 |
+
- 2024-10-29
|
| 42 |
+
|
| 43 |
+
|
| 44 |
+
The default calibration files provided in this folder are obtained from these sequences.
|
| 45 |
+
- cam<n>.yaml: 2024-03-19 sequence
|
| 46 |
+
- imu.yaml: 2024-06-29 sequence
|
| 47 |
+
- cam-lidar-imu.yaml
|
| 48 |
+
- cam-lidar: 2024-03-19 sequence
|
| 49 |
+
- cam-imu: 2024-06-29 sequence
|
| 50 |
+
|
| 51 |
+
The rationale is that
|
| 52 |
+
- most sequences we have are collected in March (2024-03-xx)
|
| 53 |
+
- for these sequences, the closest IMU calibration we did is in June (2024-06-29)
|
| 54 |
+
|
| 55 |
+
|
| 56 |
+
We recommend using the calibration that is closest to the sequence that you are testing.
|
| 57 |
+
- 2024-03-xx sequences (the majority): use the default calibration files
|
| 58 |
+
- 2024-05-20 sequences (bodleian library-02): either calibration from 2024-03-19 or 2024-06-29
|
| 59 |
+
- 2024-07-09 sequences (new college): use calibration from 2024-06-29
|