-
Notifications
You must be signed in to change notification settings - Fork 26
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
Feature request: Interface with NEQUIP #48
Comments
(I transferred this issue from the main OpenMM repository, since this is where interfaces to ML codes live.) It ought to be straightforward. There are two levels of interfacing. The lower level piece is the OpenMM-Torch plugin. It lets you use arbitrary PyTorch models as forces. You create a thin wrapper with the right interface around whatever model you want to use, and add it to your System. Once you have a general purpose pre-trained model and you want to make it easily available to users for running simulations, OpenMM-ML provides a higher level API. You create new subclasses of MLPotentialImpl and MLPotentialImplFactory, and register the factory. Here is the API, and here is the ANI implementation which can serve as an example. |
Thanks! And thanks for transferring, I was confused as to which ML-related repo would be the one to post to. |
Left a note on NEQUIP's page and got the following response, which is very promising. Still could be tricky for us higher-level users, but I am willing to try. |
Excited to see the ANI interface. I wonder how hard it would be to interface with NEQUIP? https://github.com/mir-group/nequip It's also PyTorch based and gets really exceptional performance on condensed matter systems. Currently NEQUIP runs MD with LAMMPS which is a pain.
The text was updated successfully, but these errors were encountered: