When a job needs to be restarted several times before reaching completion, it is convenient to allow subsequent jobs to restart automatically rather than submitting them manually. For this, the initial job script needs to contain the logic for submitting subsequent jobs automatically. Obviously, the code that is being executed needs to be able to restart from an existing checkpoint generated from the previous run. The code also usually needs an updated version of the restart parameters. Therefore, the initial job script also needs to be equipped with the necessary updating procedure to allow the use of the existing checkpoint file and the new input parameters.
- Adapt the example script/workflow that has been prepared for this matter in the section about "Recursive Jobs" of the "Example Workflows" topic within this documentation: Example Workflows#RecursiveJobs .