Restart

DESCRIPTION

This keyword restarts a previously-failed job. This method is primarily intended for long jobs that involve sufficiently large amounts of intermediate data, so that saving the restart data in the checkpoint file would make the checkpoint file unmanageably enormous, which would defeat the purpose of having a checkpoint file separate from the read-write file. This procedure depends on naming the read-write file so that it will be saved if the job terminates abnormally, and then using it to restart.

For example, in a frequency calculation you would include following Link 0 commands:

%RWF=myrwf
%NoSave
%Chk=mychk
#P Freq …

input continues…

By default, any file which is named with a % line is retained when the job finishes. The %NoSave after the %RWF overrides this default, so that the read-write file will still be deleted if the job finishes normally (but will be left behind if the job terminates early).

Be careful about these points:

AVAILABILITY

Analytic frequency calculations, including properties like ROA and VCD with ONIOM; CCSD and EOM-CCSD calculations; NMR; Polar=OptRot; CID, CISD, CCD, QCISD and BD energies. Calculations that compute multiple geometries, such as geometry optimizations, IRCs, and numerical frequency calculations, are better just restarted off the checkpoint file as before.

RELATED KEYWORDS

Freq, EOM

EXAMPLES

The following input file will restart a job set up as described above:

%RWF=myrwf
%NoSave
%Chk=mychk
#P Restart

No other keywords are required in the route section, and no other input is needed.

 


Last update: 23 April 2013