-
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
Lattice dynamics workflow using Pheasy #1063
base: main
Are you sure you want to change the base?
Lattice dynamics workflow using Pheasy #1063
Conversation
Modified some parts based on Janine's comments.
…atomate2 into atomate2_jz_pheasy
…group for crystals.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1063 +/- ##
========================================
- Coverage 4.32% 3.95% -0.38%
========================================
Files 178 192 +14
Lines 12911 14246 +1335
Branches 1278 1421 +143
========================================
+ Hits 559 564 +5
- Misses 12321 13651 +1330
Partials 31 31
|
no idea, never used or installed Alamode before. the best solution would be for them to publish pre-compiled wheels to PyPI so the code doesn't need to be re-compiled from scratch on every CI run as that's both slow and tends to be brittle |
@naik-aakash set up a docker for https://github.com/autoatml/autoplex but it has been a massive amount of work. Before this, we did the compilation on the repo. The slowness was a real problem. But not sure it is realistic to get the wheels. |
Could offer an issue bounty to get buy in. Happy to pitch 50$ |
@janosh thank you for offering this. I am unsure about the timescales for such solutions. We would like to have the workflow available as soom as possible due to the planned atomate2 paper. |
In that case, @JaGeo & @naik-aakash can you pls help with the compilation of alamode on the repo?
|
These are the exact commands to install Alamode:
|
Just add it to the workflow file. You can see how micromamba is used for installation here: atomate2/.github/workflows/testing.yml Line 61 in 3d55b2b
|
@@ -162,6 +162,7 @@ class BasePhononMaker(Maker, ABC): | |||
|
|||
kpath_scheme: str = "seekpath" | |||
code: str = None | |||
mp_id: str = None |
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 can be added as metadata.
@@ -202,6 +202,8 @@ def test_phonon_wf_vasp_only_displacements_no_structural_transformation( | |||
assert_allclose( | |||
responses[job.jobs[-1].uuid][1].output.primitive_matrix, | |||
((0, 1, 0), (0, 0, 1), (1, 0, 0)), | |||
rtol=1e-8, |
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.
@hrushikesh-s @naik-aakash and I are working on fixing these tests. I think I messed something up with the test files. I might have time later tonight. So, maybe skip those tests first.
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.
Aah. Sorry! Different test 😅. But I meant the update to the latest phonopy. Sorry!
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.
oh okay okay. I was wondering why suddenly the test_phonons.py file was failing 😅
Summary
Include a summary of major changes in bullet points:
Additional dependencies introduced (if any)
significantly useful functionality is perfectly fine, adding ones that add trivial
functionality, e.g., to use one single easily implementable function, is frowned upon.
Justify why that dependency is needed. Especially frowned upon are circular dependencies.
TODO (if any)
If this is a work-in-progress, write something about what else needs to be done.
Checklist
Work-in-progress pull requests are encouraged, but please put [WIP] in the pull request
title.
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.