-
Notifications
You must be signed in to change notification settings - Fork 96
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
[WIP] Defects CP2K #280
base: main
Are you sure you want to change the base?
[WIP] Defects CP2K #280
Conversation
…nto cp2k-defects
I cannot for the life of me figure out why using the combined parent breaks everything, but I guess the multiple_input_updator can only go one level deep for inheriting
I'll look for a way to clean this up later
# Conflicts: # src/atomate2/cp2k/flows/core.py
# Conflicts: # src/atomate2/cp2k/schemas/task.py
Hi @nwinner, the flow is already in common. The parts that should be language agnostic have been left as abstract methods. I also added a tutorial on dealing with DFT-code agnostic workflows here: Maybe you can just do a PR for driving the CP2K defect calculations only and we can figure out the schema later after a bit of discussion. In short, I really think the workflow should only take you as far as the DefectEntry creation and Freysoldt correction. The final chempot stuff should be left to builders. |
WIP for my defects module.
The jobs/flows could be deleted if @jmmshn 's module moves into common. The builder for assimilating after the fact could be adjusted and added to common as well. To my knowledge there is no equivalent in VASP module. Its not totally code agnostic at the moment though.