git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@11098 f3b2605a-c512-4ea7-a41b-209d697bcdaa

This commit is contained in:
sjplimp 2013-12-06 22:36:18 +00:00
parent 1c48803a54
commit a7b689a403
4 changed files with 26 additions and 14 deletions

View File

@ -85,12 +85,18 @@ created the set and how many files are in it. Read_restart then reads
the additional files. For example, if the restart file was specified
as save.% when it was written, then read_restart reads the files
save.base, save.0, save.1, ... save.P-1, where P is the number of
processors that created the restart file. The processors in the
current LAMMPS simulation share the work of reading these files; each
reads a roughly equal subset of the files. The number of processors
which created the set can be different the number of processors in the
current LAMMPS simulation. This can be a fast mode of input on
parallel machines that support parallel I/O.
processors that created the restart file.
</P>
<P>Note that P could be the total number of processors in the previous
simulation, or some subset of those processors, if the <I>fileper</I> or
<I>nfile</I> options were used when the restart file was written; see the
<A HREF = "restart.html">restart</A> and <A HREF = "write_restart.html">write_restart</A> commands
for details. The processors in the current LAMMPS simulation share
the work of reading these files; each reads a roughly equal subset of
the files. The number of processors which created the set can be
different the number of processors in the current LAMMPS simulation.
This can be a fast mode of input on parallel machines that support
parallel I/O.
</P>
<HR>

View File

@ -82,12 +82,18 @@ created the set and how many files are in it. Read_restart then reads
the additional files. For example, if the restart file was specified
as save.% when it was written, then read_restart reads the files
save.base, save.0, save.1, ... save.P-1, where P is the number of
processors that created the restart file. The processors in the
current LAMMPS simulation share the work of reading these files; each
reads a roughly equal subset of the files. The number of processors
which created the set can be different the number of processors in the
current LAMMPS simulation. This can be a fast mode of input on
parallel machines that support parallel I/O.
processors that created the restart file.
Note that P could be the total number of processors in the previous
simulation, or some subset of those processors, if the {fileper} or
{nfile} options were used when the restart file was written; see the
"restart"_restart.html and "write_restart"_write_restart.html commands
for details. The processors in the current LAMMPS simulation share
the work of reading these files; each reads a roughly equal subset of
the files. The number of processors which created the set can be
different the number of processors in the current LAMMPS simulation.
This can be a fast mode of input on parallel machines that support
parallel I/O.
:line

View File

@ -41,7 +41,7 @@ restart N file1 file2 keyword value ...
<PRE>restart 0
restart 1000 poly.restart
restart 1000 restart.*.equil
restart 10000 poly.%.1 poly.%.2
restart 10000 poly.%.1 poly.%.2 nfile 10
restart v_mystep poly.restart
</PRE>
<P><B>Description:</B>

View File

@ -31,7 +31,7 @@ keyword = {fileper} or {nfile} :l
restart 0
restart 1000 poly.restart
restart 1000 restart.*.equil
restart 10000 poly.%.1 poly.%.2
restart 10000 poly.%.1 poly.%.2 nfile 10
restart v_mystep poly.restart :pre
[Description:]