diff --git a/doc/fix_nve_limit.html b/doc/fix_nve_limit.html index ed8463f199..271340b1d9 100644 --- a/doc/fix_nve_limit.html +++ b/doc/fix_nve_limit.html @@ -54,11 +54,22 @@ very large for overlapped configurations.
No information about this fix is written to binary restart files. None of the fix_modify options -are relevant to this fix. No global scalar or vector or per-atom -quantities are stored by this fix for access by various output -commands. No parameter of this fix can be -used with the start/stop keywords of the run command. -This fix is not invoked during energy minimization. +are relevant to this fix. +
+This fix computes a scalar quantity which is the count of how many +updates of atom's velocity/position were limited by the maximum +distance criterion. This should be roughly the number of atoms so +affected, except that updates occur at both the beginning and end of a +timestep in a velocity Verlet timestepping algorithm. This is a +cummulative quantity for the current run, but is re-initialized to +zero each time a run is performed. This value can be accessed by +various output commands. The scalar value +calculated by this fix is "extensive", meaning it scales with the +number of atoms in the simulation. +
+No parameter of this fix can be used with the start/stop keywords of +the run command. This fix is not invoked during energy +minimization.
Restrictions: none
diff --git a/doc/fix_nve_limit.txt b/doc/fix_nve_limit.txt index 8bfd86b658..da44909c0b 100644 --- a/doc/fix_nve_limit.txt +++ b/doc/fix_nve_limit.txt @@ -51,11 +51,22 @@ very large for overlapped configurations. No information about this fix is written to "binary restart files"_restart.html. None of the "fix_modify"_fix_modify.html options -are relevant to this fix. No global scalar or vector or per-atom -quantities are stored by this fix for access by various "output -commands"_Section_howto.html#4_15. No parameter of this fix can be -used with the {start/stop} keywords of the "run"_run.html command. -This fix is not invoked during "energy minimization"_minimize.html. +are relevant to this fix. + +This fix computes a scalar quantity which is the count of how many +updates of atom's velocity/position were limited by the maximum +distance criterion. This should be roughly the number of atoms so +affected, except that updates occur at both the beginning and end of a +timestep in a velocity Verlet timestepping algorithm. This is a +cummulative quantity for the current run, but is re-initialized to +zero each time a run is performed. This value can be accessed by +various "output commands"_Section_howto.html#4_15. The scalar value +calculated by this fix is "extensive", meaning it scales with the +number of atoms in the simulation. + +No parameter of this fix can be used with the {start/stop} keywords of +the "run"_run.html command. This fix is not invoked during "energy +minimization"_minimize.html. [Restrictions:] none