Skip to content
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

Heuristics for selecting number of windows #1

Open
jmichel80 opened this issue Oct 5, 2016 · 0 comments
Open

Heuristics for selecting number of windows #1

jmichel80 opened this issue Oct 5, 2016 · 0 comments

Comments

@jmichel80
Copy link
Contributor

So far our studies have generally used the same number of windows for each perturbation in a given dataset. However the number of windows needed is perturbation specific.
To have a robust workflow we should optimise this.

Option 1) Run a short simulation with a small number of windows (say 8). Analyse precision and reproducibility of forward and backward runs. Add new windows to systems that converge poorly. Resume simulations.

Problem with this is MBAR needs adapting so we post-process again already computed trajectories to get the energies of the new perturbed states. This will increase storage needs significantly, at least until a job is declared converged. Or have to restart everything from scratch. TI has the advantage that adding new lambda values does not require re-analysing old trajectories.

Option 2) Analyse how much the end states differ with an ad hoc rule and guess number of windows accordingly. Ad hoc rule based on prior experience. Less rigorous but easier to code. A more refined variant could make guess by looking up a database of free energy calculation results. The database could be automatically compiled by submitting results of a free energy run to a remote server. This would help refine ad hoc rules as data is collected.

Similar considerations apply to guess the number of cycles to perform.
Here MBAR/TI are both straightforward.

Any other option? Other pros & cons of option 1 & 2 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant