-
Notifications
You must be signed in to change notification settings - Fork 20
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 MWIS part will take a really long time when the number of branches reaches 35 or more. #4
Comments
Can you please try lowering the gating area parameter in params.txt? |
I will test that and get back to you. |
Yeah, actually I set the gating area to 6, and my input is ground thruth(no false alarm), which means there is only one measurement can be included in the gating area. |
Yes, I think I will try the NetworkX maximum-weighted matching implementation to see if there is an improvement in performance. For track pruning, I set an N-scan window of 1. I will also add a user-defined parameter for this, but you can modify it here in the code: Line 50 in bcc969e
|
Any updates on this? I run into the same problem. The MWIS part is taking very long in the second frame with 14 detections. |
Any update on this? Its super slow |
I have added two missing pruning parameters from the paper: Bth for setting the maximum number of branches, and Nmiss for the maximum number of consecutive frames with missing observations for a track in commit 5627c53. Please try adjusting these parameters to improve performance. |
您发给我的信件已经收到。 胡梦景This is an automatic reply, confirming that your e-mail was received.Thank you
|
I run this code with only 5 detections a frame and the N-scan number is 3, and it takes a really long time at frame 3, in which it keeps running the bron_kerbosch() function.
I am not sure if there is a better way for this part or is that because I am not running this codes properly?
And how many detections could the algorithm handle at most when you test?
Really appreciate for your reply.
The text was updated successfully, but these errors were encountered: