From d1992eca70ddf526c4fa0e4a9ca0ccb471625a0e Mon Sep 17 00:00:00 2001 From: Ian Jauslin Date: Fri, 31 Jan 2025 21:59:41 -0500 Subject: [PATCH] interrupting lyapunov mentioned in README --- README.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 7cc5d0b..f8baca5 100644 --- a/README.md +++ b/README.md @@ -164,14 +164,15 @@ should be a `;` sperated list of `key=value` pairs. The possible keys are # Interrupting and resuming the computation -The `enstrophy` computation can be interrupted by sending Nstrophy the `SIGINT` -signal (e.g. by pressing `Ctrl-C`.) When Nstrophy receives the `SIGINT` signal, -it finishes its current step and writes the value of uk, either to `savefile` -if such a file was specified on the command line (using the `-s` flag), or to -`stderr`. In addition, when a `savefile` is specified it writes the command -that needs to be used to resume the computation (which essentially just sets -the appropriate `starting_time` and `init:file:` parameters. The data -written to the `savefile` is binary. +The `enstrophy` and `lyapunov` computations can be interrupted by sending +Nstrophy the `SIGINT` signal (e.g. by pressing `Ctrl-C`.) When Nstrophy +receives the `SIGINT` signal, it finishes its current step and writes the value +of uk, either to `savefile` if such a file was specified on the command line +(using the `-s` flag), or to `stderr`. In addition, when a `savefile` is +specified it writes the command that needs to be used to resume the computation +(which essentially just sets the appropriate `starting_time` and +`init:file:` parameters). The data written to the `savefile` is +binary. # License