Having a problem running a job - files stop updating
Posted: Fri Feb 26, 2016 9:17 pm
Hi all,
I was hoping to run a problem by you. I have been trying to do a VASP calculation with a 30 atom cell, starting from a 6 atom cell and elongated in the b direction (though this supercell is "mixed phase"). In the past I have done a similar calculation with a 30 atom cell, starting from a 6 atom cell and elongated in the a direction and this was fine (again, this supercell was "mixed phase"). I am using the same POTCAR and INCAR (with the KPOINTS changing slightly based on the direction of elongation).
The problem I am running into is when I run this job, it starts running. However, after a small period of time (usually within a few hours), all the files stop updating even though the job says it's still running. The file with the steps and energy per step just stops updating, as do all the other files. There is no error message that comes up either - according to the queue, it says the job is still running despite nothing being updated.
I've tried running this on more than one server and more than once, and run into this problem every time. Has anyone encountered this, or know of ways to overcome this?
I was hoping to run a problem by you. I have been trying to do a VASP calculation with a 30 atom cell, starting from a 6 atom cell and elongated in the b direction (though this supercell is "mixed phase"). In the past I have done a similar calculation with a 30 atom cell, starting from a 6 atom cell and elongated in the a direction and this was fine (again, this supercell was "mixed phase"). I am using the same POTCAR and INCAR (with the KPOINTS changing slightly based on the direction of elongation).
The problem I am running into is when I run this job, it starts running. However, after a small period of time (usually within a few hours), all the files stop updating even though the job says it's still running. The file with the steps and energy per step just stops updating, as do all the other files. There is no error message that comes up either - according to the queue, it says the job is still running despite nothing being updated.
I've tried running this on more than one server and more than once, and run into this problem every time. Has anyone encountered this, or know of ways to overcome this?