Description
diff --git a/doc/html/displace_atoms.html b/doc/html/displace_atoms.html
index 9208e97052..968c7345cd 100644
--- a/doc/html/displace_atoms.html
+++ b/doc/html/displace_atoms.html
@@ -128,9 +128,9 @@
displace_atoms command
Syntax
-
displace_atoms group-ID style args keyword value ...
-
-
+
+displace_atoms group-ID style args keyword value ...
+
- group-ID = ID of group of atoms to displace
- style = move or ramp or random or rotate
@@ -162,10 +162,10 @@ keyword = units
Examples
-
displace_atoms top move 0 -5 0 units box
-displace_atoms flow ramp x 0.0 5.0 y 2.0 20.5
-
-
+
+displace_atoms top move 0 -5 0 units box
+displace_atoms flow ramp x 0.0 5.0 y 2.0 20.5
+
Description
diff --git a/doc/html/dump.html b/doc/html/dump.html
index b47465bc33..d76697dbba 100644
--- a/doc/html/dump.html
+++ b/doc/html/dump.html
@@ -239,19 +239,19 @@ i_name = per-atom integer vector with name, managed by fix property/atom
Examples
-
dump myDump all atom 100 dump.atom
-dump myDump all atom/mpiio 100 dump.atom.mpiio
-dump myDump all atom/gz 100 dump.atom.gz
-dump 2 subgroup atom 50 dump.run.bin
-dump 2 subgroup atom 50 dump.run.mpiio.bin
-dump 4a all custom 100 dump.myforce.* id type x y vx fx
-dump 4b flow custom 100 dump.%.myforce id type c_myF[3] v_ke
-dump 4b flow custom 100 dump.%.myforce id type c_myF[*] v_ke
-dump 2 inner cfg 10 dump.snap.*.cfg mass type xs ys zs vx vy vz
-dump snap all cfg 100 dump.config.*.cfg mass type xs ys zs id type c_Stress[2]
-dump 1 all xtc 1000 file.xtc
-
-
+
+dump myDump all atom 100 dump.atom
+dump myDump all atom/mpiio 100 dump.atom.mpiio
+dump myDump all atom/gz 100 dump.atom.gz
+dump 2 subgroup atom 50 dump.run.bin
+dump 2 subgroup atom 50 dump.run.mpiio.bin
+dump 4a all custom 100 dump.myforce.* id type x y vx fx
+dump 4b flow custom 100 dump.%.myforce id type c_myF[3] v_ke
+dump 4b flow custom 100 dump.%.myforce id type c_myF[*] v_ke
+dump 2 inner cfg 10 dump.snap.*.cfg mass type xs ys zs vx vy vz
+dump snap all cfg 100 dump.config.*.cfg mass type xs ys zs id type c_Stress[2]
+dump 1 all xtc 1000 file.xtc
+
Description
@@ -347,12 +347,12 @@ or m = shrink wrapped with a minimum value. See the
bounding box which encloses the triclinic simulation box is output,
along with the 3 tilt factors (xy, xz, yz) of the triclinic box,
formatted as follows:
-
ITEM: BOX BOUNDS xy xz yz xx yy zz
-xlo_bound xhi_bound xy
-ylo_bound yhi_bound xz
-zlo_bound zhi_bound yz
-
-
+
+ITEM: BOX BOUNDS xy xz yz xx yy zz
+xlo_bound xhi_bound xy
+ylo_bound yhi_bound xz
+zlo_bound zhi_bound yz
+
The presence of the text “xy xz yz” in the ITEM line indicates that
the 3 tilt factors will be included on each of the 3 following lines.
This bounding box is convenient for many visualization programs. The
@@ -541,7 +541,7 @@ styles.
reference values from a compute or fix, like the
custom,
cfg, or
local styles, the bracketed index I can be specified using a
wildcard asterisk with the index to effectively specify multiple
-values. This takes the form “*” or “
n” or “n” or “m*n”. If N = the
+values. This takes the form “*” or “*n” or “n*” or “m*n”. If N = the
size of the vector (for
mode = scalar) or the number of columns in
the array (for
mode = vector), then an asterisk with no numeric
values means all indices from 1 to N. A leading asterisk means all
@@ -552,12 +552,12 @@ from m to n (inclusive).
had been listed one by one. E.g. these 2 dump commands are
equivalent, since the
compute stress/atom
command creates a per-atom array with 6 columns:
-
compute myPress all stress/atom NULL
-dump 2 all custom 100 tmp.dump id myPress[*]
-dump 2 all custom 100 tmp.dump id myPress[1] myPress[2] myPress[3] &
- myPress[4] myPress[5] myPress[6]
-
-
+
+compute myPress all stress/atom NULL
+dump 2 all custom 100 tmp.dump id myPress[*]
+dump 2 all custom 100 tmp.dump id myPress[1] myPress[2] myPress[3] &
+ myPress[4] myPress[5] myPress[6]
+
This section explains the local attributes that can be specified as
part of the local style.
@@ -598,11 +598,11 @@ be specified with a wildcard asterisk to effectively specify multiple
values.
Here is an example of how to dump bond info for a system, including
the distance and energy of each bond:
-
compute 1 all property/local batom1 batom2 btype
-compute 2 all bond/local dist eng
-dump 1 all local 1000 tmp.dump index c_1[1] c_1[2] c_1[3] c_2[1] c_2[2]
-
-
+
+compute 1 all property/local batom1 batom2 btype
+compute 2 all bond/local dist eng
+dump 1 all local 1000 tmp.dump index c_1[1] c_1[2] c_1[3] c_2[1] c_2[2]
+
This section explains the atom attributes that can be specified as
part of the custom and cfg styles.
diff --git a/doc/html/dump_custom_vtk.html b/doc/html/dump_custom_vtk.html
index 8bd838f671..b77890476a 100644
--- a/doc/html/dump_custom_vtk.html
+++ b/doc/html/dump_custom_vtk.html
@@ -182,15 +182,15 @@ v_name = per-atom vector calculated by an atom-style variable with name
Examples
-
dump dmpvtk all custom/vtk 100 dump*.myforce.vtk id type vx fx
-dump dmpvtp flow custom/vtk 100 dump*.%.displace.vtp id type c_myD[1] c_myD[2] c_myD[3] v_ke
-dump e_data all custom/vtk 100 dump*.vtu id type spin eradius fx fy fz eforce
-
-
+
+dump dmpvtk all custom/vtk 100 dump*.myforce.vtk id type vx fx
+dump dmpvtp flow custom/vtk 100 dump*.%.displace.vtp id type c_myD[1] c_myD[2] c_myD[3] v_ke
+dump e_data all custom/vtk 100 dump*.vtu id type spin eradius fx fy fz eforce
+
The style custom/vtk is similar to the custom style but
uses the VTK library to write data to VTK simple legacy or XML format
depending on the filename extension specified. This can be either
-**.vtk* for the legacy format or **.vtp* and **.vtu*, respectively,
+*.vtk for the legacy format or *.vtp and *.vtu, respectively,
for the XML format; see the VTK homepage for a detailed
description of these formats. Since this naming convention conflicts
with the way binary output is usually specified (see below),
diff --git a/doc/html/dump_h5md.html b/doc/html/dump_h5md.html
index 5980b4368d..e883ea5695 100644
--- a/doc/html/dump_h5md.html
+++ b/doc/html/dump_h5md.html
@@ -156,23 +156,23 @@ author value = quoted string
may specify a sub-interval to write the data only every N_element
iterations of the dump (i.e. every N*N_element time steps). This is
specified by the option
-
+
+every N_element
+
that follows directly the element declaration.
Examples
-
dump h5md1 all h5md 100 dump_h5md.h5 position image
-dump h5md1 all h5md 100 dump_h5md.h5 position velocity every 10
-dump h5md1 all h5md 100 dump_h5md.h5 velocity author "John Doe"
-
-
+
+dump h5md1 all h5md 100 dump_h5md.h5 position image
+dump h5md1 all h5md 100 dump_h5md.h5 position velocity every 10
+dump h5md1 all h5md 100 dump_h5md.h5 velocity author "John Doe"
+
Description
Dump a snapshot of atom coordinates every N timesteps in the
-HDF5 based H5MD file format (de Buyl).
+HDF5 based H5MD file format (de Buyl).
HDF5 files are binary, portable and self-describing. This dump style
will write only one file, on the root node.
Several dumps may write to the same file, by using file_from and
@@ -201,10 +201,10 @@ using the file_from keyword.
Typically, the species data is fixed. The following two commands
store the position data every 100 timesteps, with the image data, and
store once the species data in the same file.
-
dump h5md1 all h5md 100 dump.h5 position image
-write_dump all h5md dump.h5 file_from h5md1 species
-
-
+
+dump h5md1 all h5md 100 dump.h5 position image
+write_dump all h5md dump.h5 file_from h5md1 species
+
@@ -217,7 +217,7 @@ a limitation of the present dump h5md command and not of H5MD itself.
enabled if LAMMPS was built with that package. See the
Making LAMMPS section for more info. It also
requires (i) building the ch5md library provided with LAMMPS (See the
Making LAMMPS section for more info.) and
-(ii) having the
HDF5 library installed (C bindings are
+(ii) having the
HDF5 library installed (C bindings are
sufficient) on your system. The library ch5md is compiled with the
h5cc wrapper provided by the HDF5 library.
diff --git a/doc/html/dump_modify.html b/doc/html/dump_modify.html
index 492ef0a5f5..08afa5c7c6 100644
--- a/doc/html/dump_modify.html
+++ b/doc/html/dump_modify.html
@@ -128,9 +128,9 @@
dump_modify command
Syntax
-
dump_modify dump-ID keyword values ...
-
-
+
+dump_modify dump-ID keyword values ...
+
- dump-ID = ID of dump to modify
- one or more keyword/value pairs may be appended
@@ -228,16 +228,16 @@
Examples
-
dump_modify 1 format line "%d %d %20.15g %g %g" scale yes
-dump_modify 1 format float %20.15g scale yes
-dump_modify myDump image yes scale no flush yes
-dump_modify 1 region mySphere thresh x < 0.0 thresh epair >= 3.2
-dump_modify xtcdump precision 10000 sfactor 0.1
-dump_modify 1 every 1000 nfile 20
-dump_modify 1 every v_myVar
-dump_modify 1 amap min max cf 0.0 3 min green 0.5 yellow max blue boxcolor red
-
-
+
+dump_modify 1 format line "%d %d %20.15g %g %g" scale yes
+dump_modify 1 format float %20.15g scale yes
+dump_modify myDump image yes scale no flush yes
+dump_modify 1 region mySphere thresh x < 0.0 thresh epair >= 3.2
+dump_modify xtcdump precision 10000 sfactor 0.1
+dump_modify 1 every 1000 nfile 20
+dump_modify 1 every v_myVar
+dump_modify 1 amap min max cf 0.0 3 min green 0.5 yellow max blue boxcolor red
+
Description
@@ -318,19 +318,19 @@ to the dump file. The
every keyword cannot be used with the dump
dcd style.
For example, the following commands will
write snapshots at timesteps 0,10,20,30,100,200,300,1000,2000,etc:
-
variable s equal logfreq(10,3,10)
-dump 1 all atom 100 tmp.dump
-dump_modify 1 every v_s first yes
-
-
+
+variable s equal logfreq(10,3,10)
+dump 1 all atom 100 tmp.dump
+dump_modify 1 every v_s first yes
+
The following commands would write snapshots at the timesteps listed
in file tmp.times:
-
variable f file tmp.times
-variable s equal next(f)
-dump 1 all atom 100 tmp.dump
-dump_modify 1 every v_s
-
-
+
+variable f file tmp.times
+variable s equal next(f)
+dump 1 all atom 100 tmp.dump
+dump_modify 1 every v_s
+
Note
When using a file-style variable with the every keyword, the
@@ -406,11 +406,11 @@ an integer and you wish it to appear in the text dump file as a
(large) integer, then you need to use an appropriate format. For
example, these commands:
-
compute 1 all property/local batom1 batom2
-dump 1 all local 100 tmp.bonds index c_1[1] c_1[2]
-dump_modify 1 format "%d %0.0f %0.0f"
-
-
+
+compute 1 all property/local batom1 batom2
+dump 1 all local 100 tmp.bonds index c_1[1] c_1[2]
+dump_modify 1 format "%d %0.0f %0.0f"
+
will output the two atom IDs for atoms in each bond as integers. If
the dump_modify command were omitted, they would appear as
floating-point values, assuming they were large integers (more than 6
@@ -566,7 +566,7 @@ atoms of each type will be drawn in the image.
The specified type should be an integer from 1 to Ntypes = the
number of atom types. A wildcard asterisk can be used in place of or
in conjunction with the type argument to specify a range of atom
-types. This takes the form “*” or “n” or “n” or “m*n”. If N = the
+types. This takes the form “*” or “*n” or “n*” or “m*n”. If N = the
number of atom types, then an asterisk with no numeric values means
all types from 1 to N. A leading asterisk means all types from 1 to n
(inclusive). A trailing asterisk means all types from n to N
@@ -689,15 +689,15 @@ color map without having to specify where all the bin boundaries are.
atoms in individual molecules with a different color. See the
examples/pour/in.pour.2d.molecule input script for an example of how
this is used.
-
variable colors string &
+
+variable colors string &
"red green blue yellow white &
purple pink orange lime gray"
variable mol atom mol%10
dump 1 all image 250 image.*.jpg v_mol type &
zoom 1.6 adiam 1.5
-dump_modify 1 pad 5 amap 0 10 sa 1 10 ${colors}
-
-
+dump_modify 1 pad 5 amap 0 10 sa 1 10 ${colors}
+
In this case, 10 colors are defined, and molecule IDs are
mapped to one of the colors, even if there are 1000s of molecules.
@@ -711,7 +711,7 @@ set the color that bonds of each type will be drawn in the image.
The specified type should be an integer from 1 to Nbondtypes = the
number of bond types. A wildcard asterisk can be used in place of or
in conjunction with the type argument to specify a range of bond
-types. This takes the form “*” or “n” or “n” or “m*n”. If N = the
+types. This takes the form “*” or “*n” or “n*” or “m*n”. If N = the
number of bond types, then an asterisk with no numeric values means
all types from 1 to N. A leading asterisk means all types from 1 to n
(inclusive). A trailing asterisk means all types from n to N
diff --git a/doc/html/dump_molfile.html b/doc/html/dump_molfile.html
index 7986ce9562..60ee56baf7 100644
--- a/doc/html/dump_molfile.html
+++ b/doc/html/dump_molfile.html
@@ -143,11 +143,11 @@
Examples
-
dump mf1 all molfile 10 melt1.xml hoomd
-dump mf2 all molfile 10 melt2-*.pdb pdb .
-dump mf3 all molfile 50 melt3.xyz xyz .:/home/akohlmey/vmd/plugins/LINUX/molfile
-
-
+
+dump mf1 all molfile 10 melt1.xml hoomd
+dump mf2 all molfile 10 melt2-*.pdb pdb .
+dump mf3 all molfile 50 melt3.xyz xyz .:/home/akohlmey/vmd/plugins/LINUX/molfile
+
Description
diff --git a/doc/html/fix_addforce.html b/doc/html/fix_addforce.html
index 2e773e8d92..68b8540f51 100644
--- a/doc/html/fix_addforce.html
+++ b/doc/html/fix_addforce.html
@@ -154,11 +154,11 @@
Examples
-
fix kick flow addforce 1.0 0.0 0.0
-fix kick flow addforce 1.0 0.0 v_oscillate
-fix ff boundary addforce 0.0 0.0 v_push energy v_espace
-
-
+
+fix kick flow addforce 1.0 0.0 0.0
+fix kick flow addforce 1.0 0.0 v_oscillate
+fix ff boundary addforce 0.0 0.0 v_push energy v_espace
+
Description
@@ -232,10 +232,8 @@ by including their suffix, or you can use the
suffix command in your input script.
See Section_accelerate of the manual for
more instructions on how to use the accelerated styles effectively.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files.
The fix_modify energy option is supported by this
fix to add the potential “energy” inferred by the added force to the
diff --git a/doc/html/fix_append_atoms.html b/doc/html/fix_append_atoms.html
index d53243c00f..c15d2330aa 100644
--- a/doc/html/fix_append_atoms.html
+++ b/doc/html/fix_append_atoms.html
@@ -197,10 +197,8 @@ A box value selects standard distance units as defined by the
A lattice value means the distance units are in lattice spacings.
The lattice command must have been previously used to
define the lattice spacings.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files. None of the fix_modify options
are relevant to this fix. No global or per-atom quantities are stored
by this fix for access by various output commands. No parameter of this fix can
diff --git a/doc/html/fix_atom_swap.html b/doc/html/fix_atom_swap.html
index 862d6932af..a56f3b4f8b 100644
--- a/doc/html/fix_atom_swap.html
+++ b/doc/html/fix_atom_swap.html
@@ -156,11 +156,11 @@
Examples
-
fix 2 all atom/swap 1 1 29494 300.0 ke no types 1 2
-fix myFix all atom/swap 100 1 12345 298.0 region my_swap_region types 5 6
-fix SGMC all atom/swap 1 100 345 1.0 semi-grand yes types 1 2 3 mu 0.0 4.3 -5.0
-
-
+
+fix 2 all atom/swap 1 1 29494 300.0 ke no types 1 2
+fix myFix all atom/swap 100 1 12345 298.0 region my_swap_region types 5 6
+fix SGMC all atom/swap 1 100 345 1.0 semi-grand yes types 1 2 3 mu 0.0 4.3 -5.0
+
Description
@@ -250,9 +250,7 @@ system (the quantity used when performing GCMC moves),
you MUST enable the
fix_modify energy option for
that fix. The doc pages for individual
fix commands
specify if this should be done.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
This fix writes the state of the fix to binary restart files. This includes information about the random
number generator seed, the next timestep for MC exchanges, etc. See
the read_restart command for info on how to
diff --git a/doc/html/fix_ave_atom.html b/doc/html/fix_ave_atom.html
index b8459a1d96..72641a5006 100644
--- a/doc/html/fix_ave_atom.html
+++ b/doc/html/fix_ave_atom.html
@@ -140,22 +140,22 @@
one or more input values can be listed
value = x, y, z, vx, vy, vz, fx, fy, fz, c_ID, c_ID[i], f_ID, f_ID[i], v_name
-
x,y,z,vx,vy,vz,fx,fy,fz = atom attribute (position, velocity, force component)
-c_ID = per-atom vector calculated by a compute with ID
-c_ID[I] = Ith column of per-atom array calculated by a compute with ID, I can include wildcard (see below)
-f_ID = per-atom vector calculated by a fix with ID
-f_ID[I] = Ith column of per-atom array calculated by a fix with ID, I can include wildcard (see below)
-v_name = per-atom vector calculated by an atom-style variable with name
-
-
+
+x,y,z,vx,vy,vz,fx,fy,fz = atom attribute (position, velocity, force component)
+c_ID = per-atom vector calculated by a compute with ID
+c_ID[I] = Ith column of per-atom array calculated by a compute with ID, I can include wildcard (see below)
+f_ID = per-atom vector calculated by a fix with ID
+f_ID[I] = Ith column of per-atom array calculated by a fix with ID, I can include wildcard (see below)
+v_name = per-atom vector calculated by an atom-style variable with name
+
Examples
-
fix 1 all ave/atom 1 100 100 vx vy vz
-fix 1 all ave/atom 10 20 1000 c_my_stress[1]
-fix 1 all ave/atom 10 20 1000 c_my_stress[*]
-
-
+
+fix 1 all ave/atom 1 100 100 vx vy vz
+fix 1 all ave/atom 10 20 1000 c_my_stress[1]
+fix 1 all ave/atom 10 20 1000 c_my_stress[*]
+
Description
@@ -181,7 +181,7 @@ are the only ones that can be used with this fix since they produce
per-atom vectors.
Note that for values from a compute or fix, the bracketed index I can
be specified using a wildcard asterisk with the index to effectively
-specify multiple values. This takes the form “*” or “n” or “n” or
+specify multiple values. This takes the form “*” or “*n” or “n*” or
“m*n”. If N = the size of the vector (for mode = scalar) or the
number of columns in the array (for mode = vector), then an asterisk
with no numeric values means all indices from 1 to N. A leading
@@ -192,13 +192,13 @@ means all indices from m to n (inclusive).
had been listed one by one. E.g. these 2 fix ave/atom commands are
equivalent, since the
compute stress/atom
command creates a per-atom array with 6 columns:
-
compute my_stress all stress/atom NULL
-fix 1 all ave/atom 10 20 1000 c_my_stress[*]
-fix 1 all ave/atom 10 20 1000 c_my_stress[1] c_my_stress[1] &
- c_my_stress[3] c_my_stress[4] &
- c_my_stress[5] c_my_stress[6]
-
-
+
+compute my_stress all stress/atom NULL
+fix 1 all ave/atom 10 20 1000 c_my_stress[*]
+fix 1 all ave/atom 10 20 1000 c_my_stress[1] c_my_stress[1] &
+ c_my_stress[3] c_my_stress[4] &
+ c_my_stress[5] c_my_stress[6]
+
The Nevery, Nrepeat, and Nfreq arguments specify on what
timesteps the input values will be used in order to contribute to the
@@ -228,7 +228,7 @@ this is not what you want, consider averaging unwrapped coordinates,
which can be provided by the compute property/atom command via its xu,yu,zu
attributes.
-
If a value begins with “c_”, a compute ID must follow which has been
+
If a value begins with “c_”, a compute ID must follow which has been
previously defined in the input script. If no bracketed term is
appended, the per-atom vector calculated by the compute is used. If a
bracketed term containing an index I is appended, the Ith column of
@@ -236,7 +236,7 @@ the per-atom array calculated by the compute is used. Users can also
write code for their own compute styles and add them to LAMMPS. See the discussion above for how I can
be specified with a wildcard asterisk to effectively specify multiple
values.
-
If a value begins with “f_”, a fix ID must follow which has been
+
If a value begins with “f_”, a fix ID must follow which has been
previously defined in the input script. If no bracketed term is
appended, the per-atom vector calculated by the fix is used. If a
bracketed term containing an index I is appended, the Ith column of
@@ -246,15 +246,13 @@ compatible with Nevery, else an error will result. Users can also
write code for their own fix styles and add them to LAMMPS. See the discussion above for how I can
be specified with a wildcard asterisk to effectively specify multiple
values.
-
If a value begins with “v_”, a variable name must follow which has
+
If a value begins with “v_”, a variable name must follow which has
been previously defined in the input script as an atom-style variable Variables of style atom can reference
thermodynamic keywords, or invoke other computes, fixes, or variables
when they are evaluated, so this is a very general means of generating
per-atom quantities to time average.
-
Examples
-
fix 1 all ave/chunk 10000 1 10000 binchunk c_myCentro title1 "My output values"
-fix 1 flow ave/chunk 100 10 1000 molchunk vx vz norm sample file vel.profile
-fix 1 flow ave/chunk 100 5 1000 binchunk density/mass ave running
-fix 1 flow ave/chunk 100 5 1000 binchunk density/mass ave running
-
-
+
+fix 1 all ave/chunk 10000 1 10000 binchunk c_myCentro title1 "My output values"
+fix 1 flow ave/chunk 100 10 1000 molchunk vx vz norm sample file vel.profile
+fix 1 flow ave/chunk 100 5 1000 binchunk density/mass ave running
+fix 1 flow ave/chunk 100 5 1000 binchunk density/mass ave running
+
NOTE:
If you are trying to replace a deprectated fix ave/spatial command
with the newer, more flexible fix ave/chunk and compute chunk/atom commands, you simply need to split
@@ -242,7 +242,7 @@ ones that can be used with this fix since all other styles of variable
produce global quantities.
Note that for values from a compute or fix, the bracketed index I can
be specified using a wildcard asterisk with the index to effectively
-specify multiple values. This takes the form “*” or “n” or “n” or
+specify multiple values. This takes the form “*” or “*n” or “n*” or
“m*n”. If N = the size of the vector (for mode = scalar) or the
number of columns in the array (for mode = vector), then an asterisk
with no numeric values means all indices from 1 to N. A leading
@@ -253,11 +253,11 @@ means all indices from m to n (inclusive).
had been listed one by one. E.g. these 2 fix ave/chunk commands are
equivalent, since the
compute property/atom command creates, in this
case, a per-atom array with 3 columns:
-
compute myAng all property/atom angmomx angmomy angmomz
-fix 1 all ave/chunk 100 1 100 cc1 c_myAng[*] file tmp.angmom
-fix 2 all ave/chunk 100 1 100 cc1 c_myAng[1] c_myAng[2] c_myAng[3] file tmp.angmom
-
-
+
+compute myAng all property/atom angmomx angmomy angmomz
+fix 1 all ave/chunk 100 1 100 cc1 c_myAng[*] file tmp.angmom
+fix 2 all ave/chunk 100 1 100 cc1 c_myAng[1] c_myAng[2] c_myAng[3] file tmp.angmom
+
Note
This fix works by creating an array of size Nchunk by Nvalues
@@ -349,7 +349,7 @@ in the chunk on different timesteps were collected together as one set
of atoms to calculate their temperature. The compute allows the
center-of-mass velocity of each chunk to be subtracted before
calculating the temperature; this fix does not.
-
If a value begins with “c_”, a compute ID must follow which has been
+
If a value begins with “c_”, a compute ID must follow which has been
previously defined in the input script. If no bracketed integer is
appended, the per-atom vector calculated by the compute is used. If a
bracketed integer is appended, the Ith column of the per-atom array
@@ -357,7 +357,7 @@ calculated by the compute is used. Users can also write code for
their own compute styles and add them to LAMMPS.
See the discussion above for how I can be specified with a wildcard
asterisk to effectively specify multiple values.
-
If a value begins with “f_”, a fix ID must follow which has been
+
If a value begins with “f_”, a fix ID must follow which has been
previously defined in the input script. If no bracketed integer is
appended, the per-atom vector calculated by the fix is used. If a
bracketed integer is appended, the Ith column of the per-atom array
@@ -367,7 +367,7 @@ their values on certain timesteps, which must be compatible with
own fix styles and add them to LAMMPS. See the
discussion above for how I can be specified with a wildcard asterisk
to effectively specify multiple values.
-
If a value begins with “v_”, a variable name must follow which has
+
If a value begins with “v_”, a variable name must follow which has
been previously defined in the input script. Variables of style
atom can reference thermodynamic keywords and various per-atom
attributes, or invoke other computes, fixes, or variables when they
@@ -502,10 +502,8 @@ value of the units keyword is reduced, the coordinate values w
be in unitless reduced units (0-1). This is not true for the Coord1 value
of style bin/sphere or bin/cylinder which both represent radial
dimensions. Those values are always in distance units.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files. None of the fix_modify options
are relevant to this fix.
This fix computes a global array of values which can be accessed by
diff --git a/doc/html/fix_ave_correlate_long.html b/doc/html/fix_ave_correlate_long.html
index ccd754dbaf..a673143beb 100644
--- a/doc/html/fix_ave_correlate_long.html
+++ b/doc/html/fix_ave_correlate_long.html
@@ -139,13 +139,13 @@
one or more input values can be listed
value = c_ID, c_ID[N], f_ID, f_ID[N], v_name
-
c_ID = global scalar calculated by a compute with ID
-c_ID[I] = Ith component of global vector calculated by a compute with ID
-f_ID = global scalar calculated by a fix with ID
-f_ID[I] = Ith component of global vector calculated by a fix with ID
-v_name = global value calculated by an equal-style variable with name
-
-
+
+c_ID = global scalar calculated by a compute with ID
+c_ID[I] = Ith component of global vector calculated by a compute with ID
+f_ID = global scalar calculated by a fix with ID
+f_ID[I] = Ith component of global vector calculated by a fix with ID
+v_name = global value calculated by an equal-style variable with name
+
- zero or more keyword/arg pairs may be appended
- keyword = type or start or file or overwrite or title1 or title2 or ncorr or p or m
@@ -177,12 +177,12 @@
Examples
-
fix 1 all ave/correlate/long 5 1000 c_myTemp file temp.correlate
-fix 1 all ave/correlate/long 1 10000 &
- c_thermo_press[1] c_thermo_press[2] c_thermo_press[3] &
- type upper title1 "My correlation data" nlen 15 ncount 3
-
-
+
+fix 1 all ave/correlate/long 5 1000 c_myTemp file temp.correlate
+fix 1 all ave/correlate/long 1 10000 &
+ c_thermo_press[1] c_thermo_press[2] c_thermo_press[3] &
+ type upper title1 "My correlation data" nlen 15 ncount 3
+
Description
@@ -221,9 +221,7 @@ steps can be calculated.
4*ncorr*nlen*8 bytes. With the default values of the parameters, this
corresponds to about 10 KB.
For the meaning of the additional optional keywords, see the fix ave/correlate doc page.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
Since this fix in intended for the calculation of time correlation
functions over very long MD simulations, the information about this
fix is written automatically to binary restart files, so that the time
diff --git a/doc/html/fix_ave_histo.html b/doc/html/fix_ave_histo.html
index e8291ddeb4..bb07687b4a 100644
--- a/doc/html/fix_ave_histo.html
+++ b/doc/html/fix_ave_histo.html
@@ -145,15 +145,15 @@
one or more input values can be listed
value = x, y, z, vx, vy, vz, fx, fy, fz, c_ID, c_ID[N], f_ID, f_ID[N], v_name
-
x,y,z,vx,vy,vz,fx,fy,fz = atom attribute (position, velocity, force component)
-c_ID = scalar or vector calculated by a compute with ID
-c_ID[I] = Ith component of vector or Ith column of array calculated by a compute with ID, I can include wildcard (see below)
-f_ID = scalar or vector calculated by a fix with ID
-f_ID[I] = Ith component of vector or Ith column of array calculated by a fix with ID, I can include wildcard (see below)
-v_name = value(s) calculated by an equal-style or vector-style or atom-style variable with name
-v_name[I] = value calculated by a vector-style variable with name
-
-
+
+x,y,z,vx,vy,vz,fx,fy,fz = atom attribute (position, velocity, force component)
+c_ID = scalar or vector calculated by a compute with ID
+c_ID[I] = Ith component of vector or Ith column of array calculated by a compute with ID, I can include wildcard (see below)
+f_ID = scalar or vector calculated by a fix with ID
+f_ID[I] = Ith component of vector or Ith column of array calculated by a fix with ID, I can include wildcard (see below)
+v_name = value(s) calculated by an equal-style or vector-style or atom-style variable with name
+v_name[I] = value calculated by a vector-style variable with name
+
- zero or more keyword/arg pairs may be appended
- keyword = mode or file or ave or start or beyond or overwrite or title1 or title2 or title3
@@ -185,13 +185,13 @@
Examples
-
fix 1 all ave/histo 100 5 1000 0.5 1.5 50 c_myTemp file temp.histo ave running
-fix 1 all ave/histo 100 5 1000 -5 5 100 c_thermo_press[2] c_thermo_press[3] title1 "My output values"
-fix 1 all ave/histo 100 5 1000 -5 5 100 c_thermo_press[*]
-fix 1 all ave/histo 1 100 1000 -2.0 2.0 18 vx vy vz mode vector ave running beyond extra
-fix 1 all ave/histo/weight 1 1 1 10 100 2000 c_XRD[1] c_XRD[2]
-
-
+
+fix 1 all ave/histo 100 5 1000 0.5 1.5 50 c_myTemp file temp.histo ave running
+fix 1 all ave/histo 100 5 1000 -5 5 100 c_thermo_press[2] c_thermo_press[3] title1 "My output values"
+fix 1 all ave/histo 100 5 1000 -5 5 100 c_thermo_press[*]
+fix 1 all ave/histo 1 100 1000 -2.0 2.0 18 vx vy vz mode vector ave running beyond extra
+fix 1 all ave/histo/weight 1 1 1 10 100 2000 c_XRD[1] c_XRD[2]
+
Description
@@ -232,7 +232,7 @@ with a bracketed term appended, indicating the Ith column of the array
is used.
Note that for values from a compute or fix, the bracketed index I can
be specified using a wildcard asterisk with the index to effectively
-specify multiple values. This takes the form “*” or “n” or “n” or
+specify multiple values. This takes the form “*” or “*n” or “n*” or
“m*n”. If N = the size of the vector (for mode = scalar) or the
number of columns in the array (for mode = vector), then an asterisk
with no numeric values means all indices from 1 to N. A leading
@@ -243,11 +243,11 @@ means all indices from m to n (inclusive).
vector or columns of the array had been listed one by one. E.g. these
2 fix ave/histo commands are equivalent, since the
compute com/chunk command creates a global array with
3 columns:
-
compute myCOM all com/chunk
-fix 1 all ave/histo 100 1 100 c_myCOM[*] file tmp1.com mode vector
-fix 2 all ave/histo 100 1 100 c_myCOM[1] c_myCOM[2] c_myCOM[3] file tmp2.com mode vector
-
-
+
+compute myCOM all com/chunk
+fix 1 all ave/histo 100 1 100 c_myCOM[*] file tmp1.com mode vector
+fix 2 all ave/histo 100 1 100 c_myCOM[1] c_myCOM[2] c_myCOM[3] file tmp2.com mode vector
+
If the fix ave/histo/weight command is used, exactly two values must
be specified. If the values are vectors, they must be the same
length. The first value (a scalar or vector) is what is histogrammed
@@ -278,7 +278,7 @@ simply generated on timesteps 100,200,etc.
self-explanatory. Note that other atom attributes can be used as
inputs to this fix by using the
compute property/atom command and then specifying
an input value from that compute.
-
If a value begins with “c_”, a compute ID must follow which has been
+
If a value begins with “c_”, a compute ID must follow which has been
previously defined in the input script. If mode = scalar, then if
no bracketed term is appended, the global scalar calculated by the
compute is used. If a bracketed term is appended, the Ith element of
@@ -295,7 +295,7 @@ can thus be accessed by fix ave/histo. Or it can be a compute defined
not in your input script, but by thermodynamic output or other fixes such as fix nvt or fix temp/rescale. See
the doc pages for these commands which give the IDs of these computes.
Users can also write code for their own compute styles and add them to LAMMPS.
-
If a value begins with “f_”, a fix ID must follow which has been
+
If a value begins with “f_”, a fix ID must follow which has been
previously defined in the input script. If mode = scalar, then if
no bracketed term is appended, the global scalar calculated by the fix
is used. If a bracketed term is appended, the Ith element of the
@@ -309,7 +309,7 @@ values.
Note that some fixes only produce their values on certain timesteps,
which must be compatible with Nevery, else an error will result.
Users can also write code for their own fix styles and add them to LAMMPS.
-
If a value begins with “v_”, a variable name must follow which has
+
If a value begins with “v_”, a variable name must follow which has
been previously defined in the input script. If mode = scalar, then
only equal-style or vector-style variables can be used, which both
produce global values. In this mode, a vector-style variable requires
@@ -399,10 +399,8 @@ values for each of these, so they do not need to be specified.
describes the six values that are printed at the first of each section
of output. The third describes the 4 values printed for each bin in
the histogram.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files. None of the fix_modify options
are relevant to this fix.
This fix produces a global vector and global array which can be
diff --git a/doc/html/fix_ave_time.html b/doc/html/fix_ave_time.html
index 6c6744c5e6..2d41fdc0dc 100644
--- a/doc/html/fix_ave_time.html
+++ b/doc/html/fix_ave_time.html
@@ -140,14 +140,14 @@
one or more input values can be listed
value = c_ID, c_ID[N], f_ID, f_ID[N], v_name
-
c_ID = global scalar or vector calculated by a compute with ID
-c_ID[I] = Ith component of global vector or Ith column of global array calculated by a compute with ID, I can include wildcard (see below)
-f_ID = global scalar or vector calculated by a fix with ID
-f_ID[I] = Ith component of global vector or Ith column of global array calculated by a fix with ID, I can include wildcard (see below)
-v_name = value(s) calculated by an equal-style or vector-style variable with name
-v_name[I] = value calculated by a vector-style variable with name
-
-
+
+c_ID = global scalar or vector calculated by a compute with ID
+c_ID[I] = Ith component of global vector or Ith column of global array calculated by a compute with ID, I can include wildcard (see below)
+f_ID = global scalar or vector calculated by a fix with ID
+f_ID[I] = Ith component of global vector or Ith column of global array calculated by a fix with ID, I can include wildcard (see below)
+v_name = value(s) calculated by an equal-style or vector-style variable with name
+v_name[I] = value calculated by a vector-style variable with name
+
- zero or more keyword/arg pairs may be appended
- keyword = mode or file or ave or start or off or overwrite or title1 or title2 or title3
@@ -179,13 +179,13 @@
Examples
-
fix 1 all ave/time 100 5 1000 c_myTemp c_thermo_temp file temp.profile
-fix 1 all ave/time 100 5 1000 c_thermo_press[2] ave window 20 &
- title1 "My output values"
-fix 1 all ave/time 100 5 1000 c_thermo_press[*]
-fix 1 all ave/time 1 100 1000 f_indent f_indent[1] file temp.indent off 1
-
-
+
+fix 1 all ave/time 100 5 1000 c_myTemp c_thermo_temp file temp.profile
+fix 1 all ave/time 100 5 1000 c_thermo_press[2] ave window 20 &
+ title1 "My output values"
+fix 1 all ave/time 100 5 1000 c_thermo_press[*]
+fix 1 all ave/time 1 100 1000 f_indent f_indent[1] file temp.indent off 1
+
Description
@@ -228,7 +228,7 @@ is used. All vectors must be the same length, which is the length of
the vector or number of rows in the array.
Note that for values from a compute or fix, the bracketed index I can
be specified using a wildcard asterisk with the index to effectively
-specify multiple values. This takes the form “*” or “n” or “n” or
+specify multiple values. This takes the form “*” or “*n” or “n*” or
“m*n”. If N = the size of the vector (for mode = scalar) or the
number of columns in the array (for mode = vector), then an asterisk
with no numeric values means all indices from 1 to N. A leading
@@ -239,11 +239,11 @@ means all indices from m to n (inclusive).
vector or columns of the array had been listed one by one. E.g. these
2 fix ave/time commands are equivalent, since the
compute rdf command creates, in this case, a global array
with 3 columns, each of length 50:
-
compute myRDF all rdf 50 1 2
-fix 1 all ave/time 100 1 100 c_myRDF[*] file tmp1.rdf mode vector
-fix 2 all ave/time 100 1 100 c_myRDF[1] c_myRDF[2] c_myRDF[3] file tmp2.rdf mode vector
-
-
+
+compute myRDF all rdf 50 1 2
+fix 1 all ave/time 100 1 100 c_myRDF[*] file tmp1.rdf mode vector
+fix 2 all ave/time 100 1 100 c_myRDF[1] c_myRDF[2] c_myRDF[3] file tmp2.rdf mode vector
+
The Nevery, Nrepeat, and Nfreq arguments specify on what
timesteps the input values will be used in order to contribute to the
@@ -261,7 +261,7 @@ timestep 200, etc. If Nrepeat=1 and Nfreq = 100, then no time
averaging is done; values are simply generated on timesteps
100,200,etc.
-
If a value begins with “c_”, a compute ID must follow which has been
+
If a value begins with “c_”, a compute ID must follow which has been
previously defined in the input script. If mode = scalar, then if
no bracketed term is appended, the global scalar calculated by the
compute is used. If a bracketed term is appended, the Ith element of
@@ -277,7 +277,7 @@ can thus be accessed by fix ave/time. Or it can be a compute defined
not in your input script, but by thermodynamic output or other fixes such as fix nvt or fix temp/rescale. See
the doc pages for these commands which give the IDs of these computes.
Users can also write code for their own compute styles and add them to LAMMPS.
-
If a value begins with “f_”, a fix ID must follow which has been
+
If a value begins with “f_”, a fix ID must follow which has been
previously defined in the input script. If mode = scalar, then if
no bracketed term is appended, the global scalar calculated by the fix
is used. If a bracketed term is appended, the Ith element of the
@@ -290,7 +290,7 @@ specify multiple values.
Note that some fixes only produce their values on certain timesteps,
which must be compatible with Nevery, else an error will result.
Users can also write code for their own fix styles and add them to LAMMPS.
-
If a value begins with “v_”, a variable name must follow which has
+
If a value begins with “v_”, a variable name must follow which has
been previously defined in the input script. If mode = scalar, then
only equal-style or vector-style variables can be used, which both
produce global values. In this mode, a vector-style variable requires
@@ -383,10 +383,8 @@ so the title3 setting is ignored when mode = scalar.
describes the two values that are printed at the first of each section
of output. In the third line the values are replaced with the
appropriate fields from the fix ave/time command.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files. None of the fix_modify options
are relevant to this fix.
This fix produces a global scalar or global vector or global array
diff --git a/doc/html/fix_aveforce.html b/doc/html/fix_aveforce.html
index b5d312fdc6..3a4daf418a 100644
--- a/doc/html/fix_aveforce.html
+++ b/doc/html/fix_aveforce.html
@@ -150,11 +150,11 @@
Examples
-
fix pressdown topwall aveforce 0.0 -1.0 0.0
-fix 2 bottomwall aveforce NULL -1.0 0.0 region top
-fix 2 bottomwall aveforce NULL -1.0 v_oscillate region top
-
-
+
+fix pressdown topwall aveforce 0.0 -1.0 0.0
+fix 2 bottomwall aveforce NULL -1.0 0.0 region top
+fix 2 bottomwall aveforce NULL -1.0 v_oscillate region top
+
Description
@@ -198,10 +198,8 @@ by including their suffix, or you can use the
suffix command in your input script.
See Section_accelerate of the manual for
more instructions on how to use the accelerated styles effectively.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files.
The fix_modify respa option is supported by this
fix. This allows to set at which level of the r-RESPA
diff --git a/doc/html/fix_balance.html b/doc/html/fix_balance.html
index 0415a0054b..56beb5da2b 100644
--- a/doc/html/fix_balance.html
+++ b/doc/html/fix_balance.html
@@ -432,10 +432,8 @@ will be duplicate nodes in the list.
rectangle for each processor (1 to 4).
For a 3d problem, the syntax is similar with 8 vertices listed for
each processor, instead of 4, and “SQUARES” replaced by “CUBES”.
-
-
-
Restart, fix_modify, output, run start/stop, minimize info
+
Restart, fix_modify, output, run start/stop, minimize info:
No information about this fix is written to binary restart files. None of the fix_modify options
are relevant to this fix.
This fix computes a global scalar which is the imbalance factor
diff --git a/doc/html/fix_bond_break.html b/doc/html/fix_bond_break.html
index 9be191ab77..ef0c90e2a9 100644
--- a/doc/html/fix_bond_break.html
+++ b/doc/html/fix_bond_break.html
@@ -224,10 +224,8 @@ dramatically released when the bond is broken. More generally, you
may need to thermostat your system to compensate for energy changes
resulting from broken bonds (and angles, dihedrals, impropers).
-