-
Notifications
You must be signed in to change notification settings - Fork 10
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
What step method should be we using? #54
Comments
So, an old version of the twocomponentmodel was using it correctly. I think a little too much copy paste action from merging several versions of ITC.py and models.py of yore dropped the metropolis step. Opening a separate PR to fix after the current. |
CompetitiveBindingModel in it's current form uses both. |
Copy-paste from #55 1,000,000 steps, 10000 burn-in, thinning period of 25: |
Looks like it isn't worth the added complexity right now. Ditch
RescalingStep?
|
Sure, will switch back to regular Metropolis. Leaving the (fixed) implementation if we decide tweaking something, so will merge once I set things back to using just Metropolis. |
Copy-paste from #53
Here is something interesting.
I took a look at the different step methods for MCMC. Here is the host concentration, estimated at 1.0157 mM in this particular experiment (I just picked a host-guest titration at random from one of our previous sets of experiments).
Settings:
Using the TwoComponentBindingModel about 320000 iterations (I stopped it at around 16% of 2000000) 10000 burn in iterations and a thinning period of 25. Not sure how good those settings are but there is quite a striking difference.
Using the RescalingStep:
Note that the value on the y-axis is offset by 1.0124
Using a default pymc Metropolis step:
The text was updated successfully, but these errors were encountered: