doc files for new parallel dump file read capability

  {ix},{iy},{iz} = image flags in each dimension

  {fx},{fy},{fz} = force components :pre

zero or more keyword/value pairs may be appended :l

keyword = {box} or {replace} or {purge} or {trim} or {add} or {label} or {scaled} or {wrapped} or {format} :l

keyword = {nfile} or {box} or {replace} or {purge} or {trim} or {add} or {label} or {scaled} or {wrapped} or {format} :l

  {nfile} value = Nfiles = how many parallel dump files exist

  {box} value = {yes} or {no} = replace simulation box with dump box

  {replace} value = {yes} or {no} = overwrite atoms with dump atoms

  {purge} value = {yes} or {no} = delete all atoms before adding dump atoms

If the dump filename specified as {file} ends with ".gz", the dump

file is read in gzipped format.  You cannot (yet) read a dump file

that was written in binary format with a ".bin" suffix, or to multiple

files via the "%" option in the dump file name.  See the

"dump"_dump.html command for details.

that was written in binary format with a ".bin" suffix.

You can read dump files that were written (in parallel) to multiple

files via the "%" wild-card character in the dump file name.  If any

specified dump file name contains a "%", they must all contain it.

See the "dump"_dump.html command for details.

The "%" wild-card character is only supported by the {native} format

for dump files, described next.

If reading parallel dump files, you must also use the {nfile} keyword

to tell LAMMPS how many parallel files exist, via its specified

{Nfiles} value.

The format of the dump file is selected through the {format} keyword.

If specified, it must be the last keyword used, since all remaining

a data file read in by a "read_data"_read_data.html command, before

using the rerun command.

Also note that the frequency of thermodynamic or dump output from the

rerun simulation will depend on settings made in the rerun script, the

same as for output from any LAMMPS simulation.  See further info below

as to what that means if the timesteps for snapshots read from dump

files do not match the specified output frequency.

:line

If more than one dump file is specified, the dump files are read one

after the other.  It is assumed that snapshot timesteps will be in

ascending order.  If a snapshot is encountered that is not in

ascending order, it will cause the rerun command to complete.

ascending order, it will skip the snapshot until it reads one that is.

This allows skipping of a duplicate snapshot (same timestep),

e.g. that appeared at the end of one file and beginning of the next.

However if you specify a series of dump files in an incorrect order

(with respect to the timesteps they contain), you may skip large

numbers of snapshots

The {first}, {last}, {every}, {skip} keywords determine which

snapshots are read from the dump file(s).  Snapshots are skipped until

The various forms of LAMMPS output, as defined by the

"thermo_style"_thermo_style.html, "thermo"_thermo.html,

"dump"_dump.html, and "restart"_restart.html commands occur on

specific timesteps.  If successive dump snapshots skip those

timesteps, then no output will be produced.  E.g. if you request

thermodynamic output every 100 steps, but the dump file snapshots are

every 1000 steps, then you will only see thermodynamic output every

1000 steps.

"dump"_dump.html, and "restart"_restart.html commands occur with

specified frequency, e.g. every N steps.  If the timestep for a dump

snapshot is not a multiple of N, then it will be read and processed,

but no output will be produced.  If you want output for every dump

snapshot, you can simply use N=1 for an output frequency, e.g. for

thermodyanmic output or new dump file output.

:line