Visit the Hilti SLAM Challenge homepage for more information.
The more datasets you submit the more points you can get. The datasets where we provide the groundtruth are not considered in the final score.
We disclose the names only after prior approval. Before making the leaderboard public I will send out an email to all participants with their respective rank and the option to withdraw.
The submission will be ranked based on the completeness of the trajectory as well as on the position accuracy (ATE). The score is based on the ATE of individual points on the trajectory. Depending on the error between 10 and 0 points are added to your final score. This way also incomplete trajectories can be included in the evaluation. You always can submit your current results and receive an accuracy report using our submission system.
We provide ground truth for selected datasets. Please use our submission system to test your algorithm. We will also provide high-accuracy laserscans for selected datasets after the challenge.
We noticed that the timestamp for every point in a lidar point cloud scan is equal. Is it possible to correct this issue?
The Hesai ros driver stores the timestamp in this struct. What happens is the sensor_msgs/PointCloud2
Message has a "data" member in byte and it stores the PointXYZIT
defined time, xyz, etc. The "field" member describes what type of info is in "data". In a programme, one would convert the PointCloud2
msg into PointXYZIT
msg to access all the element pandar records.
Below is a schematic of the reference frames (red = x, green = y, blue = z): The frames are:
C0
toC4
are the camera frames of the alphasense.I
is the IMU frame as installed on the alphasense. Note that this is also the same frame the ground truth is defined in.T
is the tip frame. A calibration between IMU and tip is provided.
Yes, now there is! You can clone and compile the following ROS packages:
phasma_description
: this is the main URDF model of the sensor setup.hesai_description
: this is the URDF model of the HESAI. It's a dependency ofphasma_description
.alphasense_description
: this is the URDF of the Alphasense. It's a dependency ofphasma_description
.
To have them in you system you can just clone and compile them in your catkin workspace, for example:
cd ~/catkin_ws/src/
git clone https://github.com/Hilti-Research/phasma_description.git
git clone https://github.com/Hilti-Research/hesai_description.git
git clone https://github.com/Hilti-Research/alphasense_description.git
cd ..
catkin build phasma_description