Interested researchers should first start their readings with the following paper:
F. Pomerleau, F. Colas, R. Siegwart, and S. Magnenat, Comparing ICP variants on real-world data sets, Autonomous Robots, Online First, Feb. 2013. Publisher Link, bibtex
This page presents only summary of the evaluation protocol with the required files for the evaluation.
Here is the list of evaluation files and 3D scans for each environment:
Environment | Download | |||
---|---|---|---|---|
3D Scans | Protocol | Validation | ||
ETH | data | eth_protocol.csv | eth_validation.csv | |
Apartment | data | apartment_protocol.csv | apartment_validation.csv | |
Stairs | data | stairs_protocol.csv | stairs_validation.csv | |
Wood Summer | data | wood_protocol.csv | wood_validation.csv | |
Gazebo Winter | data | gazebo_protocol.csv | gazebo_validation.csv | |
Mountain Plain | data | plain_protocol.csv | plain_validation.csv |
The protocol header has the following elements:
reference_name | reading_name | iT00 | iT01 | iT02 | … | iT33 |
---|---|---|---|---|---|---|
Hokuyo_0.csv | Hokuyo_1.csv | 1.0 | 0.0 | 0.0 | … | 1.0 |
Hokuyo_0.csv | Hokuyo_1.csv | 0.98 | -0.14 | 0.009 | … | 1.0 |
… | … | … | … | … | … | … |
File names in the column reading_name and reference_name correspond to point cloud file name express in their own local coordinates. So files named Hokuyo_<i>.csv can be expressed as follow:
, where is the number of lines in the file.
The validation header has the following elements:
overlap_ratio | perturbation_type | gT00 | gT01 | gT02 | … | gT33 |
---|---|---|---|---|---|---|
0.308 | easyPoses | 1.0 | 0.0 | 0.0 | … | 1.0 |
0.858 | mediumPoses | 0.98 | -0.14 | 0.009 | … | 1.0 |
… | … | … | … | … | … | … |
The columns named iTxx
are the initial transformation matrices that need to be applied to the reading point cloud before registration. The same pair of scans is used multiple time with different initialization to evaluate the robustness of a registration solution against prior transformation.
The columns named gTxx
are the transformations matrices of the ground truth .
A transformation matrix can be deserialized using the columns T00
to T33
as follow:
Using the first line of the Evaluation file presented above as an example, the computation should be as follow:
iT00
to iT33
).
where is the reference point cloud, is the reading point cloud, and is the prior transformation of .
gT00
to gT33
).
The result file should be a comma-separated value (csv) file with a comma ', '
as separator and a header.
Here is an example of the expected format:
time | T00 | T01 | T02 | … | T33 |
---|---|---|---|---|---|
6.15 | 1.0 | 0.0 | 0.0 | … | 1.0 |
2.78 | 0.98 | -0.14 | 0.009 | … | 1.0 |
… | … | … | … | … | … |
The field time is expressed in second and should include all preprocessing steps required by the solution except the loading time from disk to memory. The columns Txx follow the same serialization format defined in the prior section. The 4×4 transformation matrix is the result of the registration process . Then, there should be one result per test which means that the number of lines in a Result file should be the same as in the Evaluation file. We suggest to name the file with the environment name as in this example for a test run on apartment: apartment_chen91.csv.
You can send your results to François Pomerleau so we can publish them on this web site.