Open leslie-zheng opened 2 weeks ago
@leslie-zheng Thanks 😃! I haven't looked at the code in detail yet. In any case, we would need tests and also install the pheasy code on the repo. The linting would need to pass as well.
Let me know if you need any advice for any of the points!
Attention: Patch coverage is 0%
with 585 lines
in your changes missing coverage. Please review.
Project coverage is 72.36%. Comparing base (
8d57884
) to head (93219ce
). Report is 20 commits behind head on main.
@leslie-zheng Thanks 😃! I haven't looked at the code in detail yet. In any case, we would need tests and also install the pheasy code on the repo. The linting would need to pass as well.
Let me know if you need any advice for any of the points!
Thanks Janine @JaGeo , I will make the linting check pass ASAP.
@JaGeo Hi Janine, will following all your suggestions and finish modifying it this weekend, thanks for the suggestions.
@leslie-zheng tgabk you! i think the goal should be that we reuse as much code as possible from the phonopy worfklow.
@leslie-zheng tgabk you! i think the goal should be that we reuse as much code as possible from the phonopy worfklow.
Hi Janine, Sure, I am working on it, already reuse the some repeated functions from phonopy section. After finish it again and will let you know.
@JaGeo Hi Janine, after finishing cleaning it up, and I test the whole workflow on our cluster. Take silicon as an example, it works well.
Hi @JaGeo , Maybe we can create a folder called phonon/ and move the /phonopy.py and /pheasy.py into? or a folder called lattice_dynamics/ instead.
@JaGeo Hi Janine, after finishing cleaning it up, and I test the whole workflow on our cluster. Take silicon as an example, it works well.
That's great. Could you add test workflows as well? There are many examples in the tests folder. Once this is done, I am happy to do further refactoring.
If you olan to add higher force constants as well, we can also keep the pheasy submodule for now.
@JaGeo Hi Janine, after finishing cleaning it up, and I test the whole workflow on our cluster. Take silicon as an example, it works well.
That's great. Could you add test workflows as well? There are many examples in the tests folder. Once this is done, I am happy to do further refactoring.
If you olan to add higher force constants as well, we can also keep the pheasy submodule for now.
Hi Janine @JaGeo , sure, will do it. yes, I am planning to add the higher-order force constants into.
Hi Janine @JaGeo ,
I finished adjusting the pheasy workflow based on previous linting checking again. And test the whole workflow again using silicon, working perfectly. For the pytest, I need help from you, I am not familiar with this process, cause I did not do it before. Could you please help me to write a example?, any documents from the pheasy workflow related to the pytest based on silicon case. I can packed it and shared with you.
best jiongzhi
@leslie-zheng yes, sure. Happy to help out with the tests
Summary
Include a summary of major changes in bullet points:
Additional dependencies introduced (if any)
TODO (if any)
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:
ruff
andruff format
on your new code. This will automatically reformat your code to PEP8 conventions and fix many linting issues.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.