View source for Restarting a GMIN run from a dump file

[[GMIN]] has a facility for restarting a run, as long as you have a GMIN.dump file. This means that if the job runs out of walltime, or you'd like to check if you really have found the global minimum, you can! These dump files are produced by default, every 1000 quenches. This interval can be modified by specification of the '''DUMPINT''' keyword - for example, to produce a dump file every 100 quenches:

<pre>
DUMPINT 100
</pre>

A shorter dump interval is recommended as system size (and therefore time/quench) increases. To restore a run, you need the '''RESTORE''' keyword. Here are two excerpts from example data files to demonstrate: 

Original data file:
<pre>
...
DUMPINT 100
STEPS 10000
SAVE 100
...
</pre>

data file for restarted run:
<pre>
...
DUMPINT 100
RESTORE GMIN.dump
STEPS 15000
SAVE 100
...
</pre>

The number of steps in the new data file should always be greater than in the original. In this case, the run is being restarted for a further 5000 quenches - 10000 + 5000 = 15000! The [[makerestart]] script does a lot of this for you.

===What if I want to change the value of SAVE?===
For large systems, it is nice to have the flexibility to change the number of structures that are tightly converged and dumped at the end of a run. This is because final quenches often take a long time, and you may only need to see one or two structures at the start of a long series of restart runs. If your dump file was generated by a version of [[GMIN]] compiled from the repository after 30/9/2008, you can do this by simply changing the value of '''SAVE''' in the new data file. If not, you need to make a simple modification to the dump file before you use it. Open the dump file in an editor e.g. vi:
<pre>
vi GMIN.dump
</pre>
In the new format, there is an extra line in the dump file which details the number of structures saved in the previous run. You need to input this manually if you have an old dump file, otherwise it will not be read in correctly. Here is an example, first the original - old dump file:
<pre>
 steps completed J1 in mc
   13000
COORDS
run number        1
       22.174000000000000       83.915460000000000       47.511220000000000
       21.352510000000000       82.452780000000000       47.773840000000000
       22.240000000000000       82.880000000000000       47.440000000000000
...
</pre>

Here, 13000 quenches have been done. Looking at the old data file above - we know that 100 structures were saved. This info must now be included in the dump file. The modification is performed as follows:
<pre>
 steps completed J1 in mc
   13000
     100
COORDS
run number        1
       22.174000000000000       83.915460000000000       47.511220000000000
       21.352510000000000       82.452780000000000       47.773840000000000
       22.240000000000000       82.880000000000000       47.440000000000000
...
</pre>
With this change done, you are now free to set '''SAVE''' to anything you'd like for the restart run.