<HTML>
<CENTER><A HREF = "Section_python.html">Previous Section</A> - <A HREF = "https://sparta.github.io">SPARTA WWW Site</A> -
<A HREF = "Manual.html">SPARTA Documentation</A> - <A HREF = "Section_commands.html#comm">SPARTA Commands</A> - <A HREF = "Section_history.html">Next
Section</A> 
</CENTER>






<HR>

<H3>12. Errors 
</H3>
<P>This section describes the various kinds of errors you can encounter
when using SPARTA.
</P>
12.1 <A HREF = "#err_1">Common problems</A><BR>
12.2 <A HREF = "#err_2">Reporting bugs</A><BR>
12.3 <A HREF = "#err_3">Error & warning messages</A> <BR>

<HR>

<A NAME = "err_1"></A><H4>12.1 Common problems 
</H4>
<P>If two SPARTA runs do not produce the same answer on different
machines or different numbers of processors, this is typically not a
bug.  On different machines, there can be numerical round-off in the
computations which causes slight differences in particle trajectories
or the number of particles, which will lead to numerical divergence of
the particle trajectores and averaged statistical quantities within a
few 100s or few 1000s of timesteps.  When running on different numbers
of processors, random numbers are used in different ways, so two
simulations can be immediately different.  However, the statistical
properties (e.g. overall particle temperature or per grid cell
temperature or surface energy flux) for the two runs on different
machines or on different numbers of processors should still be
similar.
</P>
<P>A SPARTA simulation typically has two stages, setup and run.  Most
SPARTA errors are detected at setup time; others like running out of
memory may not occur until the middle of a run.
</P>
<P>SPARTA tries to flag errors and print informative error messages so
you can fix the problem.  Of course, SPARTA cannot figure out physics
or numerical mistakes, like choosing too big a timestep or specifying
erroneous collision parameters.  If you run into errors that SPARTA
doesn't catch that you think it should flag, please send an email to
the <A HREF = "https://sparta.github.io/authors.html">developers</A>.
</P>
<P>If you get an error message about an invalid command in your input
script, you can determine what command is causing the problem by
looking in the log.sparta file, or using the <A HREF = "echo.html">echo command</A>
in your script or "-echo screen" as a <A HREF = "Section_start.html#start_7">command-line
argument</A> to see it on the screen.  For a
given command, SPARTA expects certain arguments in a specified order.
If you mess this up, SPARTA will often flag the error, but it may read
a bogus argument and assign a value that is valid, but not what you
wanted.
</P>
<P>Generally, SPARTA will print a message to the screen and logfile and
exit gracefully when it encounters a fatal error.  Sometimes it will
print a WARNING to the screen and logfile and continue on; you can
decide if the WARNING is important or not.  A WARNING message that is
generated in the middle of a run is only printed to the screen, not to
the logfile, to avoid cluttering up statistical output.  If SPARTA
crashes or hangs without spitting out an error message first then it
could be a bug (see the <A HREF = "#err_2">next section</A>) or one of the following
cases:
</P>
<P>SPARTA runs in the available memory a processor allows to be
allocated.  Most reasonable runs are compute limited, not memory
limited, so this shouldn't be a bottleneck on most platforms.  Almost
all large memory allocations in the code are done via C-style malloc's
which will generate an error message if you run out of memory.
Smaller chunks of memory are allocated via C++ "new" statements.  If
you are unlucky, you could run out of memory just when one of these
small requests is made, in which case the code will crash or hang (in
parallel), since SPARTA doesn't trap on those errors.
</P>
<P>Illegal arithmetic can cause SPARTA to run slow or crash.  This is
typically due to invalid physics and numerics that your simulation is
computing.  If you see wild statistical values or NaN values in your
SPARTA output, something is wrong with your simulation.  If you
suspect this is happening, it is a good idea to print out statistical
info frequently (e.g. every timestep) via the <A HREF = "stats.html">stats</A>
command so you can monitor what is happening.  Visualizing the
particle motion is also a good idea to insure your model is behaving
as you expect.
</P>
<P>In parallel, one way SPARTA can hang is due to how different MPI
implementations handle buffering of messages.  If the code hangs
without an error message, it may be that you need to specify an MPI
setting or two (usually via an environment variable) to enable
buffering or boost the sizes of messages that can be buffered.
</P>
<HR>

<A NAME = "err_2"></A><H4>12.2 Reporting bugs 
</H4>
<P>If you are confident that you have found a bug in SPARTA, please
follow these steps.
</P>
<P>Check the <A HREF = "https://sparta.github.io/bug.html">New features and bug
fixes</A> section of the <A HREF = "https://sparta.github.io">SPARTA web
site</A> to see if the bug has already been fixed.
</P>
<P>If not, please email a description of the problem to the
<A HREF = "https://sparta.github.io/authors.html">developers</A>.
</P>
<P>The most useful thing you can do to help us fix the bug is to isolate
the problem.  Run it on the smallest number of particles and grid
cells and fewest number of processors and with the simplest and
quick-to-run input script that reproduces the bug.  And try to
identify what command or combination of commands is causing the
problem.
</P>
<HR>

<H4><A NAME = "err_3"></A>12.3 Error & warning messages 
</H4>
<P>These are two alphabetic lists of the <A HREF = "#error">ERROR</A> and
<A HREF = "#warn">WARNING</A> messages SPARTA prints out and the reason why.  If the
explanation here is not sufficient, the documentation for the
offending command may help.  Error and warning messages also list the
source file and line number where the error was generated.  For
example, this message
</P>
<P>ERROR: Illegal create_particles command (create_particles.cpp:68)
</P>
<P>means that line #68 in the file src/create_particles.cpp generated the
error.  Looking in the source code may help you figure out what went
wrong.
</P>
<H4><A NAME = "error"></A>Errors: 
</H4>
<DL>

<DT><I>%d read_surf point pairs are too close</I> 

<DD>A pair of points is very close together, relative to grid size,
inidicating the grid is too large, or an ill-formed surface. 

<DT><I>%d read_surf points are not inside simulation box</I> 

<DD>If clipping was not performed, all points in surf file
must be inside (or on surface of) simulation box. 

<DT><I>%d surface elements not assigned to a collision model</I> 

<DD>All surface elements must be assigned to a surface collision model via
the surf_modify command before a simulation is perforemd. 

<DT><I>All universe/uloop variables must have same # of values</I> 

<DD>Self-explanatory. 

<DT><I>All variables in next command must be same style</I> 

<DD>Self-explanatory. 

<DT><I>Arccos of invalid value in variable formula</I> 

<DD>Argument of arccos() must be between -1 and 1. 

<DT><I>Arcsin of invalid value in variable formula</I> 

<DD>Argument of arcsin() must be between -1 and 1. 

<DT><I>Axi-symmetry is not yet supported in SPARTA</I> 

<DD>This error condition will be removed after axi-symmetry is
fully implemented. 

<DT><I>Axi-symmetry only allowed for 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>BPG edge on more than 2 faces</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Bad grid of processors for balance_grid block</I> 

<DD>Product of Px,Py,Pz must equal total number of processors. 

<DT><I>Bad grid of processors for create_grid</I> 

<DD>For block style, product of Px,Py,Pz must equal total number of
processors. 

<DT><I>Bigint setting in spatype.h is invalid</I> 

<DD>Size of bigint is less than size of smallint. 

<DT><I>Bigint setting in spatype.h is not compatible</I> 

<DD>Bigint size stored in restart file is not consistent with SPARTA
version you are running. 

<DT><I>Both restart files must use % or neither</I> 

<DD>Self-explanatory. 

<DT><I>Both sides of boundary must be periodic</I> 

<DD>Cannot specify a boundary as periodic only on the lo or hi side.  Must
be periodic on both sides. 

<DT><I>Bound_modify surf requires wall be a surface</I> 

<DD>The box boundary must be of style "s" to be assigned a surface
collision model. 

<DT><I>Bound_modify surf_collide ID is unknown</I> 

<DD>Self-explanatory. 

<DT><I>Boundary command after simulation box is defined</I> 

<DD>The boundary command cannot be used after a read_data, read_restart,
or create_box command. 

<DT><I>Box boundary not assigned a surf_collide ID</I> 

<DD>Any box boundary of style "s" must be assigned to a surface collision
model via the bound_modify command, before a simulation is performed. 

<DT><I>Box bounds are invalid</I> 

<DD>The box boundaries specified in the read_data file are invalid.  The
lo value must be less than the hi value for all 3 dimensions. 

<DT><I>Box ylo must be 0.0 for axi-symmetric model</I> 

<DD>Self-explanatory. 

<DT><I>Can only use -plog with multiple partitions</I> 

<DD>Self-explanatory.  See doc page discussion of command-line switches. 

<DT><I>Can only use -pscreen with multiple partitions</I> 

<DD>Self-explanatory.  See doc page discussion of command-line switches. 

<DT><I>Cannot add new species to mixture all or species</I> 

<DD>This is done automatically for these 2 mixtures when
each species is defined by the species command. 

<DT><I>Cannot balance grid before grid is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot create grid before simulation box is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot create grid when grid is already defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot create particles before grid is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot create particles before simulation box is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot create/grow a vector/array of pointers for %s</I> 

<DD>SPARTA code is making an illegal call to the templated memory
allocaters, to create a vector or array of pointers. 

<DT><I>Cannot create_box after simulation box is defined</I> 

<DD>A simulation box can only be defined once. 

<DT><I>Cannot open VSS parameter file %s</I> 

<DD>Self-explantory. 

<DT><I>Cannot open dir to search for restart file</I> 

<DD>Using a "*" in the name of the restart file will open the current
directory to search for matching file names. 

<DT><I>Cannot open dump file</I> 

<DD>The output file for the dump command cannot be opened.  Check that the
path and name are correct. 

<DT><I>Cannot open file %s</I> 

<DD>The specified file cannot be opened.  Check that the path and name are
correct. If the file is a compressed file, also check that the gzip
executable can be found and run. 

<DT><I>Cannot open file variable file %s</I> 

<DD>The specified file cannot be opened.  Check that the path and name are
correct. 

<DT><I>Cannot open fix ave/time file %s</I> 

<DD>The specified file cannot be opened.  Check that the path and name are
correct. 

<DT><I>Cannot open fix print file %s</I> 

<DD>The output file generated by the fix print command cannot be opened 

<DT><I>Cannot open gzipped file</I> 

<DD>SPARTA was compiled without support for reading and writing gzipped
files through a pipeline to the gzip program with -DSPARTA_GZIP. 

<DT><I>Cannot open input script %s</I> 

<DD>Self-explanatory. 

<DT><I>Cannot open log.sparta</I> 

<DD>The default SPARTA log file cannot be opened.  Check that the
directory you are running in allows for files to be created. 

<DT><I>Cannot open logfile</I> 

<DD>The SPARTA log file named in a command-line argument cannot be opened.
Check that the path and name are correct. 

<DT><I>Cannot open logfile %s</I> 

<DD>The SPARTA log file specified in the input script cannot be opened.
Check that the path and name are correct. 

<DT><I>Cannot open print file %s</I> 

<DD>Self-explanatory. 

<DT><I>Cannot open reaction file %s</I> 

<DD>Self-explanatory. 

<DT><I>Cannot open restart file %s</I> 

<DD>The specified file cannot be opened.  Check that the path and name are
correct.  If the file is a compressed file, also check that the gzip
executable can be found and run. 

<DT><I>Cannot open screen file</I> 

<DD>The screen file specified as a command-line argument cannot be
opened.  Check that the directory you are running in allows for files
to be created. 

<DT><I>Cannot open species file %s</I> 

<DD>Self-explanatory. 

<DT><I>Cannot open universe log file</I> 

<DD>For a multi-partition run, the master log file cannot be opened.
Check that the directory you are running in allows for files to be
created. 

<DT><I>Cannot open universe screen file</I> 

<DD>For a multi-partition run, the master screen file cannot be opened.
Check that the directory you are running in allows for files to be
created. 

<DT><I>Cannot read grid before simulation box is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot read grid when grid is already defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot read_restart after simulation box is defined</I> 

<DD>The read_restart command cannot be used after a read_data,
read_restart, or create_box command. 

<DT><I>Cannot read_surf after particles are defined</I> 

<DD>This is because the newly read surface objects may enclose particles. 

<DT><I>Cannot read_surf before grid ghost cells are defined</I> 

<DD>This needs to be documented if keep this restriction. 

<DT><I>Cannot read_surf before grid is defined</I> 

<DD>Self-explantory. 

<DT><I>Cannot redefine variable as a different style</I> 

<DD>An equal-style variable can be re-defined but only if it was
originally an equal-style variable. 

<DT><I>Cannot reset timestep with a time-dependent fix defined</I> 

<DD>The timestep cannot be reset when a fix that keeps track of elapsed
time is in place. 

<DT><I>Cannot run 2d simulation with nonperiodic Z dimension</I> 

<DD>Use the boundary command to make the z dimension periodic in order to
run a 2d simulation. 

<DT><I>Cannot set global surfmax when surfaces already exist</I> 

<DD>This setting must be made before any surfac elements are
read via the read_surf command. 

<DT><I>Cannot use collide_modify with no collisions defined</I> 

<DD>A collision style must be specified first. 

<DT><I>Cannot use cwiggle in variable formula between runs</I> 

<DD>This is a function of elapsed time. 

<DT><I>Cannot use dump_modify fileper without % in dump file name</I> 

<DD>Self-explanatory. 

<DT><I>Cannot use dump_modify nfile without % in dump file name</I> 

<DD>Self-explanatory. 

<DT><I>Cannot use fix inflow in y dimension for axisymmetric</I> 

<DD>This is because the y dimension boundaries cannot be
inflow boundaries for an axisymmetric model. 

<DT><I>Cannot use fix inflow in z dimension for 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Cannot use fix inflow n > 0 with perspecies yes</I> 

<DD>This is because the perspecies option calculates the
number of particles to insert itself. 

<DT><I>Cannot use fix inflow on periodic boundary</I> 

<DD>Self-explanatory. 

<DT><I>Cannot use group keyword with mixture all or species</I> 

<DD>This is because the groups for these 2 mixtures are
pre-defined. 

<DT><I>Cannot use include command within an if command</I> 

<DD>Self-explanatory. 

<DT><I>Cannot use non-rcb fix balance with a grid cutoff</I> 

<DD>This is because the load-balancing will generate a partitioning
of cells to processors that is dispersed and which will not work
with a grid cutoff >= 0.0. 

<DT><I>Cannot use ramp in variable formula between runs</I> 

<DD>This is because the ramp() function is time dependent. 

<DT><I>Cannot use specified create_grid options with more than one level</I> 

<DD>When defining a grid with more than one level, the other create_grid
keywords (stride, clump, block, etc) cannot be used.  The child grid
cells will be assigned to processors in round-robin order as explained
on the create_grid doc page. 

<DT><I>Cannot use swiggle in variable formula between runs</I> 

<DD>This is a function of elapsed time. 

<DT><I>Cannot use vdisplace in variable formula between runs</I> 

<DD>This is a function of elapsed time. 

<DT><I>Cannot use weight cell radius unless axisymmetric</I> 

<DD>An axisymmetric model is required for this style of cell weighting. 

<DT><I>Cannot use write_restart fileper without % in restart file name</I> 

<DD>Self-explanatory. 

<DT><I>Cannot use write_restart nfile without % in restart file name</I> 

<DD>Self-explanatory. 

<DT><I>Cannot weight cells before grid is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot write grid when grid is not defined</I> 

<DD>Self-explanatory. 

<DT><I>Cannot write restart file before grid is defined</I> 

<DD>Self-explanatory. 

<DT><I>Cell ID has too many bits</I> 

<DD>Cell IDs must fit in 32 bits (SPARTA small integer) or 64 bits (SPARTA
big integer), as specified by the -DSPARTA_SMALL, -DSPARTA_BIG, or
-DSPARTA_BIGBIG options in the low-level Makefile used to build
SPARTA.  See Section 2.2 of the manual for details.  And see Section
4.8 for details on how cell IDs are formatted. 

<DT><I>Cell type mis-match when marking on neigh proc</I> 

<DD>Grid cell marking as inside, outside, or overlapping with surface
elements failed.  Please report the issue to the SPARTA developers. 

<DT><I>Cell type mis-match when marking on self</I> 

<DD>Grid cell marking as inside, outside, or overlapping with surface
elements failed.  Please report the issue to the SPARTA developers. 

<DT><I>Cellint setting in spatype.h is not compatible</I> 

<DD>Cellint size stored in restart file is not consistent with SPARTA
version you are running. 

<DT><I>Collision mixture does not contain all species</I> 

<DD>The specified mixture must contain all species in the simulation so
that they can be assigned to collision groups. 

<DT><I>Collision mixture does not exist</I> 

<DD>Self-explantory. 

<DT><I>Compute ID for compute reduce does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute ID for fix ave/grid does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute ID for fix ave/surf does not exist</I> 

<DD>Self-explanatory.   

<DT><I>Compute ID for fix ave/time does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute ID must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Compute boundary mixture ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute grid mixture ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute reduce compute array is accessed out-of-range</I> 

<DD>An index for the array is out of bounds. 

<DT><I>Compute reduce compute calculates global or surf values</I> 

<DD>The compute reduce command does not operate on this kind of values.
The variable command has special functions that can reduce global
values. 

<DT><I>Compute reduce compute does not calculate a per-grid array</I> 

<DD>This is necessary if a column index is used to specify the compute. 

<DT><I>Compute reduce compute does not calculate a per-grid vector</I> 

<DD>This is necessary if no column index is used to specify the compute. 

<DT><I>Compute reduce compute does not calculate a per-particle array</I> 

<DD>This is necessary if a column index is used to specify the compute. 

<DT><I>Compute reduce compute does not calculate a per-particle vector</I> 

<DD>This is necessary if no column index is used to specify the compute. 

<DT><I>Compute reduce fix array is accessed out-of-range</I> 

<DD>An index for the array is out of bounds. 

<DT><I>Compute reduce fix calculates global values</I> 

<DD>A fix that calculates peratom or local values is required. 

<DT><I>Compute reduce fix does not calculate a per-grid array</I> 

<DD>This is necessary if a column index is used to specify the fix. 

<DT><I>Compute reduce fix does not calculate a per-grid vector</I> 

<DD>This is necessary if no column index is used to specify the fix. 

<DT><I>Compute reduce fix does not calculate a per-particle array</I> 

<DD>This is necessary if a column index is used to specify the fix. 

<DT><I>Compute reduce fix does not calculate a per-particle vector</I> 

<DD>This is necessary if no column index is used to specify the fix. 

<DT><I>Compute reduce fix does not calculate a per-surf array</I> 

<DD>This is necessary if a column index is used to specify the fix. 

<DT><I>Compute reduce fix does not calculate a per-surf vector</I> 

<DD>This is necessary if no column index is used to specify the fix. 

<DT><I>Compute reduce replace requires min or max mode</I> 

<DD>Self-explanatory. 

<DT><I>Compute reduce variable is not particle-style variable</I> 

<DD>This is the only style of variable that can be reduced. 

<DT><I>Compute sonine/grid mixture ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute surf mixture ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Compute used in variable between runs is not current</I> 

<DD>Computes cannot be invoked by a variable in between runs.  Thus they
must have been evaluated on the last timestep of the previous run in
order for their value(s) to be accessed.  See the doc page for the
variable command for more info. 

<DT><I>Could not create a single particle</I> 

<DD>The specified position was either not inside the simulation domain or
not inside a grid cell with no intersections with any defined surface
elements. 

<DT><I>Could not find compute ID to delete</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump grid compute ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump grid fix ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump grid variable name</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump image compute ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump image fix ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump modify compute ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump modify fix ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump modify variable name</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump particle compute ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump particle fix ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump particle variable name</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump surf compute ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump surf fix ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find dump surf variable name</I> 

<DD>Self-explanatory. 

<DT><I>Could not find fix ID to delete</I> 

<DD>Self-explanatory. 

<DT><I>Could not find split point in split cell</I> 

<DD>This is an error when calculating how a grid cell is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Could not find stats compute ID</I> 

<DD>Compute ID specified in stats_style command does not exist. 

<DT><I>Could not find stats fix ID</I> 

<DD>Fix ID specified in stats_style command does not exist. 

<DT><I>Could not find stats variable name</I> 

<DD>Self-explanatory. 

<DT><I>Could not find surf_modify sc-ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find surf_modify surf-ID</I> 

<DD>Self-explanatory. 

<DT><I>Could not find undump ID</I> 

<DD>A dump ID used in the undump command does not exist. 

<DT><I>Cound not find dump_modify ID</I> 

<DD>Self-explanatory. 

<DT><I>Create_box z box bounds must straddle 0.0 for 2d simulations</I> 

<DD>Self-explanatory. 

<DT><I>Create_grid nz value must be 1 for a 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Create_particles global option not yet implemented</I> 

<DD>Self-explantory. 

<DT><I>Create_particles mixture ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Create_particles single requires z = 0 for 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Create_particles species ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Created incorrect # of particles: %ld versus %ld</I> 

<DD>The create_particles command did not function
properly. 

<DT><I>Delete region ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Did not assign all restart particles correctly</I> 

<DD>One or more particles in the restart file were not assigned to a
processor.  Please report the issue to the SPARTA developers. 

<DT><I>Did not assign all restart split grid cells correctly</I> 

<DD>One or more split grid cells in the restart file were not assigned
to a processor.  Please report the issue to the SPARTA developers. 

<DT><I>Did not assign all restart sub grid cells correctly</I> 

<DD>One or more sub grid cells in the restart file were not assigned to a
processor.  Please report the issue to the SPARTA developers. 

<DT><I>Did not assign all restart unsplit grid cells correctly</I> 

<DD>One or more unsplit grid cells in the restart file were not assigned
to a processor.  Please report the issue to the SPARTA developers. 

<DT><I>Dimension command after simulation box is defined</I> 

<DD>The dimension command cannot be used after a read_data,
read_restart, or create_box command. 

<DT><I>Divide by 0 in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Dump every variable returned a bad timestep</I> 

<DD>The variable must return a timestep greater than the current timestep. 

<DT><I>Dump grid and fix not computed at compatible times</I> 

<DD>Fixes generate values on specific timesteps.  The dump grid output
does not match these timesteps. 

<DT><I>Dump grid compute does not calculate per-grid array</I> 

<DD>Self-explanatory. 

<DT><I>Dump grid compute does not compute per-grid info</I> 

<DD>Self-explanatory. 

<DT><I>Dump grid compute vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Dump grid fix does not compute per-grid array</I> 

<DD>Self-explanatory. 

<DT><I>Dump grid fix does not compute per-grid info</I> 

<DD>Self-explanatory. 

<DT><I>Dump grid fix vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Dump grid variable is not grid-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Dump image and fix not computed at compatible times</I> 

<DD>Fixes generate values on specific timesteps.  The dump image output
does not match these timesteps. 

<DT><I>Dump image cannot use grid and gridx/gridy/gridz</I> 

<DD>Can only use grid option or one or more of grid x,y,z options
by themselves, not together. 

<DT><I>Dump image compute does not have requested column</I> 

<DD>Self-explanatory. 

<DT><I>Dump image compute does not produce a vector</I> 

<DD>Self-explanatory. 

<DT><I>Dump image compute is not a per-grid compute</I> 

<DD>Self-explanatory. 

<DT><I>Dump image compute is not a per-surf compute</I> 

<DD>Self-explanatory. 

<DT><I>Dump image fix does not have requested column</I> 

<DD>Self-explanatory. 

<DT><I>Dump image fix does not produce a vector</I> 

<DD>Self-explanatory. 

<DT><I>Dump image fix does not produce per-grid values</I> 

<DD>Self-explanatory. 

<DT><I>Dump image fix does not produce per-surf values</I> 

<DD>Self-explanatory. 

<DT><I>Dump image persp option is not yet supported</I> 

<DD>Self-explanatory. 

<DT><I>Dump image requires one snapshot per file</I> 

<DD>Use a "*" in the filename. 

<DT><I>Dump modify compute ID does not compute per-particle array</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify compute ID does not compute per-particle info</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify compute ID does not compute per-particle vector</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify compute ID vector is not large enough</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify fix ID does not compute per-particle array</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify fix ID does not compute per-particle info</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify fix ID does not compute per-particle vector</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify fix ID vector is not large enough</I> 

<DD>Self-explanatory. 

<DT><I>Dump modify variable is not particle-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle and fix not computed at compatible times</I> 

<DD>Fixes generate values on specific timesteps.  The dump particle output
does not match these timesteps. 

<DT><I>Dump particle compute does not calculate per-particle array</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle compute does not calculate per-particle vector</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle compute does not compute per-particle info</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle compute vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle fix does not compute per-particle array</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle fix does not compute per-particle info</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle fix does not compute per-particle vector</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle fix vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Dump particle variable is not particle-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf and fix not computed at compatible times</I> 

<DD>Fixes generate values on specific timesteps.  The dump surf output
does not match these timesteps. 

<DT><I>Dump surf compute does not calculate per-surf array</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf compute does not compute per-surf info</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf compute vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf fix does not compute per-surf array</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf fix does not compute per-surf info</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf fix vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Dump surf variable is not surf-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Dump_modify buffer yes not allowed for this style</I> 

<DD>Not all dump styles allow dump_modify buffer yes.  See the dump_modify
doc page. 

<DT><I>Dump_modify region ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Duplicate cell ID in grid file</I> 

<DD>Parent cell IDs must be unique. 

<DT><I>Edge not part of 2 vertices</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Edge part of invalid vertex</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Edge part of same vertex twice</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Empty brackets in variable</I> 

<DD>There is no variable syntax that uses empty brackets.  Check
the variable doc page. 

<DT><I>Failed to allocate %ld bytes for array %s</I> 

<DD>The SPARTA simulation has run out of memory.  You need to run a
smaller simulation or on more processors. 

<DT><I>Failed to open FFmpeg pipeline to file %s</I> 

<DD>The specified file cannot be opened.  Check that the path and name are
correct and writable and that the FFmpeg executable can be found and run. 

<DT><I>Failed to reallocate %ld bytes for array %s</I> 

<DD>The SPARTA simulation has run out of memory.  You need to run a
smaller simulation or on more processors. 

<DT><I>File variable could not read value</I> 

<DD>Check the file assigned to the variable. 

<DT><I>Fix ID for compute reduce does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Fix ID for fix ave/grid does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Fix ID for fix ave/surf does not exist</I> 

<DD>Self-explanatory.   

<DT><I>Fix ID for fix ave/time does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Fix ID must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid compute array is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid compute does not calculate a per-grid array</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid compute does not calculate a per-grid vector</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid compute does not calculate per-grid values</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid fix array is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid fix does not calculate a per-grid array</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid fix does not calculate a per-grid vector</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid fix does not calculate per-grid values</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/grid variable is not grid-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/surf compute array is accessed out-of-range</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf compute does not calculate a per-surf array</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf compute does not calculate a per-surf vector</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf compute does not calculate per-surf values</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf fix array is accessed out-of-range</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf fix does not calculate a per-surf array</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf fix does not calculate a per-surf vector</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf fix does not calculate per-surf values</I> 

<DD>Self-explanatory.   

<DT><I>Fix ave/surf variable is not surf-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/time cannot use variable with vector mode</I> 

<DD>Variables produce scalar values. 

<DT><I>Fix ave/time columns are inconsistent lengths</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/time compute array is accessed out-of-range</I> 

<DD>An index for the array is out of bounds. 

<DT><I>Fix ave/time compute does not calculate a scalar</I> 

<DD>Self-explantory. 

<DT><I>Fix ave/time compute does not calculate a vector</I> 

<DD>Self-explantory. 

<DT><I>Fix ave/time compute does not calculate an array</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/time compute vector is accessed out-of-range</I> 

<DD>The index for the vector is out of bounds. 

<DT><I>Fix ave/time fix array is accessed out-of-range</I> 

<DD>An index for the array is out of bounds. 

<DT><I>Fix ave/time fix does not calculate a scalar</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/time fix does not calculate a vector</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/time fix does not calculate an array</I> 

<DD>Self-explanatory. 

<DT><I>Fix ave/time fix vector is accessed out-of-range</I> 

<DD>The index for the vector is out of bounds. 

<DT><I>Fix ave/time variable is not equal-style variable</I> 

<DD>Self-explanatory. 

<DT><I>Fix command before simulation box is defined</I> 

<DD>The fix command cannot be used before a read_data, read_restart, or
create_box command. 

<DT><I>Fix for fix ave/grid not computed at compatible time</I> 

<DD>Fixes generate values on specific timesteps.  Fix ave/grid is
requesting a value on a non-allowed timestep. 

<DT><I>Fix for fix ave/surf not computed at compatible time</I> 

<DD>Fixes generate their values on specific timesteps.  Fix ave/surf is
requesting a value on a non-allowed timestep. 

<DT><I>Fix for fix ave/time not computed at compatible time</I> 

<DD>Fixes generate their values on specific timesteps.  Fix ave/time
is requesting a value on a non-allowed timestep. 

<DT><I>Fix in variable not computed at compatible time</I> 

<DD>Fixes generate their values on specific timesteps.  The variable is
requesting the values on a non-allowed timestep. 

<DT><I>Fix inflow mixture ID does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Fix inflow used on outflow boundary</I> 

<DD>Self-explanatory. 

<DT><I>Fix used in compute reduce not computed at compatible time</I> 

<DD>Fixes generate their values on specific timesteps.  Compute reduce is
requesting a value on a non-allowed timestep. 

<DT><I>Found edge in same direction</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Found no restart file matching pattern</I> 

<DD>When using a "*" in the restart file name, no matching file was found. 

<DT><I>Gravity in y not allowed for axi-symmetric model</I> 

<DD>Self-explanatory. 

<DT><I>Gravity in z not allowed for 2d</I> 

<DD>Self-explanatory. 

<DT><I>Grid cell corner points on boundary marked as unknown = %d</I> 

<DD>Corner points of grid cells on the boundary of the simulation domain
were not all marked successfully as inside, outside, or overlapping
with surface elements.  Please report the issue to the SPARTA
developers. 

<DT><I>Grid cells marked as unknown = %d</I> 

<DD>Grid cell marking as inside, outside, or overlapping with surface
elements did not successfully mark all cells.  Please report the issue
to the SPARTA developers. 

<DT><I>Grid cutoff is longer than box length in a periodic dimension</I> 

<DD>This is not allowed.  Reduce the size of the cutoff specified by the
global gridcut command. 

<DT><I>Grid in/out other-mark error %d\n</I> 

<DD>Grid cell marking as inside, outside, or overlapping with surface
elements failed.  Please report the issue to the SPARTA developers. 

<DT><I>Grid in/out self-mark error %d for icell %d, icorner %d, connect %d %d, other cell %d, other corner %d, values %d %d\n</I> 

<DD>A grid cell was incorrectly marked as inside, outside, or overlapping
with surface elements.  Please report the issue to the SPARTA
developers. 

<DT><I>Grid-style variables are not yet implemented</I> 

<DD>Self-explanatory. 

<DT><I>Illegal ... command</I> 

<DD>Self-explanatory.  Check the input script syntax and compare to the
documentation for the command.  You can use -echo screen as a
command-line option when running SPARTA to see the offending line. 

<DT><I>Inconsistent surface to grid mapping in read_restart</I> 

<DD>When surface elements were mapped to grid cells after reading a
restart file, an inconsitent count of elements in a grid cell was
found, as compared to the original simulation, which should not
happen.  Please report the issue to the SPARTA developers. 

<DT><I>Incorrect format of parent cell in grid file</I> 

<DD>Number of words in a parent cell line was not the expected number. 

<DT><I>Incorrect line format in VSS parameter file</I> 

<DD>Number of parameters in a line read from file is not valid. 

<DT><I>Incorrect line format in species file</I> 

<DD>Line read did not have expected number of fields. 

<DT><I>Incorrect line format in surf file</I> 

<DD>Self-explanatory. 

<DT><I>Incorrect point format in surf file</I> 

<DD>Self-explanatory. 

<DT><I>Incorrect triangle format in surf file</I> 

<DD>Self-explanatory. 

<DT><I>Index between variable brackets must be positive</I> 

<DD>Self-explanatory. 

<DT><I>Input line quote not followed by whitespace</I> 

<DD>An end quote must be followed by whitespace. 

<DT><I>Invalid Boolean syntax in if command</I> 

<DD>Self-explanatory. 

<DT><I>Invalid Nx,Ny,Nz values in grid file</I> 

<DD>A Nx or Ny or Nz value for a parent cell is <= 0. 

<DT><I>Invalid SPARTA restart file</I> 

<DD>The file does not appear to be a SPARTA restart file since it does not
have the expected magic string at the beginning. 

<DT><I>Invalid attribute in dump grid command</I> 

<DD>Self-explanatory. 

<DT><I>Invalid attribute in dump modify command</I> 

<DD>Self-explantory. 

<DT><I>Invalid attribute in dump particle command</I> 

<DD>Self-explanatory. 

<DT><I>Invalid attribute in dump surf command</I> 

<DD>Self-explanatory. 

<DT><I>Invalid balance_grid style for non-uniform grid</I> 

<DD>Some balance styles can only be used when the grid is uniform.  See
the command doc page for details. 

<DT><I>Invalid call to ComputeGrid::post_process_grid()</I> 

<DD>This indicates a coding error.  Please report the issue to the SPARTA
developers. 

<DT><I>Invalid call to ComputeSonineGrid::post_process_grid()</I> 

<DD>This indicates a coding error.  Please report the issue to the SPARTA
developers. 

<DT><I>Invalid cell ID in grid file</I> 

<DD>A cell ID could not be converted into numeric format. 

<DT><I>Invalid character in species ID</I> 

<DD>The only allowed characters are alphanumeric, an underscore, a plus
sign, or a minus sign. 

<DT><I>Invalid collide style</I> 

<DD>The choice of collision style is unknown. 

<DT><I>Invalid color in dump_modify command</I> 

<DD>The specified color name was not in the list of recognized colors.
See the dump_modify doc page. 

<DT><I>Invalid color map min/max values</I> 

<DD>The min/max values are not consistent with either each other or
with values in the color map. 

<DT><I>Invalid command-line argument</I> 

<DD>One or more command-line arguments is invalid.  Check the syntax of
the command you are using to launch SPARTA. 

<DT><I>Invalid compute ID in variable formula</I> 

<DD>The compute is not recognized. 

<DT><I>Invalid compute property/grid field for 2d simulation</I> 

<DD>Fields that reference z-dimension properties cannot be used
in a 2d simulation. 

<DT><I>Invalid compute style</I> 

<DD>Self-explanatory. 

<DT><I>Invalid dump frequency</I> 

<DD>Dump frequency must be 1 or greater. 

<DT><I>Invalid dump grid field for 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Invalid dump image filename</I> 

<DD>The file produced by dump image cannot be binary and must
be for a single processor. 

<DT><I>Invalid dump image persp value</I> 

<DD>Persp value must be >= 0.0. 

<DT><I>Invalid dump image theta value</I> 

<DD>Theta must be between 0.0 and 180.0 inclusive. 

<DT><I>Invalid dump image zoom value</I> 

<DD>Zoom value must be > 0.0. 

<DT><I>Invalid dump movie filename</I> 

<DD>The file produced by dump movie cannot be binary or compressed
and must be a single file for a single processor. 

<DT><I>Invalid dump style</I> 

<DD>The choice of dump style is unknown. 

<DT><I>Invalid dump surf field for 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Invalid dump_modify threshhold operator</I> 

<DD>Operator keyword used for threshold specification in not recognized. 

<DT><I>Invalid fix ID in variable formula</I> 

<DD>The fix is not recognized. 

<DT><I>Invalid fix ave/time off column</I> 

<DD>Self-explantory. 

<DT><I>Invalid fix style</I> 

<DD>The choice of fix style is unknown. 

<DT><I>Invalid flag in grid section of restart file</I> 

<DD>Unrecognized entry in restart file. 

<DT><I>Invalid flag in header section of restart file</I> 

<DD>Unrecognized entry in restart file. 

<DT><I>Invalid flag in layout section of restart file</I> 

<DD>Unrecognized entry in restart file. 

<DT><I>Invalid flag in particle section of restart file</I> 

<DD>Unrecognized entry in restart file. 

<DT><I>Invalid flag in peratom section of restart file</I> 

<DD>The format of this section of the file is not correct. 

<DT><I>Invalid flag in surf section of restart file</I> 

<DD>Unrecognized entry in restart file. 

<DT><I>Invalid image up vector</I> 

<DD>Up vector cannot be (0,0,0). 

<DT><I>Invalid immediate variable</I> 

<DD>Syntax of immediate value is incorrect. 

<DT><I>Invalid keyword in compute property/grid command</I> 

<DD>Self-explantory. 

<DT><I>Invalid keyword in stats_style command</I> 

<DD>One or more specified keywords are not recognized. 

<DT><I>Invalid math function in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Invalid math/special function in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Invalid point index in line</I> 

<DD>Self-explanatory. 

<DT><I>Invalid point index in triangle</I> 

<DD>Self-explanatory. 

<DT><I>Invalid react style</I> 

<DD>The choice of reaction style is unknown. 

<DT><I>Invalid reaction coefficients in file</I> 

<DD>Self-explanatory. 

<DT><I>Invalid reaction formula in file</I> 

<DD>Self-explanatory. 

<DT><I>Invalid reaction style in file</I> 

<DD>Self-explanatory. 

<DT><I>Invalid reaction type in file</I> 

<DD>Self-explanatory. 

<DT><I>Invalid read_surf command</I> 

<DD>Self-explanatory. 

<DT><I>Invalid read_surf geometry transformation for 2d simulation</I> 

<DD>Cannot perform a transformation that changes z cooridinates of points
for a 2d simulation. 

<DT><I>Invalid region style</I> 

<DD>The choice of region style is unknown. 

<DT><I>Invalid replace values in compute reduce</I> 

<DD>Self-explanatory. 

<DT><I>Invalid reuse of surface ID in read_surf command</I> 

<DD>Surface IDs must be unique. 

<DT><I>Invalid run command N value</I> 

<DD>The number of timesteps must fit in a 32-bit integer.  If you want to
run for more steps than this, perform multiple shorter runs. 

<DT><I>Invalid run command start/stop value</I> 

<DD>Self-explanatory. 

<DT><I>Invalid run command upto value</I> 

<DD>Self-explanatory. 

<DT><I>Invalid special function in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Invalid species ID in species file</I> 

<DD>Species IDs are limited to 15 characters. 

<DT><I>Invalid stats keyword in variable formula</I> 

<DD>The keyword is not recognized. 

<DT><I>Invalid surf_collide style</I> 

<DD>Self-explanatory. 

<DT><I>Invalid syntax in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Invalid use of library file() function</I> 

<DD>This function is called thru the library interface.  This
error should not occur.  Contact the developers if it does. 

<DT><I>Invalid variable evaluation in variable formula</I> 

<DD>A variable used in a formula could not be evaluated. 

<DT><I>Invalid variable in next command</I> 

<DD>Self-explanatory. 

<DT><I>Invalid variable name</I> 

<DD>Variable name used in an input script line is invalid. 

<DT><I>Invalid variable name in variable formula</I> 

<DD>Variable name is not recognized. 

<DT><I>Invalid variable style in special function next</I> 

<DD>Only file-style or atomfile-style variables can be used with next(). 

<DT><I>Invalid variable style with next command</I> 

<DD>Variable styles <I>equal</I> and <I>world</I> cannot be used in a next
command. 

<DT><I>Ionization and recombination reactions are not yet implemented</I> 

<DD>This error conditions will be removed after those reaction styles are
fully implemented. 

<DT><I>Irregular comm recv buffer exceeds 2 GB</I> 

<DD>MPI does not support a communication buffer that exceeds a 4-byte
integer in size. 

<DT><I>Label wasn't found in input script</I> 

<DD>Self-explanatory. 

<DT><I>Log of zero/negative value in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>MPI_SPARTA_BIGINT and bigint in spatype.h are not compatible</I> 

<DD>The size of the MPI datatype does not match the size of a bigint. 

<DT><I>Migrate cells send buffer exceeds 2 GB</I> 

<DD>MPI does not support a communication buffer that exceeds a 4-byte
integer in size. 

<DT><I>Mismatched brackets in variable</I> 

<DD>Self-explanatory. 

<DT><I>Mismatched compute in variable formula</I> 

<DD>A compute is referenced incorrectly or a compute that produces per-atom
values is used in an equal-style variable formula. 

<DT><I>Mismatched fix in variable formula</I> 

<DD>A fix is referenced incorrectly or a fix that produces per-atom
values is used in an equal-style variable formula. 

<DT><I>Mismatched variable in variable formula</I> 

<DD>A variable is referenced incorrectly or an atom-style variable that
produces per-atom values is used in an equal-style variable
formula. 

<DT><I>Mixture %s fractions exceed 1.0</I> 

<DD>The sum of fractions must not be > 1.0. 

<DT><I>Mixture ID must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Mixture group ID must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Mixture species is not defined</I> 

<DD>One or more of the species ID is unknown. 

<DT><I>Modulo 0 in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>More than one positive area with a negative area</I> 

<DD>SPARTA cannot determine which positive area the negative area is
inside of, if a cell is so large that it includes both positive and
negative areas. 

<DT><I>More than one positive volume with a negative volume</I> 

<DD>SPARTA cannot determine which positive volume the negative volume is
inside of, if a cell is so large that it includes both positive and
negative volumes. 

<DT><I>Must use -in switch with multiple partitions</I> 

<DD>A multi-partition simulation cannot read the input script from stdin.
The -in command-line option must be used to specify a file. 

<DT><I>Next command must list all universe and uloop variables</I> 

<DD>This is to insure they stay in sync. 

<DT><I>No dump grid attributes specified</I> 

<DD>Self-explanatory. 

<DT><I>No dump particle attributes specified</I> 

<DD>Self-explanatory. 

<DT><I>No dump surf attributes specified</I> 

<DD>Self-explanatory. 

<DT><I>No positive areas in cell</I> 

<DD>This is an error when calculating how a 2d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>No positive volumes in cell</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Non digit character between brackets in variable</I> 

<DD>Self-explantory. 

<DT><I>Number of groups in compute boundary mixture has changed</I> 

<DD>This mixture property cannot be changed after this compute command is
issued. 

<DT><I>Number of groups in compute grid mixture has changed</I> 

<DD>This mixture property cannot be changed after this compute command is
issued. 

<DT><I>Number of groups in compute sonine/grid mixture has changed</I> 

<DD>This mixture property cannot be changed after this compute command is
issued. 

<DT><I>Number of groups in compute surf mixture has changed</I> 

<DD>This mixture property cannot be changed after this compute command is
issued. 

<DT><I>Number of groups in compute tvib/grid mixture has changed</I> 

<DD>This mixture property cannot be changed after this compute command is
issued. 

<DT><I>Number of species in compute tvib/grid mixture has changed</I> 

<DD>This mixture property cannot be changed after this compute command is
issued. 

<DT><I>Numeric index is out of bounds</I> 

<DD>A command with an argument that specifies an integer or range of
integers is using a value that is less than 1 or greater than the
maximum allowed limit. 

<DT><I>Nz value in read_grid file must be 1 for a 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Only ylo boundary can be axi-symmetric</I> 

<DD>Self-explanatory.  See the boundary doc page for more details. 

<DT><I>Owned cells with unknown neighbors = %d</I> 

<DD>One or more grid cells have unknown neighbors which will prevent
particles from moving correctly.  Please report the issue to the
SPARTA developers. 

<DT><I>Parent cell child missing</I> 

<DD>Hierarchical grid traversal failed.  Please report the issue to the
SPARTA developers. 

<DT><I>Particle %d on proc %d hit inside of surf %d on step %ld</I> 

<DD>This error should not happen if particles start outside of physical
objects.  Please report the issue to the SPARTA developers. 

<DT><I>Particle %d,%d on proc %d is in invalid cell  on timestep %ld</I> 

<DD>The particle is in a cell indexed by a value that is out-of-bounds for
the cells owned by this processor. 

<DT><I>Particle %d,%d on proc %d is in split cell  on timestep %ld</I> 

<DD>This should not happend.  The particle should be in one
of the sub-cells of the split cell. 

<DT><I>Particle %d,%d on proc %d is outside cell  on timestep %ld</I> 

<DD>The particle's coordinates are not within the grid cell
it is supposed to be in. 

<DT><I>Particle vector in equal-style variable formula</I> 

<DD>Equal-style variables cannot use per-particle quantities. 

<DT><I>Particle-style variable in equal-style variable formula</I> 

<DD>Equal-style variables cannot use per-particle quantities. 

<DT><I>Partition numeric index is out of bounds</I> 

<DD>It must be an integer from 1 to the number of partitions. 

<DT><I>Per-particle compute in equal-style variable formula</I> 

<DD>Equal-style variables cannot use per-particle quantities. 

<DT><I>Per-particle fix in equal-style variable formula</I> 

<DD>Equal-style variables cannot use per-particle quantities. 

<DT><I>Per-processor particle count is too big</I> 

<DD>No processor can have more particle than fit in a 32-bit integer,
approximately 2 billion. 

<DT><I>Point appears first in more than one CLINE</I> 

<DD>This is an error when calculating how a 2d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Point appears last in more than one CLINE</I> 

<DD>This is an error when calculating how a 2d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Power by 0 in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Processor partitions are inconsistent</I> 

<DD>The total number of processors in all partitions must match the number
of processors SPARTA is running on. 

<DT><I>React tce can only be used with collide vss</I> 

<DD>Self-explanatory. 

<DT><I>Read_grid did not find parents section of grid file</I> 

<DD>Expected Parents section but did not find keyword. 

<DT><I>Read_surf did not find lines section of surf file</I> 

<DD>Expected Lines section but did not find keyword. 

<DT><I>Read_surf did not find points section of surf file</I> 

<DD>Expected Parents section but did not find keyword. 

<DT><I>Read_surf did not find triangles section of surf file</I> 

<DD>Expected Triangles section but did not find keyword. 

<DT><I>Region ID for dump custom does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Region intersect region ID does not exist</I> 

<DD>One or more of the region IDs specified by the region intersect
command does not exist. 

<DT><I>Region union region ID does not exist</I> 

<DD>One or more of the region IDs specified by the region union command
does not exist. 

<DT><I>Replacing a fix, but new style != old style</I> 

<DD>A fix ID can be used a 2nd time, but only if the style matches the
previous fix.  In this case it is assumed you with to reset a fix's
parameters.  This error may mean you are mistakenly re-using a fix ID
when you do not intend to. 

<DT><I>Request for unknown parameter from collide</I> 

<DD>VSS model does not have the parameter being requested. 

<DT><I>Restart file byte ordering is not recognized</I> 

<DD>The file does not appear to be a SPARTA restart file since it doesn't
contain a recognized byte-ordering flag at the beginning. 

<DT><I>Restart file byte ordering is swapped</I> 

<DD>The file was written on a machine with different byte-ordering than
the machine you are reading it on. 

<DT><I>Restart file incompatible with current version</I> 

<DD>This is probably because you are trying to read a file created with a
version of SPARTA that is too old compared to the current version. 

<DT><I>Restart file is a multi-proc file</I> 

<DD>The file is inconsistent with the filename specified for it. 

<DT><I>Restart file is not a multi-proc file</I> 

<DD>The file is inconsistent with the filename specified for it. 

<DT><I>Restart variable returned a bad timestep</I> 

<DD>The variable must return a timestep greater than the current timestep. 

<DT><I>Reuse of compute ID</I> 

<DD>A compute ID cannot be used twice. 

<DT><I>Reuse of dump ID</I> 

<DD>A dump ID cannot be used twice. 

<DT><I>Reuse of region ID</I> 

<DD>A region ID cannot be used twice. 

<DT><I>Reuse of surf_collide ID</I> 

<DD>A surface collision model ID cannot be used more than once. 

<DT><I>Run command before grid ghost cells are defined</I> 

<DD>Normally, ghost cells will be defined when the grid is created via the
create_grid or read_grid commands.  However, if the global gridcut
cutoff is set to a value >= 0.0, then ghost cells can only be defined
if the partiioning of cells to processors is clumped, not dispersed.
See the fix balance command for an explanation.  Invoking the fix
balance command with a clumped option will trigger ghost cells to be
defined. 

<DT><I>Run command before grid is defined</I> 

<DD>Self-explanatory. 

<DT><I>Run command start value is after start of run</I> 

<DD>Self-explanatory. 

<DT><I>Run command stop value is before end of run</I> 

<DD>Self-explanatory. 

<DT><I>Seed command has not been used</I> 

<DD>This command should appear near the beginning of your input script,
before any random numbers are needed by other commands. 

<DT><I>Sending particle to self</I> 

<DD>This error should not occur.  Please report the issue to the SPARTA
developers. 

<DT><I>Single area is negative, inverse donut</I> 

<DD>An inverse donut is a surface with a flow region interior to the donut
hole and also exterior to the entire donut.  This means the flow
regions are disconnected.  SPARTA cannot correctly compute the flow
area of this kind of object. 

<DT><I>Single volume is negative, inverse donut</I> 

<DD>An inverse donut is a surface with a flow region interior to the donut
hole and also exterior to the entire donut.  This means the flow
regions are disconnected.  SPARTA cannot correctly compute the flow
volume of this kind of object. 

<DT><I>Singlet BPG edge not on cell face</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Singlet CLINES point not on cell border</I> 

<DD>This is an error when calculating how a 2d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Small,big integers are not sized correctly</I> 

<DD>This error occurs whenthe sizes of smallint and bigint as defined in
src/spatype.h are not what is expected.  Please report the issue
to the SPARTA developers. 

<DT><I>Smallint setting in spatype.h is invalid</I> 

<DD>It has to be the size of an integer. 

<DT><I>Smallint setting in spatype.h is not compatible</I> 

<DD>Smallint size stored in restart file is not consistent with SPARTA
version you are running. 

<DT><I>Species %s did not appear in VSS parameter file</I> 

<DD>Self-explanatory. 

<DT><I>Species ID does not appear in species file</I> 

<DD>Could not find the requested species in the specified file. 

<DT><I>Species ID is already defined</I> 

<DD>Species IDs must be unique. 

<DT><I>Sqrt of negative value in variable formula</I> 

<DD>Self-explanatory. 

<DT><I>Stats and fix not computed at compatible times</I> 

<DD>Fixes generate values on specific timesteps.  The stats output
does not match these timesteps. 

<DT><I>Stats compute array is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Stats compute does not compute array</I> 

<DD>Self-explanatory. 

<DT><I>Stats compute does not compute scalar</I> 

<DD>Self-explanatory. 

<DT><I>Stats compute does not compute vector</I> 

<DD>Self-explanatory. 

<DT><I>Stats compute vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Stats every variable returned a bad timestep</I> 

<DD>The variable must return a timestep greater than the current timestep. 

<DT><I>Stats fix array is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Stats fix does not compute array</I> 

<DD>Self-explanatory. 

<DT><I>Stats fix does not compute scalar</I> 

<DD>Self-explanatory. 

<DT><I>Stats fix does not compute vector</I> 

<DD>Self-explanatory. 

<DT><I>Stats fix vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Stats variable cannot be indexed</I> 

<DD>A variable used as a stats keyword cannot be indexed.
E.g. v_foo must be used, not v_foo<B>100</B>. 

<DT><I>Stats variable is not equal-style variable</I> 

<DD>Only equal-style variables can be output with stats output, not
particle-style or grid-style or surf-style variables. 

<DT><I>Stats_modify every variable returned a bad timestep</I> 

<DD>The variable must return a timestep greater than the current timestep. 

<DT><I>Stats_modify int format does not contain d character</I> 

<DD>Self-explanatory. 

<DT><I>Substitution for illegal variable</I> 

<DD>Input script line contained a variable that could not be substituted
for. 

<DT><I>Support for writing images in JPEG format not included</I> 

<DD>SPARTA was not built with the -DSPARTA_JPEG switch in the Makefile. 

<DT><I>Support for writing images in PNG format not included</I> 

<DD>SPARTA was not built with the -DSPARTA_PNG switch in the Makefile. 

<DT><I>Support for writing movies not included</I> 

<DD>SPARTA was not built with the -DSPARTA_FFMPEG switch in the Makefile 

<DT><I>Surf file cannot contain lines for 3d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Surf file cannot contain triangles for 2d simulation</I> 

<DD>Self-explanatory. 

<DT><I>Surf file does not contain lines</I> 

<DD>Required for a 2d simulation. 

<DT><I>Surf file does not contain points</I> 

<DD>Self-explanatory. 

<DT><I>Surf file does not contain triangles</I> 

<DD>Required for a 3d simulation. 

<DT><I>Surf-style variables are not yet implemented</I> 

<DD>Self-explanatory. 

<DT><I>Surf_collide ID must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Surf_collide diffuse rotation invalid for 2d</I> 

<DD>Specified rotation vector must be in z-direction. 

<DT><I>Surf_collide diffuse variable is invalid style</I> 

<DD>It must be an equal-style variable. 

<DT><I>Surf_collide diffuse variable name does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Surface check failed with %d duplicate edges</I> 

<DD>One or more edges appeared in more than 2 triangles. 

<DT><I>Surface check failed with %d duplicate points</I> 

<DD>One or more points appeared in more than 2 lines. 

<DT><I>Surface check failed with %d infinitely thin line pairs</I> 

<DD>Two adjacent lines have normals in opposite directions
indicating the lines overlay each other. 

<DT><I>Surface check failed with %d infinitely thin triangle pairs</I> 

<DD>Two adjacent triangles have normals in opposite directions indicating
the triangles overlay each other. 

<DT><I>Surface check failed with %d points on lines</I> 

<DD>One or more points are on a line they are not an end point of, which
indicates an ill-formed surface. 

<DT><I>Surface check failed with %d points on triangles</I> 

<DD>One or more points are on a triangle they are not an end point of,
which indicates an ill-formed surface. 

<DT><I>Surface check failed with %d unmatched edges</I> 

<DD>One or more edges did not appear in a triangle, or appeared only once
and edge is not on surface of simulation box. 

<DT><I>Surface check failed with %d unmatched points</I> 

<DD>One or more points did not appear in a line, or appeared only once and
point is not on surface of simulation box. 

<DT><I>Timestep must be >= 0</I> 

<DD>Reset_timestep cannot be used to set a negative timestep. 

<DT><I>Too big a timestep</I> 

<DD>Reset_timestep timestep value must fit in a SPARTA big integer, as
specified by the -DSPARTA_SMALL, -DSPARTA_BIG, or -DSPARTA_BIGBIG
options in the low-level Makefile used to build SPARTA.  See
Section 2.2 of the manual for details. 

<DT><I>Too many surfs in one cell</I> 

<DD>Use the global surfmax command to increase this max allowed number of
surfs per grid cell. 

<DT><I>Too many timesteps</I> 

<DD>The cummulative timesteps must fit in a SPARTA big integer, as as
specified by the -DSPARTA_SMALL, -DSPARTA_BIG, or -DSPARTA_BIGBIG
options in the low-level Makefile used to build SPARTA.  See Section
2.2 of the manual for details. 

<DT><I>Too much buffered per-proc info for dump</I> 

<DD>Number of dumped values per processor cannot exceed a small integer
(~2 billion values). 

<DT><I>Too much per-proc info for dump</I> 

<DD>Number of local atoms times number of columns must fit in a 32-bit
integer for dump. 

<DT><I>Unbalanced quotes in input line</I> 

<DD>No matching end double quote was found following a leading double
quote. 

<DT><I>Unexpected end of data file</I> 

<DD>SPARTA hit the end of the data file while attempting to read a
section.  Something is wrong with the format of the data file. 

<DT><I>Unexpected end of grid file</I> 

<DD>Self-explantory. 

<DT><I>Unexpected end of surf file</I> 

<DD>Self-explanatory. 

<DT><I>Units command after simulation box is defined</I> 

<DD>The units command cannot be used after a read_data, read_restart, or
create_box command. 

<DT><I>Universe/uloop variable count < # of partitions</I> 

<DD>A universe or uloop style variable must specify a number of values >= to the
number of processor partitions. 

<DT><I>Unknown command: %s</I> 

<DD>The command is not known to SPARTA.  Check the input script. 

<DT><I>Unknown outcome in reaction</I> 

<DD>The specified type of the reaction is not encoded in the reaction
style. 

<DT><I>VSS parameters do not match current species</I> 

<DD>Species cannot be added after VSS colision file is read. 

<DT><I>Variable ID in variable formula does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable evaluation before simulation box is defined</I> 

<DD>Cannot evaluate a compute or fix or atom-based value in a variable
before the simulation has been setup. 

<DT><I>Variable for dump every is invalid style</I> 

<DD>Only equal-style variables can be used. 

<DT><I>Variable for dump image center is invalid style</I> 

<DD>Must be an equal-style variable. 

<DT><I>Variable for dump image persp is invalid style</I> 

<DD>Must be an equal-style variable. 

<DT><I>Variable for dump image phi is invalid style</I> 

<DD>Must be an equal-style variable. 

<DT><I>Variable for dump image theta is invalid style</I> 

<DD>Must be an equal-style variable. 

<DT><I>Variable for dump image zoom is invalid style</I> 

<DD>Must be an equal-style variable. 

<DT><I>Variable for restart is invalid style</I> 

<DD>It must be an equal-style variable. 

<DT><I>Variable for stats every is invalid style</I> 

<DD>It must be an equal-style variable. 

<DT><I>Variable formula compute array is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Variable formula compute vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Variable formula fix array is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Variable formula fix vector is accessed out-of-range</I> 

<DD>Self-explanatory. 

<DT><I>Variable has circular dependency</I> 

<DD>A circular dependency is when variable "a" in used by variable "b" and
variable "b" is also used by varaible "a".  Circular dependencies with
longer chains of dependence are also not allowed. 

<DT><I>Variable name between brackets must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for compute reduce does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for dump every does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for dump image center does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for dump image persp does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for dump image phi does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for dump image theta does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for dump image zoom does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for fix ave/grid does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for fix ave/surf does not exist</I> 

<DD>Self-explanatory.   

<DT><I>Variable name for fix ave/time does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for restart does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name for stats every does not exist</I> 

<DD>Self-explanatory. 

<DT><I>Variable name must be alphanumeric or underscore characters</I> 

<DD>Self-explanatory. 

<DT><I>Variable stats keyword cannot be used between runs</I> 

<DD>Stats keywords that refer to time (such as cpu, elapsed) do not make
sense in between runs. 

<DT><I>Vertex contains duplicate edge</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Vertex contains edge that doesn't point to it</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Vertex contains invalid edge</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Vertex has less than 3 edges</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>Vertex pointers to last edge are invalid</I> 

<DD>This is an error when calculating how a 3d grid is cut or split by
surface elements.  It should not normally occur.  Please report the
issue to the SPARTA developers. 

<DT><I>World variable count doesn't match # of partitions</I> 

<DD>A world-style variable must specify a number of values equal to the
number of processor partitions. 

<DT><I>Y cannot be periodic for axi-symmetric</I> 

<DD>Self-explanatory.  See the boundary doc page for more details. 

<DT><I>Z dimension must be periodic for 2d simulation</I> 

<DD>Self-explanatory. 


</DL>
<H4><A NAME = "warn"></A>Warnings: 
</H4>
<DL>

<DT><I>%d particles were in wrong cells on timestep %ld</I> 

<DD>This is the total number of particles that are incorrectly
matched to their grid cell. 

<DT><I>Grid cell interior corner points marked as unknown = %d</I> 

<DD>Corner points of grid cells interior to the simulation domain were not
all marked successfully as inside, outside, or overlapping with
surface elements.  This should normally not happen, but does
not affect simulations. 

<DT><I>More than one compute ke/particle</I> 

<DD>This may be inefficient since each such compute stores a vector
of length equal to the number of particles. 

<DT><I>Restart file used different # of processors</I> 

<DD>The restart file was written out by a SPARTA simulation running on a
different number of processors.  This means you will likely want to
re-balance the grid cells and particles across processors.  This can
be done using the balance or fix balance commands. 

<DT><I>Surface check found %d nearly infinitely thin line pairs</I> 

<DD>Two adjacent lines have normals in nearly opposite directions
indicating the lines nearly overlay each other. 

<DT><I>Surface check found %d nearly infinitely thin triangle pairs</I> 

<DD>Two adjacent triangles have normals in nearly opposite directions
indicating the triangles nearly overlay each other. 

<DT><I>Surface check found %d points nearly on lines</I> 

<DD>One or more points are nearly on a line they are not an end point of,
which indicates an ill-formed surface. 

<DT><I>Surface check found %d points nearly on triangles</I> 

<DD>One or more points are nearly on a triangle they are not an end point
of, which indicates an ill-formed surface. 


</DL>
</HTML>
