3
3
Outputs
4
4
=======
5
5
6
- Outputs from Parthenon are controled via ``<parthenon/output*> `` blocks,
6
+ Outputs from Parthenon are controlled via ``<parthenon/output*> `` blocks,
7
7
where ``* `` should be replaced by a unique integer for each block.
8
8
9
- To disable an output block without removing it from the intput file set
9
+ To disable an output block without removing it from the input file set
10
10
the block's ``dt < 0.0 ``.
11
11
12
12
In addition to time base outputs, two additional options to trigger
@@ -114,7 +114,7 @@ Restart Files
114
114
115
115
Parthenon allows users to output restart files for restarting a
116
116
simulation. The restart file captures the input file, so no input file
117
- is required to be specified. Parameters for the input can be overriden
117
+ is required to be specified. Parameters for the input can be overridden
118
118
in the usual way from the command line. At a future date we will allow
119
119
for users the ability to extensively edit the parameters stored within
120
120
the restart file.
@@ -134,8 +134,9 @@ This will produce an hdf5 (``.rhdf``) output file every 1 units of
134
134
simulation time that can be used for restarting the simulation.
135
135
136
136
To use this restart file, simply specify the restart file with a
137
- ``-r <restart.rhdf> `` at the command line. It is an error to specify an
138
- input file with the ``-i `` flag when using the restart option.
137
+ ``-r <restart.rhdf> `` at the command line. If both ``-r <restart.rhdf> ``
138
+ and ``-i <input.in> `` are specified, the simulation will be restarted from
139
+ the restart file with input parameters updated (or added) from the input file.
139
140
140
141
For physics developers: The fields to be output are automatically
141
142
selected as all the variables that have either the ``Independent `` or
@@ -179,7 +180,7 @@ Currently supported are
179
180
- weighting by volume and/or variable
180
181
181
182
The output format follows ``numpy `` convention, so that plotting data
182
- with Python based machinery should be straightfoward (see example below).
183
+ with Python based machinery should be straightforward (see example below).
183
184
In other words, 2D histograms use C-ordering corresponding to ``[x,y] ``
184
185
indexing with ``y `` being the fast index.
185
186
In general, histograms are calculated using inclusive left bin edges and
@@ -222,7 +223,7 @@ with the following parameters
222
223
223
224
- ``hist_names=STRING, STRING, STRING, ... `` (comma separated names)
224
225
The names of the histograms in this block.
225
- Will be used as preifx in the block as well as in the output file.
226
+ Will be used as prefix in the block as well as in the output file.
226
227
All histograms will be written to the same output file with the "group" in the
227
228
output corresponding to the histogram name.
228
229
- ``NAME_ndim=INT `` (either ``1 `` or ``2 ``)
@@ -338,7 +339,7 @@ Support for Ascent is disabled by default and must be enabled via ``PARTHENON_EN
338
339
In the input file, include a ``<parthenon/output*> `` block and specify ``file_type = ascent ``.
339
340
A ``dt `` parameter controls the frequency of outputs for simulations involving evolution.
340
341
*Note * that in principle Ascent can control its own output cadence (including
341
- automated tiggers ).
342
+ automated triggers ).
342
343
If you want to call Ascent on every cycle, set ``dt `` to a value smaller than the actual simulation ``dt ``.
343
344
The mandatory ``actions_file `` parameter points to a separate file that defines
344
345
Ascent actions in ``.yaml `` or ``.json `` format, see
@@ -352,7 +353,7 @@ If component label(s) are provided, they will be added as a suffix, e.g,.
352
353
Otherwise, an integer index is added for vectors/tensors with more than one component, i.e.,
353
354
vectors/tensors with a single component and without component labels will not contain a suffix.
354
355
The definition of component labels for variables is typically done by downstream codes
355
- so that the downstream documention should be consulted for more specific information.
356
+ so that the downstream documentation should be consulted for more specific information.
356
357
357
358
A ``<parthenon/output*> `` block might look like::
358
359
0 commit comments