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
If I understand correctly, atomate2.vasp.flows.matpes.MatPesStaticFlowMaker by default is a 3-step flow where the last static job is a PBE+U static calculation. This appears to be at odds with the MatPES dataset, which is a 2-step flow where the last static job is an r2SCAN calculation and no PBE+U calculation is carried out. If this is correct, it may be worthwhile to modify the dataclass such that it does not run the static3 by default and more closely matches the pre-print.