write_restart_on_signal command

Purpose

Toggles whether a restart file is written when a simulation is aborted

Warning

GPU support for this command has not been tested and may not work as expected.

Syntax

write_restart_on_signal option

• option = required keyword

option = "yes" or "no"

Examples

write_restart_on_signal yes

Description

If activated (default) restart files will be written if either a SIGINT or a SIGUSR1 signal is intercepted by Aspherix®. Note that a restart file writing requests a reneighboring to take place so a total of two time steps might be computed before the restart files are written.

If a SIGUSR1 is intercepted the restart files will be written only. In case a SIGINT is intercepted the code will finish after the restart files are written. In case a second SIGINT is sent to the code, it will exit immediately, potentially without writing the restart files.

Output info:

The restart files are located in the execution path and their names are aspherix_auto_restart_%.basx where % is either base or the processor id that wrote part of the restart file.

For more details on the different signals that Aspherix® intercepts and how to use the written restart files please check the Sending signal to Aspherix® section.

Restrictions

None.

Related commands

write_restart

Default

Activated.