You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was running through the spike analysis with multidms 1.9, and found a bug when using Model.wildtype_df.
It's predictions do not match what I get when I crunch the numbers directly from the parameters given in Model.get_mutations_df() + offsets. Concretely
returns $-0.7806519$ as opposed to $-3.605787$ as shown above.
This actually does not effect the spike analysis almost at all, however, that's because we're not looking at the WT "effect" in our analysis - but I'm certain this could be causing @jbloom issues (sorry! 😬).
That being said all the spike results identical! I'll be taking a look at this with fresh eyes tomorrow am.
The text was updated successfully, but these errors were encountered:
Was running through the spike analysis with multidms 1.9, and found a bug when using Model.wildtype_df.
It's predictions do not match what I get when I crunch the numbers directly from the parameters given in
Model.get_mutations_df()
+ offsets. ConcretelyHere is what the method is telling me.
but, when I predict the latent wildtype of BA2 by hand
returns$-0.7806519$ as opposed to $-3.605787$ as shown above.
This actually does not effect the spike analysis almost at all, however, that's because we're not looking at the WT "effect" in our analysis - but I'm certain this could be causing @jbloom issues (sorry! 😬).
That being said all the spike results identical! I'll be taking a look at this with fresh eyes tomorrow am.
The text was updated successfully, but these errors were encountered: