-
Notifications
You must be signed in to change notification settings - Fork 48
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
Cannot generate multi-generational tracks. #190
Comments
Hi Ollie - would you be able to post the tracking log? It really helps to debug |
|
Ah - ok, I see. The optimiser timed out (DNF) so you didn't get any lineage information. This is usually because your parameters lead to a very large number of hypotheses to evaluate. You can try letting the optimizer run for a bit longer: # run the optimizer for 10 minutes before timing out
tracker.optimize(options={"tm_lim": 60_000 * 10}) or try tweaking some of the parameters to improve the tracking. Generating 79364 tracks from only 384 frames seems like a lot. Selecting parameters is problem specific, so hard to give universal advice! |
This would be parameters in the motion model initially? Thanks for getting back to me so quickly! |
Yes, the parameters of the "motion model" are a good place to start. Also, is this 2D or 3D data? Sometimes setting the tracking volume ( |
Hi @quantumjot,
I am trying to generate some tracks over a 4 day imaging experiment. While the individual tracks appear to be accurate, I am unable to obtain very long or multi-generational tracks. I have played around with HypothesisModel parameters to try and improve this but always seem to get only one generation - do you have any tips and tricks for improving this?
Let me know if you need any further info and thanks in advance for your help!
Ollie
The text was updated successfully, but these errors were encountered: