velodyne.yaml 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. common:
  2. lid_topic: "/velodyne_points"
  3. imu_topic: "/imu/data"
  4. #NCLT
  5. # lid_topic: "/points_raw"
  6. # imu_topic: "/imu_raw"
  7. #KITTI
  8. # lid_topic: "/kitti/velo/pointcloud"
  9. # imu_topic: "/kitti/oxts/imu"
  10. #RS LiDar
  11. # lid_topic: "/rslidar"
  12. # imu_topic: "/imu"
  13. time_sync_en: false # ONLY turn on when external time synchronization is really not possible
  14. preprocess:
  15. lidar_type: 2 # 1 for Livox serials LiDAR, 2 for Velodyne LiDAR, 3 for ouster LiDAR,
  16. scan_line: 32
  17. scan_rate: 10 # only need to be set for velodyne, unit: Hz,
  18. blind: 4
  19. mapping:
  20. acc_cov: 0.1
  21. gyr_cov: 0.1
  22. b_acc_cov: 0.0001
  23. b_gyr_cov: 0.0001
  24. fov_degree: 180
  25. det_range: 100.0
  26. extrinsic_est_en: true # true: enable the online estimation of IMU-LiDAR extrinsic,
  27. extrinsic_T: [ 0, 0, 0.28]
  28. extrinsic_R: [ 1, 0, 0,
  29. 0, 1, 0,
  30. 0, 0, 1]
  31. publish:
  32. path_en: true
  33. scan_publish_en: true # false: close all the point cloud output
  34. dense_publish_en: true # false: low down the points number in a global-frame point clouds scan.
  35. scan_bodyframe_pub_en: true # true: output the point cloud scans in IMU-body-frame
  36. pcd_save:
  37. pcd_save_en: true
  38. interval: -1 # how many LiDAR frames saved in each pcd file;
  39. # -1 : all frames will be saved in ONE pcd file, may lead to memory crash when having too much frames.