My Community

VASP 5.4.1 crashes with a segmentation fault if the POSCAR file is empty. Normally this would be obvious, but sometimes VASP writes an empty CONTCAR, and a job continuation script then overwrites the POSCAR with the empty file. A proper message to the user would be very helpful, especially since OUTCAR misleadingly ends with this line:
INCAR:

Well,

since there is no calculation starting it isn't a waste of computer time...
You could also check inside your script if POSCAR's size is 0 and do en error handling.

Cheers,

alex