You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My initial inspection and tests reveals that it is not currently possible at plugin level. Although there is function _need_kp which would check whether kpoints are required to parse, in the base part of calculation plugin there is not exception and it goes for parsing and writing KPOINTS.
I need to investigate it in more detail to see if there would be workarounds to avoid modifying the plugin (which seems to me inevitable).
However, it is already seen in our workchain and fixing this issue should not be a big deal.
The text was updated successfully, but these errors were encountered:
My initial inspection and tests reveals that it is not currently possible at plugin level. Although there is function
_need_kp
which would check whetherkpoints
are required to parse, in thebase
part of calculation plugin there is not exception and it goes for parsing and writingKPOINTS
.I need to investigate it in more detail to see if there would be workarounds to avoid modifying the plugin (which seems to me inevitable).
However, it is already seen in our workchain and fixing this issue should not be a big deal.
The text was updated successfully, but these errors were encountered: