-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about Evaluation #48
Comments
|
Thanks a lot for your response. I can find the ground truth files for training datasets and synthetic datasets. But I cannot find any ground_truth.txt in the test datasets. "https://www.eth3d.net/slam_datasets" Sorry for bothering you if there is some relative information I missed. Thanks for your time, I am looking forward to your response. |
That is actually the whole point of test datasets: Their ground truth is private and is only used for evaluation of results that are submitted to eth3d.net. This way, a finished SLAM system can be tested on these datasets while ensuring that no specific parameter tuning etc. has been done on those datasets that would artificially improve its results. |
Thank you so much for your response, I understood. I will close this issue. |
Hello there,
I met a question while I was evaluating my result.
I ran the test datasets from this website "https://www.eth3d.net/slam_datasets" and got my results.
Then I used "evaluate_ate.py" to evaluate my result. I added the addresses of my result file and imu file in the command. However, the ATE RMSE is about 0.98 m which is obviously incorrect.
I have two questions:
There are 4 files named imu.txt in each dataset, what is the difference?
I found an option named offset in "evaluate_ate.py", but I do not understand how to use it, I think probably this is what I should use to correct my evaluation.
Sorry for bothering you if there is some relative information I missed.
Thanks for your time, I am looking forward to your response.
Best regards,
Arete
The text was updated successfully, but these errors were encountered: