-
Notifications
You must be signed in to change notification settings - Fork 19
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
ValueError for fit of ODEModel with additional data for t0 #339
Comments
Interesting. t_bigger = t_like[t_like >= t_initial]
t_smaller = t_like[t_like <= t_initial][::-1]
t_total = np.concatenate((t_smaller[::-1][:-1], t_bigger)) Do you have for me the full traceback? [1] TODO: only do the second integration if needed |
yields to the same error.
Yep. Solely important is that the t0-value defined in I added a txt with my traceback. Please not, however, that I assume you could reproduce the same behaviour with the above mentioned example. |
In addition, prepend t0 to /both/ t_bigger and t_smaller as needed, and if that was needed, trim the result appropriately
I might have found a bug likely associate with
simfit.ODEModel
combined with fitting. More precisely, I assume it might be connected toODEModel
's theinitial
-dict. The issue can be reproduced using the first example provided in the simfit docs, “4.5 ODE Fitting”.will raise following error:
ValueError: operands could not be broadcast together with remapped shapes [original->remapped]: (8,) and requested shape (7,)
However, it will behave as expected if you change
tdata = np.array([0, 10, 10, 26, 44, 70, 120])
. In this example,adata[0]
will be repeatedly handled over to the algorithm. This issue, however, rises independently.Furthermore, the difference between original (m) and requested shape (n) mentioned in the error message is proportional to the frequency of repeated t0-values (f): m - n = f-1.
The text was updated successfully, but these errors were encountered: