Closed shenoynikhil closed 3 months ago
Hi @shenoynikhil, What happens if you use the following YAML file:
name: custom_env
channels:
- conda-forge
dependencies:
# standard stuff
- python >=3.8
- pip
- cudatoolkit
# ML
- e3nn
- pytorch
# MD
- openmm
- openmm-ml
- openmm-torch
Assuming you're on x86_64, this resolves to the latest packages on my end.
It seems the package causing the conflicts was PyG. It works fine if you install it afterwards via pip, as described here.
Combining packages from conda-forge with any other channel often doesn't work correctly.
@JMorado That seems to resolve the issue!
Installing this package with recent versions of torch results in package conflicts. I am using the following yml file to install my environment.
I think it comes from
torchani
's incompatibility with recent torch versions. Any suggestions on how this could be potentially fixed?