Skip to content

Conversation

mihaidusmanu
Copy link
Contributor

No description provided.

self.name2key[image.name]: image.image_id
for image in self.reconstruction.images.values()
}
# We cache the 3D points for mapping images to avoid parsing them from
Copy link
Collaborator

@sarlinpe sarlinpe Mar 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually in #62 (review pending) I already had 100x speedup in pose estimation by only caching the image-to-point3D ID mapping, would this be sufficient? fetching the xyz seems already pretty fast and caching it is more expensive memory-wise. The locking adds quite a lot of complexity, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll take a look there - maybe that's sufficient since I agree the locks complicate things.

To be honest, the fastest I managed to get our pose estimation was with single-threaded + caching. I didn't investigate too much where it's coming from though.

Comment on lines +150 to +156
'cosplace': {
'name': 'cosplace',
'hloc': {
'model': {'name': 'cosplace'},
'preprocessing': {'resize_max': 640},
}
},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cvg/Hierarchical-Localization@d0e8494 removes Cos/EigenPlaces but adds MegaLoc, which is much more robust (and has results on LaMAR).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the info, I'll go ahead and replace with MegaLoc and will also try that one on a currently private data split (to be released) to see where it stands (SALAD seems kinda good 😄 )

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

Successfully merging this pull request may close these issues.

2 participants