There are three ways to specify the frequency of outputs:
time-based, cycle-based (a cycle is a top-grid timestep), and, for
cosmology simulations, redshift-based. There is also a shortened
smoothed by an SPH kernel. Set to 2 to also output smoothed dark
matter velocities and velocity dispersion. Set to 0 to turn off.
+ Number of nearest neighbors to smooth dark matter quantities over.
Set to 1 or 2 to write out star particle data gridded onto mesh.
This will be useful e.g. if you have lots of star particles in a
Set to 1 if you want to output the divergence and vorticity of
``Bfield``. Works in 2D and 3D.
- Number of nearest neighbors to smooth dark matter quantities over.
+ This parameter specifies the time (in code units) when the
+ calculation will halt. For cosmology simulations, this variable is
+ automatically set by ``CosmologyFinalRedshift``. *No default.*
+ The cycle (top grid timestep) at which the calculation stops. A
+ value of zero indicates that this criterion is not be used.
+ Causes the simulation to immediately stop when a specified level is
+ reached. Default value 0 (off), possible values are levels 1
+ through maximum number of levels in a given simulation.
+ After this many datadumps have been written, the code will exit. If
+ set to 0 (default), this option will not be used. Default: 0.
+ Causes the simulation to stop if the wall time exceeds ``StopCPUTime``.
+ The simulation will output if the wall time after the next
+ top-level timestep will exceed ``StopCPUTime``, assuming that the wall
+ time elapsed during a top-level timestep the same as the previous
+ timestep. In units of seconds. Default: 2.592e6 (30 days)
+ If set to 1, the simulation will stop if the wall time will exceed
+ ``StopCPUTime`` within the next top-level timestep and run a shell
+ script defined in ``ResubmitCommand`` that should resubmit the job
+ for the user. Default: 0.
+ Filename of a shell script that creates a queuing (e.g. PBS)
+ script from two arguments, the number of processors and parameter
+ file. This script is run by the root processor when stopping with
+ ``ResubmitOn``. An example script can be found in
+ input/resubmit.sh. Default: (null)
+``NewMovieLeftEdge``, ``NewMovieRightEdge`` (external)
+ These two parameters control the region for which the streaming
+ data are written. Default: ``DomainLeftEdge`` and ``DomainRightEdge``.
+ Controls how many timesteps on a level are skipped between outputs
+ in the streaming data. Streaming format is off if this equals
+ ``INT_UNDEFINED``. Default: ``INT_UNDEFINED``
+ Set to 1 to write streaming data as 3-D arrays. This should always
+ be set to 1 if using the streaming format. A previous version had
+ 2D maximum intensity projections, which now defunct. Default: 0.
+ Set to 1 to write the streaming data interpolated to vertices. Set
+ to 0 for cell-centered data. Default: 0.
+ Counter for streaming data files. This should equal the cycle
+ Timestep counter for the streaming data files.
+ A maximum of 6 data fields can be written in the streaming format.
+ The data fields are specified by the array element of
+ BaryonField, i.e. 0 = Density, 7 = HII
+ Density. For writing temperature, a special value of 1000 is used.
+ This should be improved to be more transparent in which fields will
+ be written. Any element that equals ``INT_UNDEFINED`` indicates no
+ field will be written. Default: ``INT_UNDEFINED`` x 6
+ Set to 1 to write all particles in the grids. Set to 2 to write
+ ONLY particles that aren't dark matter, e.g. stars. Set to 3/4 to
+ write ONLY particles that aren't dark matter into a file separate
+ from the grid info. (For example, ``MoviePackParticle_P000.hdf5``,
+ etc. will be the file name; this will be very helpful in speeding
+ up the access to the star particle data, especially for the
+ visualization or for the star particle. See ``AMRH5writer.C``) Set to 0
+ for no particle output. Default: 0.
+Simulation Identifiers and UUIDs
+These parameters help to track, identify and group datasets. For reference,
+`Universally Unique Identifiers
+<http://en.wikipedia.org/wiki/Universally_Unique_Identifier>`_ (UUIDs) are
+opaque identifiers using random 128-bit numbers, with an extremely low chance
+of collision. (See :ref:`SimulationNamesAndIdentifiers` for a longer
+description of these parameters.)
+ This is a character string without spaces (specifically, something
+ that can be picked by "%s"), that can be defined in a parameter
+ file, and will be written out in every following output, if it is
+ A UUID that will be written out in all of the following outputs.
+ Like ``MetaDataIdentifier``, an existing UUID will be kept, but if one
+ is not found, and new one will be generated.
+ A UUID created for each specific output.
+ If a ``MetaDataDatasetUUID`` UUID is found when the parameter file is
+ read in, it will written to the following datasets. This is used to
+ track simulations across restarts and parameter adjustments.
+ This is similar to ``MetaDataRestartDatasetUUID``, except it's used to
+ track which initial conditions were used.