atomate
atomate copied to clipboard
Gibbs Workflow -- Phonopy QHA refactor error
The phonopy QHA code was refactored in July 2018 and the variable "_max_t_index" no longer exists. It is currently used here:
https://github.com/hackingmaterials/atomate/blob/a2cfee5c7cad28e43b2756a4168959a92f4494dc/atomate/vasp/analysis/phonopy.py#L39-L41
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).
As far as I can tell, the whole PhonopyQHA interface has been removed/simplified and replaced with just a QHA object, the method signatures look similar though. In other words, this now gives the ._qha object directly, and ._max_t_index has become ._t_max.
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:
https://github.com/atztogo/phonopy/blob/b7cff9090ae17be41b209f6b89a6f49cd83c36ab/phonopy/api_qha.py#L38
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 still need to check the results in detail and add tests.
Thanks @jmmshn for addressing this!!