2006-09-22 00:22:34 +08:00
|
|
|
"LAMMPS WWW Site"_lws - "LAMMPS Documentation"_ld - "LAMMPS Commands"_lc :c
|
|
|
|
|
|
|
|
:link(lws,http://lammps.sandia.gov)
|
|
|
|
:link(ld,Manual.html)
|
|
|
|
:link(lc,Section_commands.html#comm)
|
|
|
|
|
|
|
|
:line
|
|
|
|
|
|
|
|
thermo_style command :h3
|
|
|
|
|
|
|
|
[Syntax:]
|
|
|
|
|
|
|
|
thermo_style style args :pre
|
|
|
|
|
2008-03-18 07:43:56 +08:00
|
|
|
style = {one} or {multi} or {custom} :ulb,l
|
2006-09-22 00:22:34 +08:00
|
|
|
args = list of arguments for a particular style :l
|
|
|
|
{one} args = none
|
|
|
|
{multi} args = none
|
|
|
|
{custom} args = list of attributes
|
2013-10-02 21:46:27 +08:00
|
|
|
possible attributes = step, elapsed, elaplong, dt, time,
|
2013-11-09 05:03:18 +08:00
|
|
|
cpu, tpcpu, spcpu, cpuremain, part,
|
2010-03-04 02:40:02 +08:00
|
|
|
atoms, temp, press, pe, ke, etotal, enthalpy,
|
2006-12-20 00:33:33 +08:00
|
|
|
evdwl, ecoul, epair, ebond, eangle, edihed, eimp,
|
|
|
|
emol, elong, etail,
|
2007-02-10 05:37:30 +08:00
|
|
|
vol, lx, ly, lz, xlo, xhi, ylo, yhi, zlo, zhi,
|
2010-02-09 06:34:21 +08:00
|
|
|
xy, xz, yz, xlat, ylat, zlat,
|
2009-03-17 23:41:12 +08:00
|
|
|
pxx, pyy, pzz, pxy, pxz, pyz,
|
2010-05-22 00:00:09 +08:00
|
|
|
fmax, fnorm,
|
2011-06-17 00:03:29 +08:00
|
|
|
cella, cellb, cellc, cellalpha, cellbeta, cellgamma,
|
2009-12-10 05:20:59 +08:00
|
|
|
c_ID, c_ID\[I\], c_ID\[I\]\[J\],
|
|
|
|
f_ID, f_ID\[I\], f_ID\[I\]\[J\],
|
|
|
|
v_name
|
2006-09-22 00:22:34 +08:00
|
|
|
step = timestep
|
2010-03-04 02:40:02 +08:00
|
|
|
elapsed = timesteps since start of this run
|
|
|
|
elaplong = timesteps since start of initial run in a series of runs
|
|
|
|
dt = timestep size
|
2013-05-24 01:40:38 +08:00
|
|
|
time = simulation time
|
2010-05-21 01:15:00 +08:00
|
|
|
cpu = elapsed CPU time in seconds
|
|
|
|
tpcpu = time per CPU second
|
|
|
|
spcpu = timesteps per CPU second
|
2013-10-02 21:46:27 +08:00
|
|
|
cpuremain = estimated CPU time remaining in run
|
2013-11-09 05:03:18 +08:00
|
|
|
part = which partition (0 to Npartition-1) this is
|
2010-03-04 02:40:02 +08:00
|
|
|
atoms = # of atoms
|
2006-09-22 00:22:34 +08:00
|
|
|
temp = temperature
|
|
|
|
press = pressure
|
|
|
|
pe = total potential energy
|
|
|
|
ke = kinetic energy
|
2006-11-11 05:27:54 +08:00
|
|
|
etotal = total energy (pe + ke)
|
2009-02-25 05:16:35 +08:00
|
|
|
enthalpy = enthalpy (etotal + press*vol)
|
2006-09-22 00:22:34 +08:00
|
|
|
evdwl = VanderWaal pairwise energy
|
|
|
|
ecoul = Coulombic pairwise energy
|
2007-03-08 09:01:08 +08:00
|
|
|
epair = pairwise energy (evdwl + ecoul + elong + etail)
|
2006-09-22 00:22:34 +08:00
|
|
|
ebond = bond energy
|
|
|
|
eangle = angle energy
|
|
|
|
edihed = dihedral energy
|
|
|
|
eimp = improper energy
|
|
|
|
emol = molecular energy (ebond + eangle + edihed + eimp)
|
|
|
|
elong = long-range kspace energy
|
2006-12-20 00:33:33 +08:00
|
|
|
etail = VanderWaal energy long-range tail correction
|
2006-09-22 00:22:34 +08:00
|
|
|
vol = volume
|
2013-08-20 00:49:20 +08:00
|
|
|
density = mass density of system
|
2006-09-22 00:22:34 +08:00
|
|
|
lx,ly,lz = box lengths in x,y,z
|
2007-02-10 05:37:30 +08:00
|
|
|
xlo,xhi,ylo,yhi,zlo,zhi = box boundaries
|
2009-03-17 23:41:12 +08:00
|
|
|
xy,xz,yz = box tilt for triclinic (non-orthogonal) simulation boxes
|
2010-02-09 06:34:21 +08:00
|
|
|
xlat,ylat,zlat = lattice spacings as calculated by "lattice"_lattice.html command
|
2006-09-22 00:22:34 +08:00
|
|
|
pxx,pyy,pzz,pxy,pxz,pyz = 6 components of pressure tensor
|
2010-05-22 00:00:09 +08:00
|
|
|
fmax = max component of force on any atom in any dimension
|
|
|
|
fnorm = length of force vector for all atoms
|
2011-06-17 00:03:29 +08:00
|
|
|
cella,cellb,cellc = periodic cell lattice constants a,b,c
|
|
|
|
cellalpha, cellbeta, cellgamma = periodic cell angles alpha,beta,gamma
|
2008-01-03 03:25:15 +08:00
|
|
|
c_ID = global scalar value calculated by a compute with ID
|
2009-12-10 05:20:59 +08:00
|
|
|
c_ID\[I\] = Ith component of global vector calculated by a compute with ID
|
|
|
|
c_ID\[I\]\[J\] = I,J component of global array calculated by a compute with ID
|
2008-01-03 03:25:15 +08:00
|
|
|
f_ID = global scalar value calculated by a fix with ID
|
2009-12-10 05:20:59 +08:00
|
|
|
f_ID\[I\] = Ith component of global vector calculated by a fix with ID
|
|
|
|
f_ID\[I\]\[J\] = I,J component of global array calculated by a fix with ID
|
|
|
|
v_name = scalar value calculated by an equal-style variable with name :pre
|
2006-09-22 00:22:34 +08:00
|
|
|
:ule
|
|
|
|
|
|
|
|
[Examples:]
|
|
|
|
|
|
|
|
thermo_style multi
|
2006-11-11 05:27:54 +08:00
|
|
|
thermo_style custom step temp pe etotal press vol
|
2007-02-10 05:37:30 +08:00
|
|
|
thermo_style custom step temp etotal c_myTemp v_abc :pre
|
2006-09-22 00:22:34 +08:00
|
|
|
|
|
|
|
[Description:]
|
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
Set the style and content for printing thermodynamic data to the
|
|
|
|
screen and log file.
|
2006-09-22 00:22:34 +08:00
|
|
|
|
|
|
|
Style {one} prints a one-line summary of thermodynamic info that is
|
2006-11-11 05:27:54 +08:00
|
|
|
the equivalent of "thermo_style custom step temp epair emol etotal
|
2006-09-22 00:22:34 +08:00
|
|
|
press". The line contains only numeric values.
|
|
|
|
|
|
|
|
Style {multi} prints a multiple-line listing of thermodynamic info
|
2006-11-11 05:27:54 +08:00
|
|
|
that is the equivalent of "thermo_style custom etotal ke temp pe ebond
|
2006-09-22 00:22:34 +08:00
|
|
|
eangle edihed eimp evdwl ecoul elong press". The listing contains
|
|
|
|
numeric values and a string ID for each quantity.
|
|
|
|
|
|
|
|
Style {custom} is the most general setting and allows you to specify
|
2007-02-10 05:37:30 +08:00
|
|
|
which of the keywords listed above you want printed on each
|
|
|
|
thermodynamic timestep. Note that the keywords c_ID, f_ID, v_name are
|
|
|
|
references to "computes"_compute.html, "fixes"_fix.html, and
|
2008-01-03 03:25:15 +08:00
|
|
|
equal-style "variables"_variable.html" that have been defined
|
|
|
|
elsewhere in the input script or can even be new styles which users
|
|
|
|
have added to LAMMPS (see the "Section_modify"_Section_modify.html
|
|
|
|
section of the documentation). Thus the {custom} style provides a
|
|
|
|
flexible means of outputting essentially any desired quantity as a
|
|
|
|
simulation proceeds.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
|
|
|
All styles except {custom} have {vol} appended to their list of
|
|
|
|
outputs if the simulation box volume changes during the simulation.
|
2006-09-22 00:22:34 +08:00
|
|
|
|
2007-10-19 06:02:20 +08:00
|
|
|
The values printed by the various keywords are instantaneous values,
|
|
|
|
calculated on the current timestep. Time-averaged quantities, which
|
|
|
|
include values from previous timesteps, can be output by using the
|
|
|
|
f_ID keyword and accessing a fix that does time-averaging such as the
|
|
|
|
"fix ave/time"_fix_ave_time.html command.
|
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
Options invoked by the "thermo_modify"_thermo_modify.html command can
|
|
|
|
be used to set the one- or multi-line format of the print-out, the
|
2009-01-06 07:48:45 +08:00
|
|
|
normalization of thermodynamic output (total values versus per-atom
|
2009-04-02 06:25:09 +08:00
|
|
|
values for extensive quantities (ones which scale with the number of
|
|
|
|
atoms in the system), and the numeric precision of each printed value.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
2009-01-06 07:48:45 +08:00
|
|
|
IMPORTANT NOTE: When you use a "thermo_style" command, all
|
2007-06-26 08:03:39 +08:00
|
|
|
thermodynamic settings are restored to their default values, including
|
2009-01-06 07:48:45 +08:00
|
|
|
those previously set by a "thermo_modify"_thermo_modify.html command.
|
2007-06-26 08:03:39 +08:00
|
|
|
Thus if your input script specifies a thermo_style command, you should
|
|
|
|
use the thermo_modify command after it.
|
2007-06-20 20:56:17 +08:00
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
:line
|
|
|
|
|
|
|
|
Several of the thermodynamic quantities require a temperature to be
|
2010-05-22 00:00:09 +08:00
|
|
|
computed: "temp", "press", "ke", "etotal", "enthalpy", "pxx", etc. By
|
2009-04-02 06:25:09 +08:00
|
|
|
default this is done by using a {temperature} compute which is created
|
|
|
|
when LAMMPS starts up, as if this command had been issued:
|
2007-02-10 05:37:30 +08:00
|
|
|
|
|
|
|
compute thermo_temp all temp :pre
|
|
|
|
|
|
|
|
See the "compute temp"_compute_temp.html command for details. Note
|
2007-06-20 20:56:17 +08:00
|
|
|
that the ID of this compute is {thermo_temp} and the group is {all}.
|
|
|
|
You can change the attributes of this temperature (e.g. its
|
2007-02-10 05:37:30 +08:00
|
|
|
degrees-of-freedom) via the "compute_modify"_compute_modify.html
|
|
|
|
command. Alternatively, you can directly assign a new compute (that
|
2007-06-20 20:56:17 +08:00
|
|
|
calculates temperature) which you have defined, to be used for
|
|
|
|
calculating any thermodynamic quantity that requires a temperature.
|
|
|
|
This is done via the "thermo_modify"_thermo_modify.html command.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
|
|
|
Several of the thermodynamic quantities require a pressure to be
|
2007-11-02 00:46:50 +08:00
|
|
|
computed: "press", "enthalpy", "pxx", etc. By default this is done by
|
2009-04-02 06:25:09 +08:00
|
|
|
using a {pressure} compute which is created when LAMMPS starts up, as
|
2008-01-18 07:46:30 +08:00
|
|
|
if this command had been issued:
|
2007-02-10 05:37:30 +08:00
|
|
|
|
2008-01-18 07:46:30 +08:00
|
|
|
compute thermo_press all pressure thermo_temp :pre
|
2007-02-10 05:37:30 +08:00
|
|
|
|
|
|
|
See the "compute pressure"_compute_pressure.html command for details.
|
2008-01-18 07:46:30 +08:00
|
|
|
Note that the ID of this compute is {thermo_press} and the group is
|
2007-02-10 05:37:30 +08:00
|
|
|
{all}. You can change the attributes of this pressure via the
|
|
|
|
"compute_modify"_compute_modify.html command. Alternatively, you can
|
|
|
|
directly assign a new compute (that calculates pressure) which you
|
2007-06-20 20:56:17 +08:00
|
|
|
have defined, to be used for calculating any thermodynamic quantity
|
|
|
|
that requires a pressure. This is done via the
|
|
|
|
"thermo_modify"_thermo_modify.html command.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
2007-11-02 00:46:50 +08:00
|
|
|
Several of the thermodynamic quantities require a potential energy to
|
2009-04-02 06:25:09 +08:00
|
|
|
be computed: "pe", "etotal", "ebond", etc. This is done by using a
|
|
|
|
{pe} compute which is created when LAMMPS starts up, as if this
|
2007-11-02 00:46:50 +08:00
|
|
|
command had been issued:
|
|
|
|
|
|
|
|
compute thermo_pe all pe :pre
|
|
|
|
|
|
|
|
See the "compute pe"_compute_pe.html command for details. Note that
|
|
|
|
the ID of this compute is {thermo_pe} and the group is {all}. You can
|
|
|
|
change the attributes of this potential energy via the
|
|
|
|
"compute_modify"_compute_modify.html command.
|
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
:line
|
2006-09-22 00:22:34 +08:00
|
|
|
|
2008-03-18 07:43:56 +08:00
|
|
|
The kinetic energy of the system {ke} is inferred from the temperature
|
|
|
|
of the system with 1/2 Kb T of energy for each degree of freedom.
|
2008-03-19 05:49:24 +08:00
|
|
|
Thus, using different "compute commands"_compute.html for calculating
|
2008-03-18 07:43:56 +08:00
|
|
|
temperature, via the "thermo_modify temp"_thermo_modify.html command,
|
2008-03-20 00:03:13 +08:00
|
|
|
may yield different kinetic energies, since different computes that
|
|
|
|
calculate temperature can subtract out different non-thermal
|
|
|
|
components of velocity and/or include different degrees of freedom
|
|
|
|
(translational, rotational, etc).
|
2008-03-18 07:43:56 +08:00
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
The potential energy of the system {pe} will include contributions
|
2007-11-02 00:46:50 +08:00
|
|
|
from fixes if the "fix_modify thermo"_fix_modify.html option is set
|
|
|
|
for a fix that calculates such a contribution. For example, the "fix
|
2010-05-07 23:11:21 +08:00
|
|
|
wall/lj93"_fix_wall.html fix calculates the energy of atoms
|
2007-11-02 00:46:50 +08:00
|
|
|
interacting with the wall. See the doc pages for "individual fixes"
|
|
|
|
to see which ones contribute.
|
2006-09-22 00:22:34 +08:00
|
|
|
|
|
|
|
A long-range tail correction {etail} for the VanderWaal pairwise
|
|
|
|
energy will be non-zero only if the "pair_modify
|
|
|
|
tail"_pair_modify.html option is turned on. The {etail} contribution
|
2006-11-11 05:27:54 +08:00
|
|
|
is included in {evdwl}, {pe}, and {etotal}, and the corresponding tail
|
2006-09-22 00:22:34 +08:00
|
|
|
correction to the pressure is included in {press} and {pxx}, {pyy},
|
|
|
|
etc.
|
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
:line
|
2006-09-22 00:22:34 +08:00
|
|
|
|
2010-03-04 02:40:02 +08:00
|
|
|
The {step}, {elapsed}, and {elaplong} keywords refer to timestep
|
|
|
|
count. {Step} is the current timestep, or iteration count when a
|
|
|
|
"minimization"_minimize.html is being performed. {Elapsed} is the
|
|
|
|
number of timesteps elapsed since the beginning of this run.
|
|
|
|
{Elaplong} is the number of timesteps elapsed since the beginning of
|
|
|
|
an initial run in a series of runs. See the {start} and {stop}
|
|
|
|
keywords for the "run"_run.html for info on how to invoke a series of
|
|
|
|
runs that keep track of an initial starting time. If these keywords
|
|
|
|
are not used, then {elapsed} and {elaplong} are the same value.
|
|
|
|
|
2013-05-24 01:40:38 +08:00
|
|
|
The {dt} keyword is the current timestep size in time
|
|
|
|
"units"_units.html. The {time} keyword is the current elapsed
|
|
|
|
simulation time, also in time "units"_units.html, which is simply
|
|
|
|
(step*dt) if the timestep size has not changed and the timestep has
|
|
|
|
not been reset. If the timestep has changed (e.g. via "fix
|
|
|
|
dt/reset"_fix_dt_reset.html) or the timestep has been reset (e.g. via
|
|
|
|
the "reset_timestep" command), then the simulation time is effectively
|
|
|
|
a cummulative value up to the current point.
|
|
|
|
|
2010-05-21 01:15:00 +08:00
|
|
|
The {cpu} keyword is elapsed CPU seconds since the beginning of this
|
|
|
|
run. The {tpcpu} and {spcpu} keywords are measures of how fast your
|
|
|
|
simulation is currently running. The {tpcpu} keyword is simulation
|
|
|
|
time per CPU second, where simulation time is in time
|
|
|
|
"units"_units.html. E.g. for metal units, the {tpcpu} value would be
|
|
|
|
picoseconds per CPU second. The {spcpu} keyword is the number of
|
|
|
|
timesteps per CPU second. Both quantities are on-the-fly metrics,
|
|
|
|
measured relative to the last time they were invoked. Thus if you are
|
|
|
|
printing out thermodyamic output every 100 timesteps, the two keywords
|
|
|
|
will continually output the time and timestep rate for the last 100
|
|
|
|
steps. The {tpcpu} keyword does not attempt to track any changes in
|
|
|
|
timestep size, e.g. due to using the "fix dt/reset"_fix_dt_reset.html
|
|
|
|
command.
|
|
|
|
|
2013-10-02 21:46:27 +08:00
|
|
|
The {cpuremain} keyword estimates the CPU time remaining in the
|
|
|
|
current run, based on the time elapsed thus far. It will only be a
|
|
|
|
good estimate if the CPU time/timestep for the rest of the run is
|
|
|
|
similar to the preceding timesteps. On the initial timestep the value
|
|
|
|
will be 0.0 since there is no history to estimate from. For a
|
|
|
|
minimization run performed by the "minimize" command, the estimate is
|
|
|
|
based on the {maxiter} parameter, assuming the minimization will
|
|
|
|
proceed for the maximum number of allowed iterations.
|
|
|
|
|
2013-11-09 05:03:18 +08:00
|
|
|
The {part} keyword is useful for multi-replica or multi-partition
|
|
|
|
simulations to indicate which partition this output and this file
|
|
|
|
corresponds to, or for use in a "variable"_variable.html to append to
|
|
|
|
a filename for output specific to this partition. See the
|
|
|
|
"Command-line options"_Section_commands.html#start_7 section of the
|
|
|
|
manual for details on running in multi-partition mode.
|
|
|
|
|
2010-05-22 00:00:09 +08:00
|
|
|
The {fmax} and {fnorm} keywords are useful for monitoring the progress
|
|
|
|
of an "energy minimization"_minimize.html. The {fmax} keyword
|
|
|
|
calculates the maximum force in any dimension on any atom in the
|
|
|
|
system, or the infinity-norm of the force vector for the system. The
|
|
|
|
{fnorm} keyword calculates the 2-norm or length of the force vector.
|
|
|
|
|
2011-08-26 01:01:01 +08:00
|
|
|
The keywords {cella}, {cellb}, {cellc}, {cellalpha}, {cellbeta},
|
|
|
|
{cellgamma}, correspond to the usual crystallographic quantities that
|
|
|
|
define the periodic unit cell of a crystal. See "this
|
|
|
|
section"_Section_howto.html#howto_12 of the doc pages for a geometric
|
|
|
|
description of triclinic periodic cells, including a precise defintion
|
|
|
|
of these quantities in terms of the internal LAMMPS cell dimensions
|
2013-08-14 08:20:21 +08:00
|
|
|
{lx}, {ly}, {lz}, {yz}, {xz}, {xy}.
|
|
|
|
|
2010-05-22 00:00:09 +08:00
|
|
|
:line
|
|
|
|
|
2009-12-10 05:20:59 +08:00
|
|
|
The {c_ID} and {c_ID\[I\]} and {c_ID\[I\]\[J\]} keywords allow global
|
|
|
|
values calculated by a compute to be output. As discussed on the
|
|
|
|
"compute"_compute.html doc page, computes can calculate global,
|
|
|
|
per-atom, or local values. Only global values can be referenced by
|
|
|
|
this command. However, per-atom compute values can be referenced in a
|
|
|
|
"variable"_variable.html and the variable referenced by thermo_style
|
|
|
|
custom, as discussed below.
|
|
|
|
|
|
|
|
The ID in the keyword should be replaced by the actual ID of a compute
|
|
|
|
that has been defined elsewhere in the input script. See the
|
|
|
|
"compute"_compute.html command for details. If the compute calculates
|
|
|
|
a global scalar, vector, or array, then the keyword formats with 0, 1,
|
|
|
|
or 2 brackets will reference a scalar value from the compute.
|
2007-10-11 07:47:26 +08:00
|
|
|
|
|
|
|
Note that some computes calculate "intensive" global quantities like
|
|
|
|
temperature; others calculate "extensive" global quantities like
|
|
|
|
kinetic energy that are summed over all atoms in the compute group.
|
2009-12-10 05:20:59 +08:00
|
|
|
Intensive quantities are printed directly without normalization by
|
|
|
|
thermo_style custom. Extensive quantities may be normalized by the
|
2008-01-03 03:25:15 +08:00
|
|
|
total number of atoms in the simulation (NOT the number of atoms in
|
2009-12-10 05:20:59 +08:00
|
|
|
the compute group) when output, depending on the "thermo_modify
|
2008-01-03 03:25:15 +08:00
|
|
|
norm"_thermo_modify.html option being used.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
2009-12-10 05:20:59 +08:00
|
|
|
The {f_ID} and {f_ID\[I\]} and {f_ID\[I\]\[J\]} keywords allow global
|
|
|
|
values calculated by a fix to be output. As discussed on the
|
|
|
|
"fix"_fix.html doc page, fixes can calculate global, per-atom, or
|
|
|
|
local values. Only global values can be referenced by this command.
|
|
|
|
However, per-atom fix values can be referenced in a
|
|
|
|
"variable"_variable.html and the variable referenced by thermo_style
|
|
|
|
custom, as discussed below.
|
|
|
|
|
|
|
|
The ID in the keyword should be replaced by the actual ID of a fix
|
|
|
|
that has been defined elsewhere in the input script. See the
|
|
|
|
"fix"_fix.html command for details. If the fix calculates a global
|
|
|
|
scalar, vector, or array, then the keyword formats with 0, 1, or 2
|
|
|
|
brackets will reference a scalar value from the fix.
|
2007-10-11 07:47:26 +08:00
|
|
|
|
|
|
|
Note that some fixes calculate "intensive" global quantities like
|
|
|
|
timestep size; others calculate "extensive" global quantities like
|
|
|
|
energy that are summed over all atoms in the fix group. Intensive
|
2009-12-10 05:20:59 +08:00
|
|
|
quantities are printed directly without normalization by thermo_style
|
|
|
|
custom. Extensive quantities may be normalized by the total number of
|
|
|
|
atoms in the simulation (NOT the number of atoms in the fix group)
|
|
|
|
when output, depending on the "thermo_modify norm"_thermo_modify.html
|
|
|
|
option being used.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
|
|
|
The {v_name} keyword allow the current value of a variable to be
|
2010-08-13 07:10:38 +08:00
|
|
|
output. The name in the keyword should be replaced by the variable
|
|
|
|
name that has been defined elsewhere in the input script. Only
|
|
|
|
equal-style variables can be referenced. See the
|
2008-01-03 03:25:15 +08:00
|
|
|
"variable"_variable.html command for details. Variables of style
|
2009-12-10 05:20:59 +08:00
|
|
|
{equal} can reference per-atom properties or thermodynamic keywords,
|
|
|
|
or they can invoke other computes, fixes, or variables when evaluated,
|
|
|
|
so this is a very general means of creating thermodynamic output.
|
2007-02-10 05:37:30 +08:00
|
|
|
|
2013-06-28 03:43:07 +08:00
|
|
|
Note that equal-style variables are assumed to be "intensive" global
|
|
|
|
quantities, which are thus printed as-is, without normalization by
|
|
|
|
thermo_style custom. You can include a division by "natoms" in the
|
|
|
|
variable formula if this is not the case.
|
2006-09-22 00:22:34 +08:00
|
|
|
|
2007-02-10 05:37:30 +08:00
|
|
|
:line
|
2006-09-22 00:22:34 +08:00
|
|
|
|
|
|
|
[Restrictions:]
|
|
|
|
|
|
|
|
This command must come after the simulation box is defined by a
|
|
|
|
"read_data"_read_data.html, "read_restart"_read_restart.html, or
|
|
|
|
"create_box"_create_box.html command.
|
|
|
|
|
|
|
|
[Related commands:]
|
|
|
|
|
|
|
|
"thermo"_thermo.html, "thermo_modify"_thermo_modify.html,
|
2008-01-04 08:37:21 +08:00
|
|
|
"fix_modify"_fix_modify.html, "compute temp"_compute_temp.html,
|
|
|
|
"compute pressure"_compute_pressure.html
|
2006-09-22 00:22:34 +08:00
|
|
|
|
|
|
|
[Default:]
|
|
|
|
|
|
|
|
thermo_style one :pre
|