-
Notifications
You must be signed in to change notification settings - Fork 57
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
New upper bound for inter1d objects #205
base: master
Are you sure you want to change the base?
Conversation
@anna-parker we decided that this wasn't actually the problem that needed fixing, right? |
Yes - we discovered it was actually due to not enough error handling in the |
I have a case where this is 100% reproducible and it may be completely my fault. This is a small sample of sequences within a small time window (jan - may 2020). The error looks like
This is the command and the files are attached.
With these inputs |
After reproducing nextstrain/augur#1032 @corneliusroemer and I found that the issue was during
_ml_t_joint
. An internal node was suggested time points that were out of bounds of pre-calculated interpolation objects (integral_merger_rate
,total_merger_rate
). These time points were obtained frommsgs_to_multiply
and were outside of the x -axis upper bound for the interpolation objects. The upper bound of the interpolation objectsintegral_merger_rate
andtotal_merger_rate
was predefined usingttconf.BIG_NUMBER
.To avoid further out of bounds errors we introduced a new constant value
BIGGEST_NUMBER = sys.float_info.max
to use as an upper bound for the interpolation objects. We don't think that altering this range will have any numerical impact but please let us know if we have overlooked something @rneher.Resolves nextstrain/augur#1032