-
Notifications
You must be signed in to change notification settings - Fork 5
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
checking calculated rates for the manual test #17
Comments
@iwelland suggested the following approach (#11 (comment)): I have a 1 microsecond IFABP trajectory, let me compare rates on 500ps windows and also compare to 1ns + windows. Without experimental data or a direct MD method to compute the rate we can try to just compare multiple windows/look at convergence; the variance in the rate distribution over several .5ns windows might be helpful. |
I replied (#11 (comment)):
Then lets look at the raw rate.txt files. We can then decide how to continue, eg making histograms of rates, computing the rates over all blocks, etc. But I don't want to do anything exhaustive until we have a rough idea what to expect. |
@iwelland , you put forward the hypothesis that the weird numbers are due to the fact that the exponential fits are generated from very short trajectories. Did you look into how good of an estimator the exponential fit is for rates with few/short events? |
Not yet, what do you think the best method is? Some possibilities:
|
Simulating a simple two state model and then fitting it seems simple enough so why not try it? If you find that you can accurately fit rates even with few events then this indicates that the assumption of a simple 2 state model in hop is flawed (at least for some sites). (2) and (3) might be quicker, if you can find an answer quickly… what does Google or the ASU library search say?
Oliver Beckstein * [email protected] |
I will try 1, but I actually think the easiest thing to do is to consider several other plausible distribution functions and fit them to the 1micro Aqp1 data. Provided the bi-exponential fits are good in the first place, deviations in the simulation results vs. walker sim will give us a sense of how these things matter. We can also try various hand waves to discard edges/nodes to sanitize the model as a starting point before applying anything more rigorous. |
The current manual testing protocol contains a short (0.5 ns) trajectory of I-FABP. The rates that come out of running it through hop are not very believable, see discussion following #11 (comment).
We want to figure out if these rates are correctly calculated but just not converged or if there's a deeper problem.
(This is also important if we want to use a short version of the test trajectory for proper tests #2.)
The text was updated successfully, but these errors were encountered: