-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change number of iterations in mbar #2
Comments
@ncheron at the moment nobody is working on flamel so I am afraid, you're on your own figuring things out. If you want to contribute code and work on it then you're more than welcome!! |
Thank you for your answer. After switching from Gromacs2019.4 to Gromacs2021, my problems have disappeared and I don't know why. I will keep using Gromacs2021 for FEP. |
FYI, alchemlyb 0.5.1 fixed that (but not in flamel yet I think) |
I also just stumbled over that issue again - in flamel we just call the standard constructor of alchemlyb's MBAR introduced in alchemistry/alchemlyb#162 and changing the call in flamel/estimator/mbar.py to
or
both work fine in line with the discussion in choderalab/pymbar#419. So the passing of the arguments in alchemistry/alchemlyb#162 works as expected and the issue (at least for me) seems to be that in alchemistry/alchemlyb the default is @orbeckst should I address this in alchemistry/alchemlyb? If sticking to |
Better discussed in alchemlyb — you can raise an issue to change the default setting of the MBAR estimator. |
@xiki-tempula is this issue addressed in the flamel rewrite, namely can one choose to use AutoMBAR for the ABFE workflow from the |
@orbeckst So for alchemlyb 1.0, using MBAR defaults to use AutoMBAR. Either way, we won't have this issue. |
Thanks for the clarification, I am closing the issue. |
Hi,
I am using flamel to analyse FEP results (solvation free energy of acetate performed with Gromacs). With pymbar3.0.5 I encounter this issue choderalab/pymbar#320. After switching to pymbar3.0.3, flamel works for switching off the charges, but not when I switch off van der waals (I still have the same issue). I have read here choderalab/pymbar#419 a workaround (from Michael Shirts on March 22nd). Can you please guide me on where I should add these three lines in flamel to check if it works?
Thank you
Nicolas
PS : BTW, thank you for this tool, it is very useful
The text was updated successfully, but these errors were encountered: