ABINIT Discussion Forums

I apologize if this is already in the documentation -- I have looked but cannot find it. My student is running abinit on a machine with queues, and so each job is time limited. If the job runs out of time it is killed and the results lost. Is there a flag in the input file that tells abinit to stop once a time limit is reached?

I don't think so. I have the same problem. The real issue is that there is no "check point file" analogous to what some codes do. However, depending on what calculation you are trying to do, there are a number of options. For example:

First, the approach I use most often (also to sneak onto the high priority queues as much as I can) is NOT to use the multi-data-set facilities, but to do the calculations piecemeal and recombine results. Thus, for response functions, do the GS, then stop; then do DDK, and stop; then do electric field, and stop; and so forth. But you could do even more---

During the self-consistent ground state calculation, if you were limited to a small amount of time, you could set nstep intentionally to something small, write the (unconverged) density and WF, and restart from them, over and over, until you reach convergence within the small amount of allotted steps.

For non-self-consistent calcs, say for band structures, you can simply compute a few k points at a time (non-self-consistently), writing the output to _EIG files, and then combine them at the end.

For response function calculations, you can do a run with all perturbations of interest turned on, then kill it after it tells you which are the irreducible ones, then run only those one at a time and use mrgddb to combine the DDB files.

Hi!

Isn't there a way where you put write END or STOP at the beginning of the input file and leave a blank line after it? I remember vaguely that I read about something like that in web documentation. It should stop cleanly the calculation before the next scf step. Maybe some of the older guys will remember it more correctly.

Igor L.

I think you are right. It used to be the case in the early days of the code (late 1980s). The trouble is we do not have access to the files while it is running. But if we can put in a stop by hand, then it must be easy to get abinit to effectively write this stop at a certain time. Or not?

Looks like the answer was in the documentation all along:

http://www.abinit.org/documentation/hel ... s.html#cpu