Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
lammps
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
multiscale
lammps
Commits
dc622dbb
Commit
dc622dbb
authored
17 years ago
by
sjplimp
Browse files
Options
Downloads
Patches
Plain Diff
git-svn-id:
svn://svn.icms.temple.edu/lammps-ro/trunk@1276
f3b2605a-c512-4ea7-a41b-209d697bcdaa
parent
c10f59aa
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/fix_nve_limit.html
+16
-5
16 additions, 5 deletions
doc/fix_nve_limit.html
doc/fix_nve_limit.txt
+16
-5
16 additions, 5 deletions
doc/fix_nve_limit.txt
with
32 additions
and
10 deletions
doc/fix_nve_limit.html
+
16
−
5
View file @
dc622dbb
...
...
@@ -54,11 +54,22 @@ very large for overlapped configurations.
</P>
<P>
No information about this fix is written to
<A
HREF =
"restart.html"
>
binary restart
files
</A>
. None of the
<A
HREF =
"fix_modify.html"
>
fix_modify
</A>
options
are relevant to this fix. No global scalar or vector or per-atom
quantities are stored by this fix for access by various
<A
HREF =
"Section_howto.html#4_15"
>
output
commands
</A>
. No parameter of this fix can be
used with the
<I>
start/stop
</I>
keywords of the
<A
HREF =
"run.html"
>
run
</A>
command.
This fix is not invoked during
<A
HREF =
"minimize.html"
>
energy minimization
</A>
.
are relevant to this fix.
</P>
<P>
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
<A
HREF =
"Section_howto.html#4_15"
>
output commands
</A>
. The scalar value
calculated by this fix is "extensive", meaning it scales with the
number of atoms in the simulation.
</P>
<P>
No parameter of this fix can be used with the
<I>
start/stop
</I>
keywords of
the
<A
HREF =
"run.html"
>
run
</A>
command. This fix is not invoked during
<A
HREF =
"minimize.html"
>
energy
minimization
</A>
.
</P>
<P><B>
Restrictions:
</B>
none
</P>
...
...
This diff is collapsed.
Click to expand it.
doc/fix_nve_limit.txt
+
16
−
5
View file @
dc622dbb
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment