-
Notifications
You must be signed in to change notification settings - Fork 38
Adding support for custom protocols #347
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
base: master
Are you sure you want to change the base?
Adding support for custom protocols #347
Conversation
For now, only implemented for QE and abinit, needs to be implemented for all Also, fixing a couple of bugs in the ACWF relax for ABINIT
|
Thanks, Giovanni! I'm not sure when I renamed the forces output in the plugin (it's even marked for backwards-compatibility), but great that you caught it. I'll give this a deeper look on Monday. |
|
After a second look, this looks reasonable to me and shouldn't be too hard to add for all the codes 👍🏼 |
This allows to override the protocol ones by the launching user by using a custom protocol
azadoks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
c912898 to
0ecc634
Compare
Very often one wants a custom protocol, but it's not convenient to add a protocol definition in this repo for every independent project. Therefore, I'm here supporting the possibility to pass the protocol as a dictionary.
Note: For now, only implemented for QE and abinit, needs to be implemented for all if we agree on how I did it.
Note: In this PR I also fixing a couple of bugs in the ACWF relax for ABINIT.