Skip to content

Conversation

nwinner
Copy link
Contributor

@nwinner nwinner commented Mar 27, 2023

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.

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
@jmmshn
Copy link
Contributor

jmmshn commented Mar 27, 2023

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:
https://github.com/materialsproject/jobflow/blob/main/docs/tutorials/4-generalized-makers.ipynb

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants