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

Why Kruskal for track generation? #6

Open
AIBluefisher opened this issue Oct 11, 2021 · 0 comments
Open

Why Kruskal for track generation? #6

AIBluefisher opened this issue Oct 11, 2021 · 0 comments

Comments

@AIBluefisher
Copy link

AIBluefisher commented Oct 11, 2021

Hi, @mihaidusmanu

I'm curious about the manner of track generation. As is mentioned in your paper, you used kruskal to generate tracks with confidence that comes from descriptors similarity. It is different from the traditional track generation method which simply uses a union-find algorithm with limited size to generate tracks firstly and then filter ambiguous track elements. In my point of view, kruskal can generate more tracks but potentially shorter, union-find can generate longer but fewer tracks. Both methods may contain outliers and it's not clear which one is better. What do you think?

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

1 participant