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

doc/Section_start.html

@@ -219,8 +219,8 @@ gmake foo
 <P>(1) Building LAMMPS for multiple platforms.
 </P>
 <P>You can make LAMMPS for multiple platforms from the same src
-directory.  Each target creates its own object sub-dir called Obj_name
+directory.  Each target creates its own object sub-directory called
-where it stores the system-specific *.o files.
+Obj_name where it stores the system-specific *.o files.
 </P>
 <P>(2) Cleaning up.
 </P>

doc/Section_start.txt

@@ -214,8 +214,8 @@ You should get the executable lmp_foo when the build is complete.
 (1) Building LAMMPS for multiple platforms.
 
 You can make LAMMPS for multiple platforms from the same src
-directory.  Each target creates its own object sub-dir called Obj_name
+directory.  Each target creates its own object sub-directory called
-where it stores the system-specific *.o files.
+Obj_name where it stores the system-specific *.o files.
 
 (2) Cleaning up.
 

doc/dimension.html

@@ -32,6 +32,11 @@ Restart files also store this setting.
 <P>See the discussion in <A HREF = "Section_howto.html">this section</A> for additional
 instructions on how to run 2d simulations.
 </P>
+<P>IMPORTANT NOTE: Some models in LAMMPS treat particles as extended
+spheres or ellipsoids, as opposed to point particles.  In 2d, the
+particles will still be spheres or ellipsoids, not circular disks or
+ellipses, meaning their moment of inertia will be the same as in 3d.
+</P>
 <P><B>Restrictions:</B>
 </P>
 <P>This command must be used before the simulation box is defined by a

doc/dimension.txt

@@ -29,6 +29,11 @@ Restart files also store this setting.
 See the discussion in "this section"_Section_howto.html for additional
 instructions on how to run 2d simulations.
 
+IMPORTANT NOTE: Some models in LAMMPS treat particles as extended
+spheres or ellipsoids, as opposed to point particles.  In 2d, the
+particles will still be spheres or ellipsoids, not circular disks or
+ellipses, meaning their moment of inertia will be the same as in 3d.
+
 [Restrictions:]
 
 This command must be used before the simulation box is defined by a

doc/fix_nve_asphere.html

@@ -29,6 +29,9 @@ angular velocity for aspherical particles in the group each timestep.
 V is volume; E is energy.  This creates a system trajectory consistent
 with the microcanonical ensemble.
 </P>
+<P>This fix differs from the <A HREF = "fix_nve.html">fix nve</A> command, which
+assumes point particles and only updates their position and velocity.
+</P>
 <P><B>Restart, fix_modify, output, run start/stop, minimize info:</B>
 </P>
 <P>No information about this fix is written to <A HREF = "restart.html">binary restart

doc/fix_nve_asphere.txt

@@ -26,6 +26,9 @@ angular velocity for aspherical particles in the group each timestep.
 V is volume; E is energy.  This creates a system trajectory consistent
 with the microcanonical ensemble.
 
+This fix differs from the "fix nve"_fix_nve.html command, which
+assumes point particles and only updates their position and velocity.
+
 [Restart, fix_modify, output, run start/stop, minimize info:]
 
 No information about this fix is written to "binary restart

doc/jump.html

@@ -52,8 +52,8 @@ jump in.lj loop
 <P>If the jump <I>file</I> argument is a variable, the jump command can be
 used to cause different processor partitions to run different input
 scripts.  In this example, LAMMPS is run on 40 processors, with 4
-partitions of 10 procs each.  An in.file containing the example variable
+partitions of 10 procs each.  An in.file containing the example
-and jump command will cause each partition to run a different
+variable and jump command will cause each partition to run a different
 simulation.
 </P>
 <PRE>mpirun -np 40 lmp_ibm -partition 4x10 -in in.file 

doc/jump.txt

@@ -49,8 +49,8 @@ jump in.lj loop :pre
 If the jump {file} argument is a variable, the jump command can be
 used to cause different processor partitions to run different input
 scripts.  In this example, LAMMPS is run on 40 processors, with 4
-partitions of 10 procs each.  An in.file containing the example variable
+partitions of 10 procs each.  An in.file containing the example
-and jump command will cause each partition to run a different
+variable and jump command will cause each partition to run a different
 simulation.
 
 mpirun -np 40 lmp_ibm -partition 4x10 -in in.file :pre