-
Notifications
You must be signed in to change notification settings - Fork 12
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
Exception raised when no matching node is found #5
Comments
Currently I don't think it is possible. I also want to add a feature like that, but it requires to reformat the code... Hope it helps ! |
Okay! Thanks. Yes I am trying to tune them now. However I am getting a new error
This is due to the If you have any insights as to why the Best |
Seems like I need to dive a little deeper in the code. I will try to figure it out this weekend, if I find any fixes I will update this thread ! |
Hello! I am also facing this problem, Have you figured it out? Thanks! |
Hello! The only way I could solve this is by playing around with the parametrers (max_dist , max_dist_init etc) defined while generating a DistanceMatcher object |
Hello, dear Huzaifg! |
matching.match(graph, track, method='hmm')
raises an exception when no matching node is found and stops the program. Can we skip the point is there is no matching node found in order to prevent the program from ending?The text was updated successfully, but these errors were encountered: