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

if we change the two image of order, we got the different size of matching-poing, ps : config, extractor:num_kpt=300 #5

Closed
larsoncs opened this issue Jan 15, 2022 · 3 comments

Comments

@larsoncs
Copy link

thanks

@vdvchen
Copy link
Owner

vdvchen commented Jan 17, 2022

Hi,

Due to the concate operation in our network, the obtained matches are expected to differ when reversing img order. However, statistically the result should make very little differences.

@larsoncs
Copy link
Author

can you eliminate the differences?

@vdvchen
Copy link
Owner

vdvchen commented Jan 17, 2022

As a workaround, you may run the network twice for both img orders and find the intersection set, as is done for some neural outlier rejector(filtering based methods)

@vdvchen vdvchen closed this as completed Mar 26, 2022
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