... | ... | @@ -15,7 +15,7 @@ simulation: |
|
|
|
|
|
- Monitoring file – `nirvana.mon`
|
|
|
|
|
|
### Log file
|
|
|
## Log file
|
|
|
|
|
|
The log file `nirvana.log` is a structured text file. It serves to store
|
|
|
selected simulation parameters and to record the timeline of a
|
... | ... | @@ -30,7 +30,7 @@ well or not. In case NIRVANA encounters a *code-controlled* exception |
|
|
during runtime a message about the type of exception is written to
|
|
|
`nirvana.log` before the job is terminated.
|
|
|
|
|
|
### Snapshot files
|
|
|
## Snapshot files
|
|
|
|
|
|
A snapshot is a set of files which dumps the state of a simulation at
|
|
|
one point in time represented by the cycle number `_C.model`. Snapshot
|
... | ... | @@ -74,7 +74,7 @@ which store the last available snapshot in due course. `NIRLAST.#` is |
|
|
either renewed every `_C.freq_walltime` seconds as specified by the user
|
|
|
in `nirvana.par` or is overwritten by the latest produced snapshot.
|
|
|
|
|
|
### Monitoring file
|
|
|
## Monitoring file
|
|
|
|
|
|
The monitoring file `nirvana.mon` is a CSV-like counterpart to
|
|
|
`nirvana.log`. Data is stored in a line-by-line fashion with each line
|
... | ... | |