Projections in VASP

[JaGeo]

@utf , I saw this updated wiki page of VASP recently: https://www.vasp.at/wiki/index.php/LORBIT

It might be interesting to keep this in mind for future changes. LORBIT=14 seems to be recommended now and LORBIT=12 needs to be run without symmetry for VASP versions older than VASP 6.

[utf]

Thanks for this suggestion. I think using ISMEAR=14 makes a lot of sense. We might have to couple it with a custodian feature that fixes it back to 11 if an error occurs (e.g with older versions of VASP)

[JaGeo]

Probably and where one switches off symmetry.

[jmmshn]

Additional note on this. I think ISMEAR=-5 + LORBIT=11 + NEDOS=3600 is extremely slow now due to interactions between the major changes made to the tetrahedron method and other parts of the VASP code.

I have not been able to finish the vast majority of these (fairly standard) calculations.

[JaGeo]

Did they maybe simply switch off the symmetry as a fix 😬

[jmmshn]

So the entire tetrahedron method was reimplemented to be a bit more modern. I have not examined the original VASP5 code enough to say for sure.