-
Notifications
You must be signed in to change notification settings - Fork 23
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
Does not interface with extra PLUMED2 modules (i.e FunnelMD, Maze) #56
Comments
Sorry for the delay. I'm just catching up after the holidays. I don't quite understand your question. What do you mean when you say it "does not capture the correct platform"? Could you give a working example that shows the problem? |
OpenMM-PLUMED pass the script to the PLUMED parser (
Most likely, FunnelMD or Maze tags aren't recognized because PLUMED was built without these extra modules. |
Hi, Could you please let me know how to add and use these other PLUMED modules (e.g. Maze) when using OpenMM? Looks like simply using condo to install it |
It has been some time since I have revisited this issue, I might need to try and recreate the issue again to see if it still exists in version 8.0, but essentially this is all happening with the understanding that plumed will need to be compiled locally (maybe openmm-plumed as well?) in order to compile the extra modules (e.g. MAZE) in the build process which are not included in the distributions on conda. |
After compiling plumed, openmm, and openmm-plumed locally, I would have thought that the force script utilizes plumed native parsing. However, I cannot reference the additional plumed modules through the plugin. Is there a simple fix such as adding the tags for them to be parsed somewhere?
I do not believe that this should break any existing calculations since it works already with the METAD tag.
Edit: I should clarify, the force is being picked up, but it does not capture the correct platform for the specified context. This is odd since a normal METAD tag PLUMEDForce script does capture the correct platform.
The text was updated successfully, but these errors were encountered: