-
Notifications
You must be signed in to change notification settings - Fork 103
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
Equation of State workflow for FHI-aims #889
Conversation
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.
nice work, esp. on the tests! 👍 lgtm
) | ||
|
||
@classmethod | ||
def from_parameters(cls, parameters: dict[str, Any], **kwargs) -> AimsEosMaker: |
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.
minor nitpick but i would prob call this from_params
for brevity.
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.
This method is usually called from_parameters
in aims workflows, I'd leave it as it is for compatibility
Hi, is there anything else we can do with the pull request? |
thanks again @ansobolev, i'll go ahead and merge this! 👍 |
* Added EOS FHI-aims workflow * Added tmp_path to phonon tests * Added test data for EOS workflow * Tests changed for older Pymatgen version * simplify from_parameters * Change the test reference value --------- Co-authored-by: Janosh Riebesell <[email protected]>
* Added EOS FHI-aims workflow * Added tmp_path to phonon tests * Added test data for EOS workflow * Tests changed for older Pymatgen version * simplify from_parameters * Change the test reference value --------- Co-authored-by: Janosh Riebesell <[email protected]>
Summary
Additional dependencies introduced (if any)
None
TODO (if any)
None
Checklist
Before a pull request can be merged, the following items must be checked:
The easiest way to handle this is to run the following in the correct sequence on
your local machine. Start with running
ruff
andruff format
on your new code. This willautomatically reformat your code to PEP8 conventions and fix many linting issues.
Run ruff on your code.
type check your code.
Note that the CI system will run all the above checks. But it will be much more
efficient if you already fix most errors prior to submitting the PR. It is highly
recommended that you use the pre-commit hook provided in the repository. Simply run
pre-commit install
and a check will be run prior to allowing commits.