| ... | ... | @@ -142,7 +142,7 @@ possible values or a numeric range. |
|
|
|
`runNIRVANA_PBS`, `runNIRVANA_SLURM`). The base filename has to
|
|
|
|
be specified without container id file extension, i.e., `NIR#`
|
|
|
|
or `NIRLAST` instead of `NIR#.#` or `NIRLAST.#` (cf. [Snapshot
|
|
|
|
files](#snapshot-files)).
|
|
|
|
files](3.3-Output-data#snapshot-files)).
|
|
|
|
|
|
|
|
- `02` (`_C.mod_max`, `_C.time_max`)
|
|
|
|
|
| ... | ... | @@ -161,17 +161,17 @@ possible values or a numeric range. |
|
|
|
|
|
|
|
- `_C.freq_log`: interval in units of timesteps at which the
|
|
|
|
NIRVANA log file `nirvana.log` and monitoring file `nirvana.mon`
|
|
|
|
(cf. [Output data](#Output-data)) is updated.
|
|
|
|
(cf. [Output data](3.3-Output-data)) is updated.
|
|
|
|
|
|
|
|
- `_C.freq_nir`: interval in units of timesteps at which NIRVANA
|
|
|
|
snapshots (cf. [Snapshot files](#snapshot-files)) are produced.
|
|
|
|
snapshots (cf. [Snapshot files](3.3-Output-data#snapshot-files)) are produced.
|
|
|
|
|
|
|
|
- `_C.freq_ana`: interval in units of timesteps at which the user
|
|
|
|
interface function `analysisUser()` is called for user-specific
|
|
|
|
analysis tasks (cf. [Data analysis](#data-analysis)).
|
|
|
|
analysis tasks (cf. [Data analysis](3.3-Output-data#data-analysis)).
|
|
|
|
|
|
|
|
- `_C.freq_walltime`: interval in seconds at which the special
|
|
|
|
snapshot `NIRLAST.#` (cf. [Snapshot files](#snapshot-files)) is
|
|
|
|
snapshot `NIRLAST.#` (cf. [Snapshot files](3.3-Output-data#snapshot-files)) is
|
|
|
|
renewed by overwriting existing older files.
|
|
|
|
|
|
|
|
**GEOMETRY**:
|
| ... | ... | @@ -359,7 +359,7 @@ possible values or a numeric range. |
|
|
|
(`_C.amr_eps[1]`), energy density (`_C.amr_eps[2]`), magnetic
|
|
|
|
field strength (`_C.amr_eps[3]`) and tracer variables
|
|
|
|
(`_C.amr_eps[4]`) in the derivatives-based mesh refinement
|
|
|
|
criterion (cf. [AMR](#adaptive-mesh-refinement)). A zero or
|
|
|
|
criterion (cf. [AMR](3.1-Code-basics#adaptive-mesh-refinement)). A zero or
|
|
|
|
negative value indicates that the respective component is not
|
|
|
|
used in the mesh refinement check.
|
|
|
|
|
| ... | ... | |