-
Notifications
You must be signed in to change notification settings - Fork 175
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
Gibbs Workflow -- Phonopy QHA refactor error #271
Comments
As far as I can tell, the whole Not sure if there would be a better way of writing this analysis step without using 'protected' attributes? |
@mkhorton the PhonopyQHA interface is just for the API -- it has always just created a QHA object actually |
Right, which is I guess why it was removed? |
It hasn't been removed though? |
Ah my mistake, I must have been looking at an old commit. |
Haha it's alright, I thought the same thing. This is where it is defined FYI: |
I am trying to run a QHA analysis with phonopy and just got this error. Do I have an old version of the code or is this still an issue? |
Hi @ehomer, sorry for the late reply. I think this bug has not been fixed actually -- I don't see any commits to the code since 2017. I ran the Gibbs workflow so long ago I'm not actually sure what edits I made to get things to work... this was also at the beginning of me starting as a grad student so I didn't do a great job contribution-wise. If my old branch might be of any use, here it is: https://github.com/mattmcdermott/atomate/tree/gibbs It's possible I'll revisit if/when I do phonopy stuff again, but if you are able to make a pull request with the fix that would be much appreciated :) |
Basic fix from PR #751 |
Thanks @jmmshn for addressing this!! |
The phonopy QHA code was refactored in July 2018 and the variable "_max_t_index" no longer exists. It is currently used here:
atomate/atomate/vasp/analysis/phonopy.py
Lines 39 to 41 in a2cfee5
This needs to be updated for the current version of phonopy to be used with the Gibbs workflow (should be able to use _len instead).
The text was updated successfully, but these errors were encountered: