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

Wrong matching in demo_match #91

Open
npmhung opened this issue Dec 18, 2024 · 2 comments
Open

Wrong matching in demo_match #91

npmhung opened this issue Dec 18, 2024 · 2 comments

Comments

@npmhung
Copy link

npmhung commented Dec 18, 2024

Thank you for your great work.

roma_warp_toronto
To get the uploaded result, I modified the code a bit so that all certainty values>0.05 are changed to 1 as follow:
certainty[certainty>0.05] = 1.

The 2 corresponding frames are also shown in the top row for comparison.

If you look at the red car near the bridge in the first image, you can see that the warped version somehow moves it toward the bridge.

This effect seems to happen to dynamic/occluded regions only. The warped image in the following example is pretty good.

roma_warp_toronto

Could you think of any potential reasons causing this problem?

Thank you
@Parskatt

@npmhung
Copy link
Author

npmhung commented Dec 18, 2024

roma_warp_toronto
One more example with the matching.

@Parskatt
Copy link
Owner

Hi!

The matcher is trained only on static objects. So it's likely that dynamic objects get a low certainty and don't match well. It's a limitation of the current training. Could be fixed by having dynamic data for training.

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