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

The result about LoFTR in Table V #11

Closed
RingoWRW opened this issue Sep 15, 2024 · 3 comments
Closed

The result about LoFTR in Table V #11

RingoWRW opened this issue Sep 15, 2024 · 3 comments

Comments

@RingoWRW
Copy link

Hi Luo, I believe JointLoc is a remarkable achievement and I am intrigued by this work. I have a question about Table V. Why can't LoFTR generate matches in textureless regions?

@LuoXubo
Copy link
Owner

LuoXubo commented Sep 15, 2024

Hi, sorry for the confusion. The "failed" here refers to the fact that our device cannot support the matching of LoFTR in large-scale map localization.

@RingoWRW
Copy link
Author

Thank you for your response. I also have another question regarding Table V. I would like to know the experimental conditions for absolute localization. I noticed that the error for absolute localization is 10 times larger than SLAM.

@LuoXubo
Copy link
Owner

LuoXubo commented Sep 15, 2024

The experiments are conducted on the RTX 2080Ti. Absolute localization sometimes has very small errors, and sometimes has very large errors. I think the main reason why absolute localization cannot be used alone for UAV is that the positioning result is not smooth enough.

@LuoXubo LuoXubo closed this as completed Nov 16, 2024
@LuoXubo LuoXubo pinned this issue Nov 16, 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

2 participants