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:
Segmentation fault with empty POSCAR
Moderators: Global Moderator, Moderator
-
mwistey
- Newbie
- Posts: 12
- Joined: Fri Sep 26, 2014 2:22 am
- License Nr.: 5-1877
-
alex
- Hero Member
- Posts: 585
- Joined: Tue Nov 16, 2004 2:21 pm
- License Nr.: 5-67
- Location: Germany
Re: Segmentation fault with empty POSCAR
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
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