-
Notifications
You must be signed in to change notification settings - Fork 71
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #503 from JulienDoerner/Interrupt
Handling of interruptions
- Loading branch information
Showing
11 changed files
with
873 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
396 changes: 396 additions & 0 deletions
396
doc/pages/example_notebooks/interrupting_simulations/interrupt_candidateVector.ipynb
Large diffs are not rendered by default.
Oops, something went wrong.
355 changes: 355 additions & 0 deletions
355
doc/pages/example_notebooks/interrupting_simulations/interrupt_source.ipynb
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
Interrupting simulations on runtime | ||
------------------------------------------------ | ||
|
||
CRPropa simulations can be interrupted on runtime with the `SIGTERM` or `SIGINT` signals. | ||
If the user defines an output for the interruption (called `InterruptAction`) all candidates which are currently in the simulation will be passed to this output. | ||
In the error stream the user will see a message denoting the number of candidates which have not been started yet. | ||
If the simulation was run with a `candidateVector` as source, the indices of the candidates which have not been started yet will be printed or written to the file. | ||
For a simulation with a source interface, a restart with the missing number of candidates will be sufficient to continue the simulation. | ||
|
||
.. toctree:: | ||
:caption: Using a candidateVector as source | ||
:maxdepth: 1 | ||
|
||
example_notebooks/interrupting_simulations/interrupt_candidateVector.ipynb | ||
|
||
.. toctree:: | ||
:caption: Using a source interface | ||
:maxdepth: 1 | ||
|
||
example_notebooks/interrupting_simulations/interrupt_source.ipynb | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters