Closed abhardwaj73 closed 8 months ago
Hey @abhardwaj73 This is probably because the auto_ismear
behavior changed recently in atomate2 but the r2SCAN WF didn't update to accommodate that. Here, atomate2 is trying to run the relaxation with ISMEAR = -5
@janosh, do you want to update auto_ismear = False
in the MP set generators, or should I submit a PR?
Much obliged if you could fix that @esoteric-ephemera!
Done PR #673!
Thanks!
While using MPMetaGGADoubleRelaxMaker in atomate2, the following 2 errors have appeared in all 3 of my runs:
Although
custodian
handles them and updates the files (and the workflow finishes), is this something that can be added directly in the default settings of this workflow? Especially reading the WAVECAR part, ascustodian
deletes the WAVECAR file to resolve the issue. As the WAVECAR is quite big, and not used in the r2SCAN relax step, can it be avoided in printing?Steps to reproduce the behavior:
MP meta-GGA relax 2
step (andcustodian
's involvement)Here is the custodian.json file for this step, which tells the action it has taken: