Skip to content

Extending the Robustness of LiDAR SLAM to Geometrically Degenerate Scenarios

Notifications You must be signed in to change notification settings

PengYu-Team/GEODE_dataset

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GEODE Dataset

Heterogeneous LiDAR Dataset for Benchmarking Robust Localization in Diverse Degenerate Scenarios

| Webpage | Full Paper |

TL;DR: A comprehensive multi-LiDAR, multi-scenario dataset that extensively incorporates segments of real-world geometric degeneracy.

image-20240909194424089

image-20240909194439292

News

  • (20241025) The metadata.json file for the OS1-64 used in the Beta platform can be accessed via the following link: Google Drive.
  • (20240910) Data can be downloaded from GEODE - Google Drive.
  • (20240910) Dataset README is avaliable.

Overview

Usage Steps

  1. Review the overview of the GEODE dataset, including details about sensors, definitions of ROS topics and messages, and important caveats regarding localization evaluation.
  2. Download the dataset from GEODE - Google Drive. Additional information about each sequence and scenario is available on our homepage. Additional download options for users in Mainland China will be made available in the future. Currently, we only provide ROS1 bags. ROS2 users can convert these using the rosbags-convert toolkit.
  3. Adapt your SLAM algorithm using the provided dataset parameters, and calculate the error after obtaining the results.

Sensors

  • Device $\alpha$:
    • Velodyne VLP-16 ;
    • Stereo HikRobot MV-CS050-10GC cameras;
    • Xsens MTi-30 IMU;
  • Device $\beta$:
    • Ouster OS1-64;
    • Stereo HikRobot MV-CS050-10GC cameras;
    • Xsens MTi-30 IMU;
  • Device $\gamma$:
    • Livox AVIA;
    • Stereo HikRobot MV-CS050-10GC cameras;
    • Xsens MTi-30 IMU;

The GEODE dataset provides sensor raw data and corresponding rosbag.

Alt text

Sensor raw data with * is only available for $\beta$ device.

ROS Topic and Explanation of Each Message

image-20240717154348844

Sensor Calibration

The calibration results are stored in three files, alpha.yaml, beta.yaml and gamma.yaml, according to the acquisition device.

Ground-Truth Devices

image-20240717154308031

Localization Evaluation

We have provided the script 'rmse.py' for everyone to calculate the localization accuracy of the algorithms they run.

python3 rmse.py <Your traj> <GT traj> <time offset>

For example, running the following command will calculate the error between all trajectories in TUM format that contain the relead field and the ground truth trajectories, and then compute the average value.

python3 rmse.py relead <GT traj> 0

image-20240717154531532

For the sequences 'off-road', 'inland_waterways', and 'Metro_Tunnels_Tunneling', three sets of equipment were mounted on a rack constructed from aluminum profiles to simultaneously collect data, while only one set of GT pose equipment was utilized to capture motion trajectories. Consequently, the trajectories obtained from the algorithm need to be processed before proceeding with subsequent error calculations. Fortunately, due to the effectiveness of the time synchronization scheme, we only need to account for the spatial offsets between different sensors in these sequences.

For the 'off-road' and 'inland_waterways' sequences, where GT poses are collected using GNSS/INS, we align the GT poses to the coordinate system of the beta device. This alignment allows the trajectories derived from the beta device's data, processed by the algorithm, to be directly used for error calculation. For the alpha and carol devices, the trajectories from the algorithm are transformed into the GT pose coordinate system using the scripts alpha2gt_gnss.py and ``gamma2gt_gnss.py` before error calculations are performed.

In the 'Metro_Tunnels_Tunneling' sequence, where GT poses are obtained by tracking prisms with a Leica MS60, we align the true values to the alpha device. The beta and gamma devices then convert the algorithm's trajectories to the GT pose coordinate system using the scripts beta2gt_leica.py and carol2gt_leica.py. The necessity of using scripts to transform coordinate systems, which requires additional operations to calculate errors, arises from the fact that the GT poses from the Leica tracking prisms include only positions, not attitudes. It is challenging to convert the true values to the other two devices using the results of multi-aLiDAR calibration. To maintain a unified processing approach, we adopt the same method for sequences recorded simultaneously.

For the “stair” sequence, we obtain the ground truth pose by using the PALoc algorithm to align the sensor data with the ground truth map. However, due to the small field of view of the Livox Avia LiDAR equipped with the $\gamma$ acquisition device, the odometry drifts, preventing us from obtaining the GT trajectory for the $\gamma$ acquisition device. Therefore, for this sequence, I propose to evaluate the localization errors of different algorithms by comparing the maps constructed by the odometry with the ground truth maps (Evaluation with Cloud Map Evaluation Lib).

Dataset Details and Download

Click the button below to access detailed information (including scenarios, degeneration types, etc.) and to download the dataset.

Homepage of GEODE dataset

Related Links

Awesome-Algorithms-Against-Degeneracy

Dataset

Publications

  1. Heterogeneous LiDAR Dataset for Benchmarking Robust Localization in Diverse Degenerate Scenarios Zhiqiang Chen, Yuhua Qi, Dapeng Feng, Xuebin Zhuang, Hongbo Chen, Xiangcheng Hu, Jin Wu, Kelin Peng, Peng Lu Under Review [Arxiv]

Contact

If you have any other issues, please report them on the repository.

About

Extending the Robustness of LiDAR SLAM to Geometrically Degenerate Scenarios

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages