Open barmoral opened 1 year ago
I'm able to run this pretty quickly with two changes:
conda install -c conda-forge mamba
. Mamba is much faster than conda.mamba create
instead of mamba install
- install
tries to update the current environment with minimal changes, but your environment above is using python 3.6 which major packages don't publish for any more, so the environment resolution is very complex. If you do create
, it solves everything with no constraints. Separately, YANK has fallen out of repair and so Evaluator dropped its YANK interface in July. So you probably want to pin openff-evaluator=0.4.3
in the mamba create command as well if you're looking to use YANK. As a replacement, Perses is rolling out support for hydration free energies instead, but my understanding is that it's still coming.
So basically, after you install mamba (the first bullet point), do mamba create -n evaluator_env -c conda-forge openff-evaluator=0.4.2
. This solves the environment for me in just a few seconds.
Please let me know if this solves your issue!
@barmoral are you still having issues with installation?
Thank you for your help! Yes, I was able to install the old versions succesfully, but have not come around to try if everything works fine. I'll keep you posted if anything else comes up. I appreciate your time and attention!
Describe the bug
The installation of openff-evaluator in conda is failing to solve environment. The process is killed and installation does not go through.
To Reproduce
In a new/blank conda environment run the command "conda install -c conda-forge openff-evaluator".
Output
Collecting package metadata (current_repodata.json): done Solving environment: failed with initial frozen solve. Retrying with flexible solve. Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source. Collecting package metadata (repodata.json): done Solving environment: - Killed
Computing environment (please complete the following information):
conda list
:Additional context
I tried installing the "yank" package on a new conda environment too (using "conda install yank"), and got the same error as output. These issues might be related.