6.3 Restart continuity is a state-recovery experiment
These are unexecuted teaching inputs and starting models. Original diagrams are schematics, not calculated results. Validate version-specific syntax, licensed or authorized data, numerical convergence and the scientific model before using this workflow.
6.3.1 Model, units and provenance
Keep basis/potential files and executable versions traceable. Grid controls use Ry; common energy/force outputs use hartree and hartree/bohr. Read the unit in each output heading.
Shared inputs, conventions and evidence
6.3.2 Unexecuted inputs and explicit deltas
Use the accompanying instructions to identify the parent calculation and placement of every delta; a snippet is not automatically a standalone input. Preserve all blank-line and file-provenance requirements.
6.3.2.1 Input block 1
6.3.3 Worked investigation
Intuition. Restarting MD means restoring phase-space and auxiliary state, not merely loading the last coordinates. Velocities, cell, thermostat/barostat variables, random-number state where relevant and electronic guesses all matter. A wavefunction restart accelerates electronic convergence but is not the whole MD checkpoint. Use a short diagnostic trajectory whose files you can inspect before trusting a long queue-limited run.
Original control. Preserve the generated CP2K text restart and its matching electronic restart files. To continue through an input that explicitly references it, add a root-level section:
See input block 1 above.
Replace the filename with the actual saved checkpoint, not an assumed prefix. Review the resolved restart controls and generated input for the installed version. If intentionally changing ensemble or temperature, select documented restart flags to avoid restoring an old setting unexpectedly; that is a new stage, not the identical-continuation test. Copy the checkpoint into a new run directory before launch so the original remains recoverable.
Workflow. 1. Run a short continuous trajectory as a reference. 2. From the same initial state, run a split trajectory with a planned stop and checkpoint. 3. Continue from the checkpoint with the same executable, model, parallel layout and ensemble as far as practicable. 4. Compare the first resumed coordinates, velocities, time, step, cell and energy against the matching reference point. 5. Check that no duplicated boundary frame or omitted interval is introduced when joining analysis files. 6. Inspect longer-time statistical agreement without demanding bitwise identical chaotic trajectories across different parallel layouts or builds.
Interpretation and tests. A small numerical difference may grow exponentially in chaotic dynamics without invalidating ensemble statistics. An immediate large jump in energy, temperature or volume suggests incomplete state restoration or a mismatched input. A trajectory that restarts at time zero with randomized velocities is a new segment and must not be presented as exact continuation. Stochastic thermostats require appropriate random-state handling to reproduce an exact path; otherwise compare statistically valid independent paths and describe the distinction.
Pitfalls and limits. A scheduler termination during file writing can leave a partial checkpoint; keep backups and validate parsing before deleting earlier files. Binary wavefunction files may depend on architecture/build compatibility. Renaming a project can change file discovery. Copying only .xyz loses velocities and other state. Restart selection should not silently restore old coordinates after a user intentionally supplied new ones. Read the effective output rather than assuming precedence.
Exercise. Create a restart audit with expected next step/time, atom count, cell, velocity checksum or norm, electronic settings and output-file merge rules. Simulate a missing wavefunction file while retaining the MD checkpoint and explain the difference between electronic recomputation and loss of nuclear state. Do not deliberately destroy the only checkpoint.
Diagram. Continuous line versus split line connected by a checkpoint bundle containing position, velocity, cell and auxiliary state icons; a separate wfn icon feeds the SCF guess. EN: state checkpoint, electronic guess, continuity test, duplicate-frame check.
6.3.4 Related calculations
- 6.2 NVT and NpT answer different ensemble questions
- 6.4 RDF, mean-square displacement and honest uncertainty