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

Adding customized standard in determining the probability of acceptance for Hamiltonian REMD #456

Open
chemlove opened this issue Dec 5, 2019 · 1 comment

Comments

@chemlove
Copy link

chemlove commented Dec 5, 2019

I am new to openmmtools and I try to perform a Hamiltonian-exchange MD with customized standard in determining the probability of acceptance.

For example, I want to add a residue-residue distance to monitor the MD process, and integrate this CV into the Hamiltonian to determine the probability of acceptance in replica exchanges.

As a biginner of enhanced sampling MD, I don't know whether it is meaningful to do this and how to modify relevant codes in openmmtools to achieve it. Can you give me some advice?

It seems the REMD output trajectory in openmmtools is a single trajectory containing all replicas, another problem to be solved is how to calculate the customized CV for different replicas on-the-fly?

Any advice on these problems are very appreciated.

@andrrizzi
Copy link
Contributor

andrrizzi commented Dec 8, 2019

Hi @chemlove . I'm not sure I understand your requirements exactly, but I suggest you look at the CustomCVForce in OpenMM (http://docs.openmm.org/latest/api-python/generated/simtk.openmm.openmm.CustomCVForce.html#simtk.openmm.openmm.CustomCVForce).

Currently, the simulation doesn't store the CVs, but you could either extend the MultiStateSampler and MultiStateReporter code to do so or do it manually after each iteration with something like

for iteration in range(n_iterations):
    hrex_simulation.run(n_iterations=1)
    for sampler_state in hrex.sampler_states:
        # Store sampler_state.collective_variables

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

No branches or pull requests

2 participants