-
Notifications
You must be signed in to change notification settings - Fork 49
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
A problem of file parsing for simulations with multiple coupled states #102
Comments
@wehs7661, can you upload a small data set (maybe just 20 lambda, for not too many steps) that has the same issue? It's much easier for developers to see the issues when they have data to look at. |
Hi @wehs7661! Hmmm, this is an interesting case; thank you for bringing it up! I agree with @mrshirts that if you can package up a reduced set of this data and put it somewhere downloadable it would be useful to proceed. Expanded ensemble is an approach we definitely want to get right, and this is a case I haven't encountered yet. Please also include a minimal working example of the code you are applying to this data to produce the problem you are seeing; that will help to make sure we're both approaching it with the same expectations of what "should work." |
Hi @mrshirts and @dotsdl, |
Hi
alchemlyb
developers,I was running a Hamiltonian replica exchange simulation of 140 states, with the first 4 states being the coupled states (\lambda_{coul}, \lambda_{vdw}, \lambda_{restr}) = (0, 0, 0) since I need more data from physical states. However, I found that with the current GROMACS parsers, including
extract_u_nk
andextract_dHdl
, theu_nk
anddHdl
returned only had 137 states instead of 140 states since the parses did not distinguish the states with the same lambda vectors. This will lead to wrong overlap matrix such that the probabilities of the same row do not sum up to 1. I also had a hard time converging when initializingpymbar.mbar.MBAR()
, but I was not sure if convergence issue is related to the parsing issue. This might be an issue worthy to address. Thank you!The text was updated successfully, but these errors were encountered: