Replies: 2 comments 2 replies
-
|
Thanks for reporting this @PabloNA97 Overall, we do not recommend downgrading and re-upgrading. I'm glad to see that it works for you in this instance, but this is far too error prone. Ideally we want to make sure it works when you install things the first time around. The first issue you mention (re: CMMotionRemover) is something that is fixed in OpenMMForceFields 0.14.2. It's interesting to see that your first environment didn't pick this up. Could I ask how you installed that environment? Was it just "mamba install openfe"? The second issue you mention seems to maybe be related to a know issue that happened with importllib-metadata yesterday: conda-forge/importlib_metadata-feedstock#148 I'm wondering if retrying a fresh environment today might fix some of these issues. I'm going to tag @atravitz and @mikemhenry here - it looks like the |
Beta Was this translation helpful? Give feedback.
-
|
Hi @IAlibay Thank you for the feedback, I'll take this into account! My first attempt involved upgrading an older environment to
Both gave me the CMMotionRemover error. This was a clean installation in principle and no base environment was active - not sure what happened. From what you say it doesn't make sense that it went away downgrading openmmforcefields. If you cannot reproduce it it might be a mistake on my end. Thanks for all the work you do here by the way :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Recently I came across two errors related to openfe dependencies. I leave here the errors and what I did to solve them in case someone else finds it useful. Apologies for not providing the environment.yml files to reproduce the errors easily. Also, I can move this user story to Issues if it's more appropiate...
I installed the openfe environment following the instructions from the webpage. I obtained this environment:
first_openfe_env.txt
Then I created ligand networks and tested a single edge for 3 different systems (one of them I had already ran it before). But this time I obtained the following error:
ForceException: Custom forces not supported. Found force of type CMMotionRemover.Looking at the stdout file I saw this:
openfe testwas showing the same error. I compared my environment with a previous one and I downgraded openfe, gufe, openmmforcefields and ambertools with:mamba install openfe=1.1.0 gufe=1.0.0 openmmforcefields=0.14.1 ambertools=23.6This seemed to work and the error went away. However a new one appeared:
ValueError: Could not locate file amber/ff14SB.xmlI checked the environment and I could find the file in
./lib/python3.12/site-packages/openmmforcefields/ffxml/amber/ff14SB.xmlinside the environment folder. Theopenfe testcommand show some test failing with the same message related to importlib_* packages. Thus I tried to downgrade them as well:mamba install "importlib-metadata=8.5.0" "importlib_resources=6.4.5"Now I have a working environment, I was also able to upgrade openfe back to 1.4.0 and works fine. See both environments exported with the '--no-builds' option to hopefully make them cross-platform compatible :)
Environment with openfe 1.1.0
`channels:
dependencies:
`
Environment with openfe 1.4.0
`channels:
dependencies:
`
Hope it's useful to someone!
Beta Was this translation helpful? Give feedback.
All reactions