Skip to content
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

About Tracking On TUM Dataset #22

Open
Buffyqsf opened this issue Apr 29, 2024 · 2 comments
Open

About Tracking On TUM Dataset #22

Buffyqsf opened this issue Apr 29, 2024 · 2 comments

Comments

@Buffyqsf
Copy link

Thanks for your great work!
I installed the pygicp library and tried to test it on TUM dataset and Replica dataset with the example you gave (fast_gicp/python_tester). And I found that the tracking accuracy of Replica dataset is similar to that of the article, but it is difficult to achieve the tracking accuracy of the article on TUM dataset.
In your approach, tracking is achieved through pygicp.FastGICP (), but what other factors or tricks brings a better tracking accuracy?

@Lightingooo
Copy link

I have the same question.

@Riboha
Copy link
Member

Riboha commented May 2, 2024

As mentioned in the paper, in the GS-ICP SLAM, we select keyframes by our dynamic selection method. But this method is not implemented in the python_tester of fast_gicp.
And further details are added to the GS-ICP SLAM. Please checkout the paper for more details.

@Riboha Riboha closed this as completed May 9, 2024
@Riboha Riboha reopened this May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants