3 <TITLE>mdp options</TITLE>
4 <LINK rel=stylesheet href="style.css" type="text/css">
5 <BODY text="#000000" bgcolor="#FFFFFF" link="#0000FF" vlink="#990000" alink="#FF0000">
6 <TABLE WIDTH="98%" NOBORDER >
8 <TABLE WIDTH=400 NOBORDER>
10 <a href="http://www.gromacs.org/"><img SRC="../images/gmxlogo_small.jpg"BORDER=0 height=133 width=116></a></td>
11 <td ALIGN=LEFT VALIGN=TOP WIDTH=280><br><h2>mdp options</h2><font size=-1><A HREF="../online.html">Main Table of Contents</A></font><br><br></td>
12 </TABLE></TD><TD WIDTH="*" ALIGN=RIGHT VALIGN=BOTTOM><p> </p><B>VERSION 4.6.3</B></td></tr></TABLE>
17 PLEASE BE VERY CAREFUL WHEN EDITING THIS FILE: IT MUST BE
18 AUTOMATICALLY PARSED BY A SIMPLE SCRIPT (mkmdp in the GROMACS manual repository) TO PRODUCE A
19 CORRESPONDING LATEX FILE.
21 IF YOU'RE NOT SURE ABOUT WHAT YOU'RE DOING, DON'T DO IT!
25 <H3>Table of Contents</H3>
28 <li><A HREF="#general"><b>General remarks</b></A>
30 <li><A HREF="#pp"><b>preprocessing</b></A> (include, define)
31 <li><A HREF="#run"><b>run control</b></A> (integrator, tinit, dt, nsteps, init-step, comm-mode, nstcomm, comm-grps)
32 <li><A HREF="#ld"><b>langevin dynamics</b></A> (bd-fric, ld-seed)
33 <li><A HREF="#em"><b>energy minimization</b></A> (emtol, emstep, nstcgsteep)
34 <li><a HREF="#xmdrun"><b>shell molecular dynamics</b></a>(emtol,niter,fcstep)
35 <li><a HREF="#tpi"><b>test particle insertion</b></a>(rtpi)
36 <li><A HREF="#out"><b>output control</b></A> (nstxout, nstvout, nstfout, nstlog, nstcalcenergy, nstenergy, nstxtcout, xtc-precision, xtc-grps, energygrps)
37 <li><A HREF="#nl"><b>neighbor searching</b></A> (cutoff-scheme, nstlist, nstcalclr, ns-type, pbc, periodic-molecules, verlet-buffer-drift, rlist, rlistlong)
38 <li><A HREF="#el"><b>electrostatics</b></A> (coulombtype, coulomb-modifier, rcoulomb-switch, rcoulomb, epsilon-r, epsilon-rf)
39 <li><A HREF="#vdw"><b>VdW</b></A> (vdwtype, vdw-modifier, rvdw-switch, rvdw, DispCorr)
40 <li><A HREF="#table"><b>tables</b></A> (table-extension, energygrp-table)
41 <li><A HREF="#ewald"><b>Ewald</b></A> (fourierspacing, fourier-nx, fourier-ny, fourier-nz, pme-order, ewald-rtol, ewald-geometry, epsilon-surface, optimize-fft)
42 <li><A HREF="#tc"><b>Temperature coupling</b></A> (tcoupl, nsttcouple, tc-grps, tau-t, ref-t)
43 <li><A HREF="#pc"><b>Pressure coupling</b></A> (pcoupl, pcoupltype,
44 nstpcouple, tau-p, compressibility, ref-p, refcoord-scaling)
45 <li><A HREF="#sa"><b>simulated annealing</b></A> (annealing, annealing-npoints, annealing-time, annealing-temp)
46 <li><A HREF="#vel"><b>velocity generation</b></A> (gen-vel, gen-temp, gen-seed)
47 <li><A HREF="#bond"><b>bonds</b></A> (constraints, constraint-algorithm, continuation, shake-tol, lincs-order, lincs-iter, lincs-warnangle, morse)
48 <li><A HREF="#egexcl"><b>Energy group exclusions</b></A> (energygrp-excl)
49 <li><A HREF="#walls"><b>Walls</b></A> (nwall, wall-type, wall-r-linpot, wall-atomtype,
50 wall-density, wall-ewald-zfac)
51 <li><A HREF="#pull"><b>COM pulling</b></A> (pull, ...)
52 <li><A HREF="#nmr"><b>NMR refinement</b></A> (disre, disre-weighting, disre-mixed, disre-fc, disre-tau, nstdisreout, orire, orire-fc, orire-tau, orire-fitgrp, nstorireout)
53 <li><A HREF="#free"><b>Free energy calculations</b></A> (free-energy, nstdhdl, dhdl-print-energy, init-lambda, delta-lambda, fep-lambdas, coul-lambdas, vdw-lambdas, bonded-lambdas, restraint-lambdas, mass-lambdas, temperature-lambdas, sc-alpha, sc-coul, sc-power, sc-r-power, sc-sigma, couple-moltype, couple-lambda0, couple-lambda1, couple-intramol)
54 <li><A HREF="#expanded"><b>Expanded ensemble simulation</b></A> (lmc-stats, lmc-mc-move, lmc-seed, lmc-gibbsdelta, mc-temperature, nst-transition-matrix, init-lambda-weights, initial-wl-delta, wl-scale, wl-ratio, symmetrized-transition-matrix, lmc-forced-nstart, mininum-var-min, lmc-weights-equil, weight-equil-wl-delta, weight-equil-number-all-lambda, weight-equil-number-steps, weight-equil-number-samples, weight-equil-count-ratio, simulated-tempering, simulated-tempering-scaling, sim-temp-low, sim-temp-high)
55 <li><A HREF="#neq"><b>Non-equilibrium MD</b></A> (acc-grps, accelerate, freezegrps, freezedim, cos-acceleration, deform)
56 <li><A HREF="#ef"><b>Electric fields</b></A> (E-x, E-xt, E-y, E-yt, E-z, E-zt )
57 <li><A HREF="#qmmm"><b>Mixed quantum/classical dynamics</b></A> (QMMM, QMMM-grps, QMMMscheme, QMmethod, QMbasis, QMcharge, Qmmult, CASorbitals, CASelectrons, SH)
58 <li><A HREF="#gbsa"><b>Implicit solvent</b></A> (implicit-solvent, gb-algorithm, nstgbradii, rgbradii, gb-epsilon-solvent, gb-saltconc, gb-obc-alpha, gb-obc-beta, gb-obc-gamma, gb-dielectric-offset, sa-algorithm, sa-surface-tension)
59 <li><A HREF="#adress"><b>AdResS settings</b></A> (adress, adress_type, adress_const_wf, adress_ex_width, adress_hy_width, adress_ex_forcecap, adress_interface_correction, adress_site, adress_reference_coords, adress_tf_grp_names, adress_cg_grp_names)
60 <li><A HREF="#user"><b>User defined thingies</b></A> (user1-grps, user2-grps, userint1, userint2, userint3, userint4, userreal1, userreal2, userreal3, userreal4)
61 <li><A HREF="#idx"><b>Index</b></A>
67 <A NAME="general"><br>
71 Default values are given in parentheses. The first option in
72 the list is always the default option. Units are given in
73 square brackets The difference between a dash and an underscore
77 A <a href="mdp.html">sample <TT>.mdp</TT> file</a> is
78 available. This should be appropriate to start a normal
79 simulation. Edit it to suit your specific needs and desires. </P>
83 <h3>Preprocessing</h3>
86 <dt><b>include:</b></dt>
87 <dd>directories to include in your topology. Format:
88 <PRE>-I/home/john/mylib -I../otherlib</PRE></dd>
89 <dt><b>define:</b></dt>
90 <dd>defines to pass to the preprocessor, default is no defines. You can use
91 any defines to control options in your customized topology files. Options
92 that are already available by default are:
95 <dd>Will tell <tt>grompp</tt> to include flexible water in stead of rigid water into your
96 topology, this can be useful for normal mode analysis.</dd>
98 <dd>Will tell <tt>grompp</tt> to include posre.itp into your topology, used for
99 <!--Idx-->position restraint<!--EIdx-->s.</dd>
108 <dt><b>integrator:</b> (Despite the name, this list includes algorithms that are not actually integrators. <tt>steep</tt> and all entries following it are in this category)</dt>
111 <dd>A leap-frog algorithm<!--QuietIdx-->leap-frog integrator<!--EQuietIdx-->
112 for integrating Newton's equations of motion.</dd>
113 <dt><b>md-vv</b></dt>
114 <dd>A velocity Verlet algorithm for integrating Newton's equations of motion.
115 For constant NVE simulations started from corresponding points in the same trajectory, the trajectories
116 are analytically, but not binary, identical to the <b>md</b> leap-frog integrator. The the kinetic
117 energy, which is determined from the whole step velocities and is therefore
118 slightly too high. The advantage of this integrator is more accurate,
119 reversible Nose-Hoover and Parrinello-Rahman coupling integration
120 based on Trotter expansion, as well as (slightly too small) full step velocity
121 output. This all comes at the cost off extra computation, especially with
122 constraints and extra communication in parallel. Note that for nearly all
123 production simulations the <b>md</b> integrator is accurate enough.
125 <dt><b>md-vv-avek</b></dt>
126 <dd>A velocity Verlet algorithm identical to <b>md-vv</b>, except that
127 the kinetic energy is determined as the average of
128 the two half step kinetic energies as in the <b>md</b> integrator, and this thus more accurate.
129 With Nose-Hoover and/or Parrinello-Rahman coupling this comes with
130 a slight increase in computational cost.
133 <dd> An accurate leap-frog stochastic dynamics integrator.
134 Four Gaussian random number are required
135 per integration step per degree of freedom. With constraints,
136 coordinates needs to be constrained twice per integration step.
137 Depending on the computational cost of the force calculation,
138 this can take a significant part of the simulation time.
139 The temperature for one or more groups of atoms
140 (<b><A HREF="#tc">tc-grps</A></b>)
141 is set with <b><A HREF="#tc">ref-t</A></b> [K],
142 the inverse friction constant for each group is set with
143 <b><A HREF="#tc">tau-t</A></b> [ps].
144 The parameter <b><A HREF="#tc">tcoupl</A></b> is ignored.
145 The random generator is initialized with <b><A HREF="#ld">ld-seed</A></b>.
146 When used as a thermostat, an appropriate value for <b>tau-t</b> is 2 ps,
147 since this results in a friction that is lower than the internal friction
148 of water, while it is high enough to remove excess heat
149 (unless <b>cut-off</b> or <b>reaction-field</b> electrostatics is used).
150 NOTE: temperature deviations decay twice as fast as with
151 a Berendsen thermostat with the same <b>tau-t</b>.</dd>
153 <dd> An efficient leap-frog stochastic dynamics integrator.
154 This integrator is equivalent to <b>sd</b>, except that it requires
155 only one Gaussian random number and one constraint step and is therefore
156 significantly faster. Without constraints the accuracy is the same as <b>sd</b>.
157 With constraints the accuracy is significantly reduced, so then <b>sd</b>
158 will often be preferred.</dd>
160 <dd>An Euler integrator for Brownian or position Langevin dynamics, the
161 velocity is the force divided by a friction coefficient
162 (<b><A HREF="#ld">bd-fric</A></b> [amu ps<sup>-1</sup>])
163 plus random thermal noise (<b><A HREF="#tc">ref-t</A></b>).
164 When <b><A HREF="#ld">bd-fric</A></b><tt>=0</tt>, the friction coefficient for each
165 particle is calculated as mass/<b><A HREF="#tc">tau-t</A></b>, as for the
166 integrator <tt>sd</tt>.
167 The random generator is initialized with <b><A HREF="#ld">ld-seed</A></b>.</dd>
169 <dt><b>steep</b></dt>
170 <dd>A <!--Idx-->steepest descent<!--EIdx--> algorithm for energy
171 minimization. The maximum step size is <b><A HREF="#em">emstep</A></b>
172 [nm], the tolerance is <b><A HREF="#em">emtol</A></b> [kJ
173 mol<sup>-1</sup> nm<sup>-1</sup>].</dd>
175 <dd>A <!--Idx-->conjugate gradient<!--EIdx--> algorithm for energy
176 minimization, the tolerance is <b>emtol</b> [kJ mol<sup>-1</sup>
177 nm<sup>-1</sup>]. CG is more efficient when a steepest descent step
178 is done every once in a while, this is determined by
179 <b><A HREF="#em">nstcgsteep</A></b>.
180 For a minimization prior to a normal mode analysis, which requires
181 a very high accuracy, GROMACS should be compiled in double precision.</dd>
182 <dt><b>l-bfgs</b></dt>
183 <dd>A <!--Idx-->quasi-Newtonian<!--EIdx--> algorithm for energy minimization
184 according to the low-memory Broyden-Fletcher-Goldfarb-Shanno approach.
185 In practice this seems to converge faster than Conjugate Gradients, but due
186 to the correction steps necessary it is not (yet) parallelized.
189 <dd>Normal mode analysis<!--QuietIdx-->normal-mode analysis<!--EQuietIdx--> is performed
190 on the structure in the <tt>tpr</tt> file. GROMACS should be
191 compiled in double precision.</dd>
193 <dd> Test particle insertion. The last molecule in the topology
194 is the test particle. A trajectory should be provided with
195 the <tt>-rerun</tt> option of <tt>mdrun</tt>. This trajectory
196 should not contain the molecule to be inserted. Insertions
197 are performed <b>nsteps</b> times in each frame at random locations
198 and with random orientiations of the molecule. When <b>nstlist</b>
199 is larger than one, <b>nstlist</b> insertions are performed
200 in a sphere with radius <b><A HREF="#tpi">rtpi</A></b>
201 around a the same random location using the same neighborlist
202 (and the same long-range energy when <b>rvdw</b> or <b>rcoulomb</b>><b>rlist</b>,
203 which is only allowed for single-atom molecules).
204 Since neighborlist construction is expensive, one can perform several
205 extra insertions with the same list almost for free.
206 The random seed is set with <b><A HREF="#ld">ld-seed</A></b>.
207 The temperature for the Boltzmann weighting is set with
208 <b><A HREF="#tc">ref-t</A></b>, this should match the temperature
209 of the simulation of the original trajectory.
210 Dispersion correction is implemented correctly for tpi.
211 All relevant quantities are written to the file specified with
212 the <tt>-tpi</tt> option of <tt>mdrun</tt>.
213 The distribution of insertion energies is written to the file specified with
214 the <tt>-tpid</tt> option of <tt>mdrun</tt>.
215 No trajectory or energy file is written.
216 Parallel tpi gives identical results to single node tpi.
217 For charged molecules, using PME with a fine grid is most accurate
218 and also efficient, since the potential in the system only needs
219 to be calculated once per frame.
222 <dd> Test particle insertion into a predefined cavity location.
223 The procedure is the same as for <b>tpi</b>, except that one coordinate
224 extra is read from the trajectory, which is used as the insertion location.
225 The molecule to be inserted should be centered at 0,0,0. Gromacs does
226 not do this for you, since for different situations a different
227 way of centering might be optimal.
228 Also <b><A HREF="#tpi">rtpi</A></b> sets the radius for the sphere
229 around this location. Neighbor searching is done only once per frame,
230 <b>nstlist</b> is not used.
231 Parallel tpic gives identical results to single node tpic.
234 <dt><b>tinit: (0) [ps]</b></dt>
235 <dd>starting time for your run (only makes sense for integrators <tt>md</tt>,
236 <tt>sd</tt> and <tt>bd</tt>)</dd>
237 <dt><b>dt: (0.001) [ps]</b></dt></dd>
238 <dd>time step for integration (only makes sense for integrators <tt>md</tt>,
239 <tt>sd</tt> and <tt>bd</tt>)</dd>
240 <dt><b>nsteps: (0)</b></dt>
241 <dd>maximum number of steps to integrate or minimize, -1 is no maximum</dd>
242 <dt><b>init-step: (0)</b></dt>
243 <dd>The starting step.
244 The time at an step i in a run is calculated as: t = <tt>tinit</tt> + <tt>dt</tt>*(<tt>init-step</tt> + i).
245 The free-energy lambda is calculated as: lambda = <tt>init-lambda</tt> + <tt>delta-lambda</tt>*(<tt>init-step</tt> + i).
246 Also non-equilibrium MD parameters can depend on the step number.
247 Thus for exact restarts or redoing part of a run it might be necessary to
248 set <tt>init-step</tt> to the step number of the restart frame.
249 <tt>tpbconv</tt> does this automatically.
251 <dt><b>comm-mode:</b></dt>
253 <dt><b>Linear</b></dt>
254 <dd>Remove center of mass translation</dd>
255 <dt><b>Angular</b></dt>
256 <dd>Remove center of mass translation and rotation around the center of mass
259 <dd>No restriction on the center of mass motion
261 <dt><b>nstcomm: (100) [steps]</b></dt>
262 <dd>frequency for center of mass motion removal</dd>
263 <dt><b>comm-grps:</b></dt>
264 <dd>group(s) for center of mass motion removal, default is the whole system</dd>
269 <h3><!--Idx-->Langevin dynamics<!--EIdx--></h3>
272 <dt><b>bd-fric: (0) [amu ps<sup>-1</sup>]</b></dt>
273 <dd>Brownian dynamics friction coefficient.
274 When <b>bd-fric</b><tt>=0</tt>, the friction coefficient for each
275 particle is calculated as mass/<b><A HREF="#tc">tau-t</A></b>.</dd>
276 <dt><b>ld-seed: (1993) [integer]</b></dt>
277 <dd>used to initialize random generator for thermal noise
278 for stochastic and Brownian dynamics.
279 When <b>ld-seed</b> is set to -1, the seed is calculated from the process ID.
280 When running BD or SD on multiple processors, each processor uses a seed equal
281 to <b>ld-seed</b> plus the processor number.</dd>
286 <h3>Energy minimization<!--QuietIdx-->energy minimization<!--EQuietIdx--></h3>
288 <dt><b>emtol: (10.0) [kJ mol<sup>-1</sup> nm<sup>-1</sup>]</b></dt>
289 <dd>the minimization is converged when the maximum force is smaller than
291 <dt><b>emstep: (0.01) [nm]</b></dt>
292 <dd>initial step-size</dd>
293 <dt><b>nstcgsteep: (1000) [steps]</b></dt>
294 <dd>frequency of performing 1 steepest descent step while doing
295 conjugate gradient energy minimization.</dd>
296 <dt><b>nbfgscorr: (10)</b></dt>
297 <dd>Number of correction steps to use for L-BFGS minimization. A higher
298 number is (at least theoretically) more accurate, but slower.</dd>
301 <A NAME="xmdrun"><br>
303 <h3>Shell Molecular Dynamics<!--QuietIdx-->shell molecular dynamics<!--EQuietIdx--></h3>
305 flexible constraints are present in the system the positions of the shells
306 and the lengths of the flexible constraints are optimized at
307 every time step until either the RMS force on the shells and constraints
308 is less than emtol, or a maximum number of iterations (niter) has been reached
310 <dt><b>emtol: (10.0) [kJ mol<sup>-1</sup> nm<sup>-1</sup>]</b></dt>
311 <dd>the minimization is converged when the maximum force is smaller than
312 this value. For shell MD this value should be 1.0 at most, but since the
313 variable is used for energy minimization as well the default is 10.0.</dd>
314 <dt><b>niter: (20)</b></dt>
315 <dd>maximum number of iterations for optimizing the shell positions
316 and the flexible constraints.</dd>
317 <dt><b>fcstep: (0) [ps<sup>2</sup>]</b></dt>
318 <dd>the step size for optimizing the flexible constraints.
319 Should be chosen as mu/(d<sup>2</sup>V/dq<sup>2</sup>)
320 where mu is the reduced mass of two particles in a flexible constraint
321 and d<sup>2</sup>V/dq<sup>2</sup> is the second derivative of the potential
322 in the constraint direction. Hopefully this number does not differ too
323 much between the flexible constraints, as the number of iterations
324 and thus the runtime is very sensitive to <tt>fcstep</tt>.
325 Try several values!</dd>
330 <h3>Test particle insertion</h3>
332 <dt><b>rtpi: (0.05) [nm]</b></dt>
333 <dd>the test particle insertion radius see integrators
334 <b><a href="#run">tpi</a></b> and <b><a href="#run">tpic</a></b></dd>
339 <h3>Output control</h3>
341 <dt><b>nstxout: (0) [steps]</b></dt>
342 <dd>frequency to write coordinates to output
343 <!--Idx-->trajectory file<!--EIdx-->, the last coordinates are always written</dd>
344 <dt><b>nstvout: (0) [steps]</b></dt>
345 <dd>frequency to write velocities to output trajectory,
346 the last velocities are always written</dd>
347 <dt><b>nstfout: (0) [steps]</b></dt>
348 <dd>frequency to write forces to output trajectory.</dd>
349 <dt><b>nstlog: (1000) [steps]</b></dt>
350 <dd>frequency to write energies to <!--Idx-->log file<!--EIdx-->,
351 the last energies are always written</dd>
352 <dt><b>nstcalcenergy: (100)</b></dt>
353 <dd>frequency for calculating the energies, 0 is never.
354 This option is only relevant with dynamics.
355 With a twin-range cut-off setup <b>nstcalcenergy</b> should be equal to
356 or a multiple of <b>nstlist</b>.
357 This option affects the performance in parallel simulations,
358 because calculating energies requires global communication between all
359 processes which can become a bottleneck at high parallelization.
361 <dt><b>nstenergy: (1000) [steps]</b></dt>
362 <dd>frequency to write energies to energy file,
363 the last energies are always written,
364 should be a multiple of <b>nstcalcenergy</b>.
365 Note that the exact sums and fluctuations over all MD steps
366 modulo <b>nstcalcenergy</b> are stored in the energy file,
367 so <tt>g_energy</tt> can report exact
368 energy averages and fluctuations also when <b>nstenergy</b><tt>>1</tt></dd>
369 <dt><b>nstxtcout: (0) [steps]</b></dt>
370 <dd>frequency to write coordinates to xtc trajectory</dd>
371 <dt><b>xtc-precision: (1000) [real]</b></dt>
372 <dd>precision to write to xtc trajectory</dd>
373 <dt><b>xtc-grps:</b></dt>
374 <dd>group(s) to write to xtc trajectory, default the whole system is written
375 (if <b>nstxtcout</b> > 0)</dd>
376 <dt><b>energygrps:</b></dt>
377 <dd>group(s) to write to energy file</dd>
382 <h3>Neighbor searching<!--QuietIdx-->neighbor searching<!--EQuietIdx--></h3>
384 <dt><b>cutoff-scheme:</b></dt>
386 <dt><b>group</b></dt>
387 <dd>Generate a pair list for groups of atoms. These groups correspond to the
388 charge groups in the topology. This was the only cut-off treatment scheme
390 There is no explicit buffering of the pair list. This enables efficient force
391 calculations, but energy is only conserved when a buffer is explicitly added.
392 For energy conservation, the <b>Verlet</b> option provides a more convenient
393 and efficient algorithm.</dd>
395 <dt><b>Verlet</b></dt>
396 <dd>Generate a pair list with buffering. The buffer size is automatically set
397 based on <b>verlet-buffer-drift</b>, unless this is set to -1, in which case
398 <b>rlist</b> will be used. This option has an explicit, exact cut-off at
399 <b>rvdw</b>=<b>rcoulomb</b>. Currently only cut-off, reaction-field,
400 PME electrostatics and plain LJ are supported. Some <tt>mdrun</tt> functionality
401 is not yet supported with the <b>Verlet</b> scheme, but <tt>grompp</tt> checks for this.
402 Native GPU acceleration is only supported with <b>Verlet</b>. With GPU-accelerated PME,
403 <tt>mdrun</tt> will automatically tune the CPU/GPU load balance by
404 scaling <b>rcoulomb</b> and the grid spacing. This can be turned off with
407 <b>Verlet</b> is somewhat faster than <b>group</b> when there is no water, or if <b>group</b> would use a pair-list buffer to conserve energy.
411 <dt><b>nstlist: (10) [steps]</b></dt>
413 <dt><b>>0</b></dt>
414 <dd>Frequency to update the <!--Idx-->neighbor list<!--EIdx--> (and
415 the long-range forces, when using twin-range cut-offs). When this is 0,
416 the neighbor list is made only once.
417 With energy minimization the neighborlist will be updated for every
418 energy evaluation when <b>nstlist</b><tt>>0</tt>.
419 With non-bonded force calculation on the GPU, a value of 20 or more gives
420 the best performance.</dd>
422 <dd>The neighbor list is only constructed once and never updated.
423 This is mainly useful for vacuum simulations in which all particles
426 <dd>Automated update frequency, only supported with <b>cutoff-scheme</b>=<b>group</b>.
427 This can only be used with switched, shifted or user potentials where
428 the cut-off can be smaller than <b>rlist</b>. One then has a buffer
429 of size <b>rlist</b> minus the longest cut-off.
430 The neighbor list is only updated when one or more particles have moved further
431 than half the buffer size from the center of geometry of their charge group
432 as determined at the previous neighbor search.
433 Coordinate scaling due to pressure coupling or the <b>deform</b> option
434 is taken into account.
435 This option guarantees that their are no cut-off artifacts,
436 but for larger systems this can come at a high computational cost,
437 since the neighbor list update frequency will be determined
438 by just one or two particles moving slightly beyond the half buffer length
439 (which does not necessarily imply that the neighbor list is invalid),
440 while 99.99% of the particles are fine.
444 <dt><b>nstcalclr: (-1) [steps]</b></dt>
446 Controls the period between calculations of long-range forces when
447 using the group cut-off scheme.
450 <dd>Calculate the long-range forces every single step. This is useful
451 to have separate neighbor lists with buffers for electrostatics and Van
452 der Waals interactions, and in particular it makes it possible to have
453 the Van der Waals cutoff longer than electrostatics (useful e.g. with
454 PME). However, there is no point in having identical long-range
455 cutoffs for both interaction forms and update them every step - then
456 it will be slightly faster to put everything in the short-range
458 <dt><b>>1</b></dt>
459 <dd>Calculate the long-range forces every <b>nstcalclr</b> steps and
460 use a multiple-time-step integrator to combine forces. This can now be
461 done more frequently than <b>nstlist</b> since the lists are stored,
462 and it might be a good idea e.g. for Van der Waals interactions that
463 vary slower than electrostatics.</dd>
465 <dd>Calculate long-range forces on steps where neighbor searching is
466 performed. While this is the default value, you might want to consider
467 updating the long-range forces more frequently.</dd>
469 Note that twin-range force evaluation might be enabled automatically
470 by PP-PME load balancing. This is done in order to maintain the chosen
471 Van der Waals interaction radius even if the load balancing is
472 changing the electrostatics cutoff. If the <tt>.mdp</tt> file already
473 specifies twin-range interactions (e.g. to evaluate Lennard-Jones
474 interactions with a longer cutoff than the PME electrostatics every
475 2-3 steps), the load balancing will have also a small effect on
476 Lennard-Jones, since the short-range cutoff (inside which forces are
477 evaluated every step) is changed.
482 <dt><b>ns-type:</b></dt>
485 <dd>Make a grid in the box and only check atoms in neighboring grid
486 cells when constructing a new neighbor list every <b>nstlist</b> steps.
487 In large systems grid search is much faster than simple search.</dd>
488 <dt><b>simple</b></dt>
489 <dd>Check every atom in the box when constructing a new neighbor list
490 every <b>nstlist</b> steps.</dd>
496 <dd>Use periodic boundary conditions in all directions.</dd>
498 <dd>Use no periodic boundary conditions, ignore the box.
499 To simulate without cut-offs, set all cut-offs to 0 and <b>nstlist</b><tt>=0</tt>.
500 For best performance without cut-offs, use <b>nstlist</b><tt>=0</tt>,
501 <b>ns-type</b><tt>=simple</tt>
502 and particle decomposition instead of domain decomposition.</dd>
504 <dd>Use periodic boundary conditions in x and y directions only.
505 This works only with <b>ns-type</b><tt>=grid</tt> and can be used
506 in combination with <b><a href="#walls">walls</a></b>.
507 Without walls or with only one wall the system size is infinite
508 in the z direction. Therefore pressure coupling or Ewald summation
509 methods can not be used.
510 These disadvantages do not apply when two walls are used.</dd>
513 <dt><b>periodic-molecules:</b></dt>
516 <dd>molecules are finite, fast molecular PBC can be used</dd>
518 <dd>for systems with molecules that couple to themselves through
519 the periodic boundary conditions, this requires a slower PBC algorithm
520 and molecules are not made whole in the output</dd>
523 <dt><b>verlet-buffer-drift: (0.005) [kJ/mol/ps]</b></dt>
524 <dd>Useful only with <b>cutoff-scheme</b>=<b>Verlet</b>. This sets the target energy drift
525 per particle caused by the Verlet buffer, which indirectly sets <b>rlist</b>.
526 As both <b>nstlist</b> and the Verlet buffer size are fixed
527 (for performance reasons), particle pairs not in the pair list can occasionally
528 get within the cut-off distance during <b>nstlist</b>-1 nsteps. This
529 generates energy drift. In a constant-temperature ensemble, the drift can be
530 estimated for a given cut-off and <b>rlist</b>. The estimate assumes a
531 homogeneous particle distribution, hence the drift might be slightly
532 underestimated for multi-phase systems. For longer pair-list life-time
533 (<b>nstlist</b>-1)*dt the drift is overestimated, because the interactions
534 between particles are ignored. Combined with cancellation of errors,
535 the actual energy drift is usually one to two orders of magnitude smaller.
536 Note that the generated buffer size takes into account that
537 the GROMACS pair-list setup leads to a reduction in the drift by
538 a factor 10, compared to a simple particle-pair based list.
539 Without dynamics (energy minimization etc.), the buffer is 5% of the cut-off.
540 For dynamics without temperature coupling or to override the buffer size,
541 use <b>verlet-buffer-drift</b>=-1 and set <b>rlist</b> manually.</dd>
543 <dt><b>rlist: (1) [nm]</b></dt>
544 <dd>Cut-off distance for the short-range neighbor list.
545 With <b>cutoff-scheme</b>=<b>Verlet</b>, this is by default set by the
546 <b>verlet-buffer-drift</b> option and the value of <b>rlist</b> is ignored.</dd>
548 <dt><b>rlistlong: (-1) [nm]</b></dt>
549 <dd>Cut-off distance for the long-range neighbor list.
550 This parameter is only relevant for a twin-range cut-off setup
551 with switched potentials. In that case a buffer region is required to account
552 for the size of charge groups. In all other cases this parameter
553 is automatically set to the longest cut-off distance.</dd>
559 <h3>Electrostatics<!--QuietIdx-->electrostatics<!--EQuietIdx--></h3>
561 <dt><b>coulombtype:</b></dt>
564 <dt><b>Cut-off</b></dt>
565 <dd>Twin range cut-offs with neighborlist cut-off <b>rlist</b> and
566 Coulomb cut-off <b>rcoulomb</b>,
567 where <b>rcoulomb</b>≥<b>rlist</b>.
569 <dt><b>Ewald</b></dt>
570 <dd>Classical <!--Idx-->Ewald sum<!--EIdx--> electrostatics.
571 The real-space cut-off <b>rcoulomb</b> should be equal to <b>rlist</b>.
572 Use e.g. <b>rlist</b><tt>=0.9</tt>, <b>rcoulomb</b><tt>=0.9</tt>. The highest magnitude of
573 wave vectors used in reciprocal space is controlled by <b>fourierspacing</b>.
574 The relative accuracy of direct/reciprocal space
575 is controlled by <b>ewald-rtol</b>.
577 NOTE: Ewald scales as O(N<sup>3/2</sup>)
578 and is thus extremely slow for large systems. It is included mainly for
579 reference - in most cases PME will perform much better.</dd>
581 <dt><b><!--Idx-->PME<!--EIdx--></b></dt>
582 <dd>Fast smooth Particle-Mesh Ewald (SPME) electrostatics. Direct space is similar
583 to the Ewald sum, while the reciprocal part is performed with
584 FFTs. Grid dimensions are controlled with <b>fourierspacing</b> and the
585 interpolation order with <b>pme-order</b>. With a grid spacing of 0.1
586 nm and cubic interpolation the electrostatic forces have an accuracy
587 of 2-3*10<sup>-4</sup>. Since the error from the vdw-cutoff is larger than this you
588 might try 0.15 nm. When running in parallel the interpolation
589 parallelizes better than the FFT, so try decreasing grid dimensions
590 while increasing interpolation.</dd>
592 <dt><b><!--Idx-->P3M-AD<!--EIdx--></b></dt>
593 <dd>Particle-Particle Particle-Mesh algorithm with analytical derivative
594 for for long range electrostatic interactions. The method and code
595 is identical to SPME, except that the influence function is optimized
596 for the grid. This gives a slight increase in accuracy.</dd>
598 <dt><b>Reaction-Field electrostatics<!--QuietIdx-->reaction-field electrostatics<!--EQuietIdx--></b></dt>
599 <dd>Reaction field with Coulomb cut-off <b>rcoulomb</b>,
600 where <b>rcoulomb</b> ≥ <b>rlist</b>.
601 The dielectric constant beyond the cut-off is <b>epsilon-rf</b>.
602 The dielectric constant can be set to infinity by setting <b>epsilon-rf</b><tt>=0</tt>.</dd>
604 <dt><b>Generalized-Reaction-Field</b></dt>
605 <dd>Generalized reaction field with Coulomb cut-off <b>rcoulomb</b>,
606 where <b>rcoulomb</b> ≥ <b>rlist</b>.
607 The dielectric constant beyond the cut-off is <b>epsilon-rf</b>.
608 The ionic strength is computed from the number of charged
609 (i.e. with non zero charge) <!--Idx-->charge group<!--EIdx-->s.
610 The temperature for the GRF potential is set with
611 <b><A HREF="#tc">ref-t</A></b> [K].</dd>
613 <dt><b>Reaction-Field-zero</b></dt>
614 <dd>In GROMACS, normal reaction-field electrostatics with
615 <b>cutoff-scheme</b><b>=group</b> leads to bad
616 energy conservation. <b>Reaction-Field-zero</b> solves this
617 by making the potential zero beyond the cut-off. It can only
618 be used with an infinite dielectric constant (<b>epsilon-rf=0</b>),
619 because only for that value the force vanishes at the cut-off.
620 <b>rlist</b> should be 0.1 to 0.3 nm larger than <b>rcoulomb</b>
621 to accommodate for the size of charge groups and diffusion
622 between neighbor list updates. This, and the fact that table lookups
623 are used instead of analytical functions make <b>Reaction-Field-zero</b>
624 computationally more expensive than normal reaction-field.</dd>
626 <dt><b>Reaction-Field-nec</b></dt>
627 <dd>The same as <b>Reaction-Field</b>, but implemented as in
628 GROMACS versions before 3.3. No reaction-field correction is applied
629 to excluded atom pairs and self pairs.
630 The 1-4 interactions are calculated using a reaction-field.
631 The missing correction due to the excluded pairs that do not have a 1-4
632 interaction is up to a few percent of the total electrostatic
633 energy and causes a minor difference in the forces and the pressure.</dd>
635 <dt><b>Shift</b></dt>
636 <dd>Analogous to <b>Shift</b> for <b>vdwtype</b>.
637 You might want to use <b>Reaction-Field-zero</b> instead,
638 which has a similar potential shape, but has a physical interpretation
639 and has better energies due to the exclusion correction terms.
642 <dt><b>Encad-Shift</b></dt>
644 potential is decreased over the whole range, using the definition
645 from the Encad simulation package.</dd>
647 <dt><b>Switch</b></dt>
648 <dd>Analogous to <b>Switch</b> for <b>vdwtype</b>.
649 Switching the Coulomb potential can lead to serious artifacts,
650 advice: use <b>Reaction-Field-zero</b> instead.</dd>
653 <dd><a name="usertab"></a><tt>mdrun</tt> will now expect to find a file
654 <tt>table.xvg</tt> with user-defined potential functions for
655 repulsion, dispersion and Coulomb. When pair interactions are present,
656 <tt>mdrun</tt> also expects to find a file <tt>tablep.xvg</tt> for
657 the pair interactions. When the same interactions should be used
658 for non-bonded and pair interactions the user can specify the same
659 file name for both table files.
660 These files should contain 7
661 columns: the <tt>x</tt> value,
662 <tt>f(x)</tt>, <tt>-f'(x)</tt>,
663 <tt>g(x)</tt>, <tt>-g'(x)</tt>,
664 <tt>h(x)</tt>, <tt>-h'(x)</tt>,
665 where <tt>f(x)</tt> is the Coulomb function, <tt>g(x)</tt> the dispersion function
666 and <tt>h(x)</tt> the repulsion function.
667 When <b>vdwtype</b> is not set to <b>User</b> the values
668 for <tt>g</tt>, <tt>-g'</tt>, <tt>h</tt> and <tt>-h'</tt> are ignored.
669 For the non-bonded interactions <tt>x</tt> values should run
670 from 0 to the largest cut-off distance + <b>table-extension</b>
671 and should be uniformly spaced. For the pair interactions the table
672 length in the file will be used.
673 The optimal spacing, which is used for non-user tables,
674 is <tt>0.002</tt> [nm] when you run in single precision
675 or <tt>0.0005</tt> [nm] when you run in double precision.
676 The function value at <tt>x=0</tt> is not important. More information is
677 in the printed manual.</dd>
679 <dt><b>PME-Switch</b></dt>
680 <dd>A combination of PME and a switch function for the direct-space part
681 (see above). <b>rcoulomb</b> is allowed to be smaller than <b>rlist</b>.
682 This is mainly useful constant energy simulations (note that using
683 <b>PME</b> with <b>cutoff-scheme</b>=<b>Verlet</b> will be more efficient).
686 <dt><b>PME-User</b></dt>
687 <dd>A combination of PME and user tables (see above).
688 <b>rcoulomb</b> is allowed to be smaller than <b>rlist</b>.
689 The PME mesh contribution is subtracted from the user table by <tt>mdrun</tt>.
690 Because of this subtraction the user tables should contain
691 about 10 decimal places.</dd>
693 <dt><b>PME-User-Switch</b></dt>
694 <dd>A combination of PME-User and a switching function (see above).
695 The switching function is applied to final particle-particle interaction,
696 i.e. both to the user supplied function and the PME Mesh correction part.</dd>
700 <dt><b>coulomb-modifier:</b></dt>
702 <dt><b>Potential-shift-Verlet</b></dt>
703 <dd>Selects <b>Potential-shift</b> with the Verlet cutoff-scheme,
704 as it is (nearly) free; selects <b>None</b> with the group cutoff-scheme.</dd>
705 <dt><b>Potential-shift</b></dt>
706 <dd>Shift the Coulomb potential by a constant such that it is zero at the cut-off.
707 This makes the potential the integral of the force. Note that this does not
708 affect the forces or the sampling.</dd>
710 <dd>Use an unmodified Coulomb potential. With the group scheme this means no exact cut-off is used, energies and forces are calculated for all pairs in the neighborlist.</dd>
715 <dt><b>rcoulomb-switch: (0) [nm]</b></dt>
716 <dd>where to start switching the Coulomb potential</dd>
718 <dt><b>rcoulomb: (1) [nm]</b></dt>
719 <dd>distance for the Coulomb <!--Idx-->cut-off<!--EIdx--></dd>
721 <dt><b>epsilon-r: (1)</b></dt>
722 <dd>The relative <!--Idx-->dielectric constant<!--EIdx-->.
723 A value of 0 means infinity.</dd>
725 <dt><b>epsilon-rf: (0)</b></dt>
726 <dd>The relative dielectric constant of the reaction field.
727 This is only used with reaction-field electrostatics.
728 A value of 0 means infinity.</dd>
735 <dt><b>vdwtype:</b></dt>
737 <dt><b>Cut-off</b></dt>
738 <dd>Twin range cut-offs with neighbor list cut-off <b>rlist</b> and
739 VdW cut-off <b>rvdw</b>,
740 where <b>rvdw</b> <tt>≥</tt> <b>rlist</b>.</dd>
741 <dt><b>Shift</b></dt>
742 <dd>The LJ (not Buckingham) potential is decreased over the whole
743 range and the forces decay smoothly to zero between <b>rvdw-switch</b>
744 and <b>rvdw</b>. The neighbor search cut-off <b>rlist</b> should be
745 0.1 to 0.3 nm larger than <b>rvdw</b> to accommodate for the size of
746 charge groups and diffusion between neighbor list
749 <dt><b>Switch</b></dt>
750 <dd>The LJ (not Buckingham)
751 potential is normal out to <b>rvdw-switch</b>, after which it is switched
752 off to reach zero at <b>rvdw</b>. Both the potential and force functions
753 are continuously smooth, but be aware that all switch functions will give rise
754 to a bulge (increase) in the force (since we are switching the potential).
755 The neighbor search cut-off <b>rlist</b> should be 0.1 to 0.3 nm larger than
756 <b>rvdw</b> to accommodate for the size of charge groups and diffusion
757 between neighbor list updates.</dd>
759 <dt><b>Encad-Shift</b></dt>
760 <dd>The LJ (not Buckingham)
761 potential is decreased over the whole range, using the definition
762 from the Encad simulation package.</dd>
765 <dd>See <b><a href="#usertab">user</a></b> for <b>coulombtype</b>.
766 The function value at <tt>x=0</tt> is not important. When you want to
767 use LJ correction, make sure that <b>rvdw</b> corresponds to the
768 cut-off in the user-defined function.
769 When <b>coulombtype</b> is not set to <b>User</b> the values
770 for <tt>f</tt> and <tt>-f'</tt> are ignored.</dd>
773 <dt><b>vdw-modifier:</b></dt>
775 <dt><b>Potential-shift-Verlet</b></dt>
776 <dd>Selects <b>Potential-shift</b> with the Verlet cutoff-scheme,
777 as it is (nearly) free; selects <b>None</b> with the group cutoff-scheme.</dd>
778 <dt><b>Potential-shift</b></dt>
779 <dd>Shift the Van der Waals potential by a constant such that it is zero at the cut-off.
780 This makes the potential the integral of the force. Note that this does not
781 affect the forces or the sampling.</dd>
783 <dd>Use an unmodified Van der Waals potential. With the group scheme this means no exact cut-off is used, energies and forces are calculated for all pairs in the neighborlist.</dd>
786 <dt><b>rvdw-switch: (0) [nm]</b></dt>
787 <dd>where to start switching the LJ potential</dd>
789 <dt><b>rvdw: (1) [nm]</b></dt>
790 <dd>distance for the LJ or Buckingham <!--Idx-->cut-off<!--EIdx--></dd>
792 <dt><b>DispCorr:</b></dt>
793 <dd><dl compact></dd>
795 <dd>don't apply any correction</dd>
796 <dt><b>EnerPres</b></dt>
797 <dd>apply long range <!--Idx-->dispersion correction<!--EIdx-->s for Energy
800 <dd>apply long range dispersion corrections for Energy
809 <dt><b>table-extension: (1) [nm]</b></dt>
810 <dd>Extension of the non-bonded potential lookup tables beyond the largest cut-off distance.
811 The value should be large enough to account for charge group sizes
812 and the diffusion between neighbor-list updates.
813 Without user defined potential the same table length is used
814 for the lookup tables for the 1-4 interactions,
815 which are always tabulated irrespective of the use of
816 tables for the non-bonded interactions. </dd>
818 <dt><b>energygrp-table:</b></dt>
819 <dd>When user tables are used for electrostatics and/or VdW,
820 here one can give pairs of energy groups for which seperate
821 user tables should be used.
822 The two energy groups will be appended to the table file name,
823 in order of their definition in <b>energygrps</b>, seperated by underscores.
824 For example, if <tt>energygrps = Na Cl Sol</tt>
825 and <tt>energygrp-table = Na Na Na Cl</tt>, <tt>mdrun</tt> will read
826 <tt>table_Na_Na.xvg</tt> and <tt>table_Na_Cl.xvg</tt> in addition
827 to the normal <tt>table.xvg</tt> which will be used for all other
836 <dt><b>fourierspacing: (0.12) [nm]</b></dt>
837 <dd>For ordinary Ewald, the ratio of the box dimensions and the spacing
838 determines a lower bound for the number of wave vectors to use in each
839 (signed) direction. For PME and P3M, that ratio determines a lower bound
840 for the number of Fourier-space grid points that will be used along that
841 axis. In all cases, the number for each direction can be overridden by
842 entering a non-zero value for <b>fourier_n[xyz]</b>.
843 For optimizing the relative load of the particle-particle interactions
844 and the mesh part of PME, it is useful to know that
845 the accuracy of the electrostatics remains nearly constant
846 when the Coulomb cut-off and the PME grid spacing are scaled
847 by the same factor.</dd>
849 <dt><b>fourier-nx (0) ; fourier-ny (0) ; fourier-nz: (0)</b></dt>
850 <dd>Highest magnitude of wave vectors in reciprocal space when using Ewald.</dd>
851 <dd>Grid size when using PME or P3M. These values override
852 <b>fourierspacing</b> per direction. The best choice is powers of
853 2, 3, 5 and 7. Avoid large primes.</dd>
855 <dt><b>pme-order (4)</b></dt>
856 <dd>Interpolation order for PME. 4 equals cubic interpolation. You might try
857 6/8/10 when running in parallel and simultaneously decrease grid dimension.</dd>
859 <dt><b>ewald-rtol (1e-5)</b></dt>
860 <dd>The relative strength of the Ewald-shifted direct potential at
861 <b>rcoulomb</b> is given by <b>ewald-rtol</b>.
862 Decreasing this will give a more accurate direct sum,
863 but then you need more wave vectors for the reciprocal sum.</dd>
865 <dt><b>ewald-geometry: (3d)</b></dt>
868 <dd>The Ewald sum is performed in all three dimensions.</dd>
870 <dd>The reciprocal sum is still performed in 3D,
871 but a force and potential correction applied in the <tt>z</tt>
872 dimension to produce a pseudo-2D summation.
873 If your system has a slab geometry in the <tt>x-y</tt> plane you can
874 try to increase the <tt>z</tt>-dimension of the box (a box height of 3 times
875 the slab height is usually ok)
876 and use this option.</dd>
879 <dt><b>epsilon-surface: (0)</b></dt>
880 <dd>This controls the dipole correction to the Ewald summation in 3D. The
881 default value of zero means it is turned off. Turn it on by setting it to the value
882 of the relative permittivity of the imaginary surface around your infinite system. Be
883 careful - you shouldn't use this if you have free mobile charges in your system.
884 This value does not affect the slab 3DC variant of the long range corrections.</dd>
887 <dt><b>optimize-fft:</b></dt>
890 <dd>Don't calculate the optimal FFT plan for the grid at startup.</dd>
892 <dd>Calculate the optimal FFT plan for the grid at startup. This saves a
893 few percent for long simulations, but takes a couple of minutes
901 <h3>Temperature coupling<!--QuietIdx-->temperature coupling<!--EQuietIdx--></h3>
904 <dt><b>tcoupl:</b></dt>
907 <dd>No temperature coupling.</dd>
908 <dt><b>berendsen</b></dt>
909 <dd>Temperature coupling with a Berendsen-thermostat to a bath with
910 temperature <b>ref-t</b> [K], with time constant <b>tau-t</b> [ps].
911 Several groups can be coupled separately, these are specified in the
912 <b>tc-grps</b> field separated by spaces.</dd>
913 <dt><b>nose-hoover</b></dt>
914 <dd>Temperature coupling using a Nose-Hoover extended
915 ensemble. The reference temperature and coupling groups are selected
916 as above, but in this case <b>tau-t</b> [ps] controls the period
917 of the temperature fluctuations at equilibrium, which is slightly
918 different from a relaxation time.
919 For NVT simulations the conserved energy quantity is written
920 to energy and log file.</dd>
921 <dt><b>v-rescale</b></dt>
922 <dd>Temperature coupling using velocity rescaling with a stochastic term
924 This thermostat is similar to Berendsen coupling, with the same scaling
925 using <b>tau-t</b>, but the stochastic term ensures that a proper
926 canonical ensemble is generated. The random seed is set with
927 <b><A HREF="#ld">ld-seed</A></b>.
928 This thermostat works correctly even for <b>tau-t</b><tt>=0</tt>.
929 For NVT simulations the conserved energy quantity is written
930 to the energy and log file.</dd>
932 <dt><b>nsttcouple: (-1)</b></dt>
933 <dd>The frequency for coupling the temperature.
934 The default value of -1 sets <b>nsttcouple</b> equal to <b>nstlist</b>,
935 unless <b>nstlist</b>≤0, then a value of 10 is used.
936 For velocity Verlet integrators <b>nsttcouple</b> is set to 1.</dd>
938 <dt><b>nh-chain-length (10)</b></dt>
939 <dd>the number of chained Nose-Hoover thermostats for velocity Verlet integrators, the leap-frog <b>md</b> integrator only supports 1. Data for the NH chain variables is not printed to the .edr, but can be using the <tt>GMX_NOSEHOOVER_CHAINS</tt> environment variable</dd>
940 <dt><b>tc-grps:</b></dt>
941 <dd>groups to couple separately to temperature bath</dd>
942 <dt><b>tau-t: [ps]</b></dt>
943 <dd>time constant for coupling (one for each group in <b>tc-grps</b>),
944 -1 means no temperature coupling</dd>
945 <dt><b>ref-t: [K]</b></dt>
946 <dd>reference temperature for coupling (one for each group in <b>tc-grps</b>)</dd>
951 <h3>Pressure coupling<!--QuietIdx-->pressure coupling<!--EQuietIdx--></h3>
954 <dt><b>pcoupl:</b></dt>
957 <dd>No pressure coupling. This means a fixed box size.</dd>
958 <dt><b>berendsen</b></dt>
959 <dd>Exponential relaxation pressure coupling with time constant
960 <b>tau-p</b> [ps]. The box is scaled every timestep. It has been
961 argued that this does not yield a correct thermodynamic ensemble,
962 but it is the most efficient way to scale a box at the beginning
964 <dt><b>Parrinello-Rahman</b></dt>
965 <dd>Extended-ensemble pressure coupling where the box vectors are
966 subject to an equation of motion. The equation of motion for the atoms
967 is coupled to this. No instantaneous scaling takes place. As for
968 Nose-Hoover temperature coupling the time constant <b>tau-p</b> [ps]
969 is the period of pressure fluctuations at equilibrium. This is
970 probably a better method when you want to apply pressure scaling
971 during data collection, but beware that you can get very large
972 oscillations if you are starting from a different pressure. For
973 simulations where the exact fluctation of the NPT ensemble are
974 important, or if the pressure coupling time is very short it may not
975 be appropriate, as the previous time step pressure is used in some
976 steps of the GROMACS implementation for the current time step pressure.</dd>
979 <dd>Martyna-Tuckerman-Tobias-Klein implementation, only useable with <b>md-vv</b>
980 or <b>md-vv-avek</b>, very similar to Parrinello-Rahman.
981 As for Nose-Hoover temperature coupling the time constant <b>tau-p</b>
982 [ps] is the period of pressure fluctuations at equilibrium. This is
983 probably a better method when you want to apply pressure scaling
984 during data collection, but beware that you can get very large
985 oscillations if you are starting from a different pressure. Currently only supports isotropic scaling.</dd>
989 <dt><b>pcoupltype:</b></dt>
991 <dt><b>isotropic</b></dt>
992 <dd>Isotropic pressure coupling with time constant <b>tau-p</b> [ps].
993 The compressibility and reference pressure are set with
994 <b>compressibility</b> [bar<sup>-1</sup>] and <b>ref-p</b> [bar], one
995 value is needed.</dd>
996 <dt><b>semiisotropic</b></dt>
997 <dd>Pressure coupling which is isotropic in the <tt>x</tt> and <tt>y</tt> direction,
998 but different in the <tt>z</tt> direction.
999 This can be useful for membrane simulations.
1000 2 values are needed for <tt>x/y</tt> and <tt>z</tt> directions respectively.</dd>
1001 <dt><b>anisotropic</b></dt>
1002 <dd>Idem, but 6 values are needed for <tt>xx</tt>, <tt>yy</tt>, <tt>zz</tt>, <tt>xy/yx</tt>, <tt>xz/zx</tt> and <tt>yz/zy</tt>
1003 components, respectively.
1004 When the off-diagonal compressibilities are set to zero,
1005 a rectangular box will stay rectangular.
1006 Beware that anisotropic scaling can lead to extreme deformation
1007 of the simulation box.</dd>
1008 <dt><b>surface-tension</b></dt>
1009 <dd>Surface tension coupling for surfaces parallel to the xy-plane.
1010 Uses normal pressure coupling for the <tt>z</tt>-direction, while the surface tension
1011 is coupled to the <tt>x/y</tt> dimensions of the box.
1012 The first <b>ref-p</b> value is the reference surface tension times
1013 the number of surfaces [bar nm],
1014 the second value is the reference <tt>z</tt>-pressure [bar].
1015 The two <b>compressibility</b> [bar<sup>-1</sup>] values are the compressibility
1016 in the <tt>x/y</tt> and <tt>z</tt> direction respectively.
1017 The value for the <tt>z</tt>-compressibility should be reasonably accurate since it
1018 influences the convergence of the surface-tension, it can also be set to zero
1019 to have a box with constant height.</dd>
1022 <dt><b>nstpcouple: (-1)</b></dt>
1023 <dd>The frequency for coupling the pressure.
1024 The default value of -1 sets <b>nstpcouple</b> equal to <b>nstlist</b>,
1025 unless <b>nstlist</b> ≤0, then a value of 10 is used.
1026 For velocity Verlet integrators <b>nstpcouple</b> is set to 1.</dd>
1029 <dt><b>tau-p: (1) [ps]</b></dt>
1030 <dd>time constant for coupling</dd>
1031 <dt><b>compressibility: [bar<sup>-1</sup>]</b></dt>
1032 <dd>compressibility (NOTE: this is now really in bar<sup>-1</sup>)
1033 For water at 1 atm and 300 K the compressibility is 4.5e-5 [bar<sup>-1</sup>].</dd>
1034 <dt><b>ref-p: [bar]</b></dt>
1035 <dd>reference pressure for coupling</dd>
1036 <dt><b>refcoord-scaling:</b></dt>
1039 <dd>The reference coordinates for position restraints are not modified.
1040 Note that with this option the virial and pressure will depend on the absolute
1041 positions of the reference coordinates.</dd>
1043 <dd>The reference coordinates are scaled with the scaling matrix of the pressure coupling.</dd>
1045 <dd>Scale the center of mass of the reference coordinates with the scaling matrix of the pressure coupling. The vectors of each reference coordinate to the center of mass are not scaled. Only one COM is used, even when there are multiple molecules with position restraints. For calculating the COM of the reference coordinates in the starting configuration, periodic boundary conditions are not taken into account.
1052 <h3>Simulated annealing<!--QuietIdx-->simulated annealing<!--EQuietIdx--></h3>
1054 Simulated annealing is controlled separately for each temperature group in GROMACS. The reference temperature is a piecewise linear function, but you can use an arbitrary number of points for each group, and choose either a single sequence or a periodic behaviour for each group. The actual annealing is performed by dynamically changing the reference temperature used in the thermostat algorithm selected, so remember that the system will usually not instantaneously reach the reference temperature!
1056 <dt><b>annealing:</b></dt>
1057 <dd>Type of annealing for each temperature group</dd>
1058 <dd><dl compact></dd>
1060 <dd>No simulated annealing - just couple to reference temperature value.</dd>
1061 <dt><b>single</b></dt>
1062 <dd>A single sequence of annealing points. If your simulation is longer than the time of the last point, the temperature will be coupled to this constant value after the annealing sequence has reached the last time point.</dd>
1063 <dt><b>periodic</b></dt>
1064 <dd>The annealing will start over at the first reference point once the last reference time is reached. This is repeated until the simulation ends.
1068 <dt><b>annealing-npoints:</b></dt>
1069 <dd>A list with the number of annealing reference/control points used for
1070 each temperature group. Use 0 for groups that are not annealed. The number of entries should equal the number of temperature groups.</dd>
1072 <dt><b>annealing-time:</b></dt>
1073 <dd>List of times at the annealing reference/control points for each group. If you are using periodic annealing, the times will be used modulo the last value, i.e. if the values are 0, 5, 10, and 15, the coupling will restart at the 0ps value after 15ps, 30ps, 45ps, etc. The number of entries should equal the sum of the numbers given in <tt>annealing-npoints</tt>.</dd>
1075 <dt><b>annealing-temp:</b></dt>
1076 <dd>List of temperatures at the annealing reference/control points for each group. The number of entries should equal the sum of the numbers given in <tt>annealing-npoints</tt>.</dd>
1078 Confused? OK, let's use an example. Assume you have two temperature groups, set the group selections to <tt>annealing = single periodic</tt>, the number of points of each group to <tt>annealing-npoints = 3 4</tt>, the times to <tt>annealing-time = 0 3 6 0 2 4 6</tt> and finally temperatures to <tt>annealing-temp = 298 280 270 298 320 320 298</tt>.
1079 The first group will be coupled to 298K at 0ps, but the reference temperature will drop linearly to reach 280K at 3ps, and then linearly between 280K and 270K from 3ps to 6ps. After this is stays constant, at 270K. The second group is coupled to 298K at 0ps, it increases linearly to 320K at 2ps, where it stays constant until 4ps. Between 4ps and 6ps it decreases to 298K, and then it starts over with the same pattern again, i.e. rising linearly from 298K to 320K between 6ps and 8ps. Check the summary printed by <tt>grompp</tt> if you are unsure!
1084 <h3>Velocity generation</h3>
1087 <dt><b>gen-vel:</b></dt>
1090 <dd> Do not generate velocities. The velocities are set to zero
1091 when there are no velocities in the input structure file.</dd>
1093 <dd>Generate velocities in <tt>grompp</tt> according to a Maxwell distribution at
1094 temperature <b>gen-temp</b> [K], with random seed <b>gen-seed</b>.
1095 This is only meaningful with integrator <b><A HREF="#run">md</A></b>.</dd>
1097 <dt><b>gen-temp: (300) [K]</b></dt>
1098 <dd>temperature for Maxwell distribution</dd>
1099 <dt><b>gen-seed: (173529) [integer]</b></dt>
1100 <dd>used to initialize random generator for random velocities,
1101 when <b>gen-seed</b> is set to -1, the seed is calculated from
1102 the process ID number.
1110 <dt><b>constraints<!--QuietIdx-->constraint algorithms<!--EQuietIdx-->:</b></dt>
1112 <dt><b>none</b></dt>
1113 <dd>No constraints except for those defined explicitly in the topology,
1114 i.e. bonds are represented by a harmonic (or other) potential
1115 or a Morse potential (depending on the setting of <b>morse</b>)
1116 and angles by a harmonic (or other) potential.
1117 <dt><b>h-bonds</b></dt>
1118 <dd>Convert the bonds with H-atoms to constraints.</dd>
1119 <dt><b>all-bonds</b></dt>
1120 <dd>Convert all bonds to constraints.</dd>
1121 <dt><b>h-angles</b></dt>
1122 <dd>Convert all bonds and additionally the angles that involve H-atoms
1123 to bond-constraints.</dd>
1124 <dt><b>all-angles</b></dt>
1125 <dd>Convert all bonds and angles to bond-constraints.</dd>
1128 <dt><b>constraint-algorithm:</b></dt>
1130 <dt><b><!--Idx-->LINCS<!--EIdx--></b></dt>
1131 <dd>LINear Constraint Solver.
1132 With domain decomposition the parallel version P-LINCS is used.
1133 The accuracy in set with
1134 <b>lincs-order</b>, which sets the number of matrices in the expansion
1135 for the matrix inversion.
1136 After the matrix inversion correction the algorithm does
1137 an iterative correction to compensate for lengthening due to rotation.
1138 The number of such iterations can be controlled with
1139 <b>lincs-iter</b>. The root mean square relative constraint deviation
1140 is printed to the log file every <b>nstlog</b> steps.
1141 If a bond rotates more than <b>lincs-warnangle</b> [degrees] in one step,
1142 a warning will be printed both to the log file and to <TT>stderr</TT>.
1143 LINCS should not be used with coupled angle constraints.
1145 <dt><b><!--Idx-->SHAKE<!--EIdx--></b></dt>
1146 <dd>SHAKE is slightly slower and less stable than LINCS, but does work with
1148 The relative tolerance is set with <b>shake-tol</b>, 0.0001 is a good value
1149 for ``normal'' MD. SHAKE does not support constraints between atoms
1150 on different nodes, thus it can not be used with domain decompositon
1151 when inter charge-group constraints are present.
1152 SHAKE can not be used with energy minimization.
1155 <dt><b>continuation:</b></dt>
1156 <dd>This option was formerly known as <tt>unconstrained-start</tt>.</dd>
1159 <dd>apply constraints to the start configuration and reset shells</dd>
1161 <dd>do not apply constraints to the start configuration
1162 and do not reset shells, useful for exact coninuation and reruns</dd>
1166 <dt><b>shake-tol: (0.0001)</b></dt>
1167 <dd>relative tolerance for SHAKE</dd>
1168 <dt><b>lincs-order: (4)</b></dt>
1169 <dd>Highest order in the expansion of the constraint coupling matrix.
1170 When constraints form triangles, an additional expansion of the same
1171 order is applied on top of the normal expansion only for the couplings
1172 within such triangles.
1173 For ``normal'' MD simulations an order of 4 usually suffices, 6 is
1174 needed for large time-steps with virtual sites or BD.
1175 For accurate energy minimization an order of 8 or more might be required.
1176 With domain decomposition, the cell size is limited by the distance
1177 spanned by <b>lincs-order</b>+1 constraints. When one wants to scale
1178 further than this limit, one can decrease <b>lincs-order</b> and increase
1179 <b>lincs-iter</b>, since the accuracy does not deteriorate
1180 when (1+<b>lincs-iter</b>)*<b>lincs-order</b> remains constant.</dd>
1181 <dt><b>lincs-iter: (1)</b></dt>
1182 <dd>Number of iterations to correct for rotational lengthening in LINCS.
1183 For normal runs a single step is sufficient, but for NVE
1184 runs where you want to conserve energy accurately or for accurate
1185 energy minimization you might want to increase it to 2.
1186 <dt><b>lincs-warnangle: </b>(30) [degrees]</dt>
1187 <dd>maximum angle that a bond can rotate before LINCS will complain</dd>
1189 <dt><b>morse:</b></dt>
1192 <dd>bonds are represented by a harmonic potential</dd>
1194 <dd>bonds are represented by a Morse potential</dd>
1198 <A NAME="egexcl"><br>
1200 <h3>Energy group <!--Idx-->exclusions<!--EIdx--></h3>
1202 <dt><b>energygrp-excl: </b></dt>
1203 <dd>Pairs of energy groups for which all non-bonded interactions are
1204 excluded. An example: if you have two energy groups <tt>Protein</tt>
1205 and <tt>SOL</tt>, specifying
1207 <tt>energygrp-excl = Protein Protein SOL SOL</tt>
1209 would give only the non-bonded interactions between the protein and the
1210 solvent. This is especially useful for speeding up energy calculations with
1211 <tt>mdrun -rerun</tt> and for excluding interactions within frozen groups.</dd>
1214 <A NAME="walls"><br>
1216 <h3>Walls<!--QuietIdx-->walls<!--EQuietIdx--></h3>
1218 <dt><b>nwall: 0</b></dt>
1219 <dd>When set to <b>1</b> there is a wall at <tt>z=0</tt>, when set to <b>2</b>
1220 there is also a wall at <tt>z=z-box</tt>. Walls can only be used with <b>pbc=xy</b>.
1221 When set to <b>2</b> pressure coupling and Ewald summation can be used
1222 (it is usually best to use semiisotropic pressure coupling with
1223 the <tt>x/y</tt> compressibility set to 0, as otherwise the surface area will change).
1224 Walls interact wit the rest of the system through an optional <tt>wall-atomtype</tt>.
1225 Energy groups <tt>wall0</tt> and <tt>wall1</tt> (for <b>nwall=2</b>) are
1226 added automatically to monitor the interaction of energy groups
1228 The <A HREF="#run">center of mass motion removal</A> will be turned
1229 off in the <tt>z</tt>-direction.</dd>
1230 <dt><b>wall-atomtype:</b></dt>
1231 <dd>the atom type name in the force field for each wall.
1232 By (for example) defining a special wall atom type in the topology with its
1233 own combination rules, this allows for independent tuning of the interaction
1234 of each atomtype with the walls.</dd>
1235 <dt><b>wall-type:</b></dt>
1238 <dd>LJ integrated over the volume behind the wall: 9-3 potential</dd>
1239 <dt><b>10-4</b></dt>
1240 <dd>LJ integrated over the wall surface: 10-4 potential</dd>
1241 <dt><b>12-6</b></dt>
1242 <dd>direct LJ potential with the z distance from the wall</dd>
1243 <dt><b>table</b></dt><dd>user defined potentials indexed with the z distance from the wall, the tables are read analogously to
1244 the <b><A HREF="#table">energygrp-table</A></b> option,
1245 where the first name is for a ``normal'' energy group and the second name
1246 is <tt>wall0</tt> or <tt>wall1</tt>,
1247 only the dispersion and repulsion columns are used</dd>
1249 <dt><b>wall-r-linpot: -1 (nm)</b></dt>
1250 <dd>Below this distance from the wall the potential is continued
1251 linearly and thus the force is constant. Setting this option to
1252 a postive value is especially useful for equilibration when some atoms
1254 When the value is ≤0 (<0 for <b>wall-type=table</b>),
1255 a fatal error is generated when atoms are beyond a wall.
1257 <dt><b>wall-density: [nm<sup>-3</sup>/nm<sup>-2</sup>]</b></dt>
1258 <dd>the number density of the atoms for each wall for wall types
1259 <b>9-3</b> and <b>10-4</b>
1260 <dt><b>wall-ewald-zfac: 3</b></dt>
1261 <dd>The scaling factor for the third box vector for Ewald summation only,
1263 Ewald summation can only be used with <b>nwall=2</b>, where one
1264 should use <b><A HREF="#ewald">ewald-geometry</A><tt>=3dc</tt></b>.
1265 The empty layer in the box serves to decrease the unphysical Coulomb
1266 interaction between periodic images.
1271 <h3>COM <!--Idx-->pulling<!--EIdx--></h3>
1273 <dt><b>pull:</b></dt>
1276 <dd>No center of mass pulling.
1277 All the following pull options will be ignored
1278 (and if present in the <tt>.mdp</tt> file, they unfortunately generate warnings)</dd>
1279 <dt><b>umbrella</b></dt>
1280 <dd>Center of mass pulling using an umbrella potential
1281 between the reference group and one or more groups.</dd>
1282 <dt><b>constraint</b></dt>
1283 <dd>Center of mass pulling using a constraint
1284 between the reference group and one or more groups.
1285 The setup is identical to the option <b>umbrella</b>, except for the fact
1286 that a rigid constraint is applied instead of a harmonic potential.</dd>
1287 <dt><b>constant-force</b></dt>
1288 <dd>Center of mass pulling using a linear potential and therefore
1289 a constant force. For this option there is no reference position
1290 and therefore the parameters <b>pull-init</b> and <b>pull-rate</b>
1293 <dt><b>pull-geometry:</b></dt>
1295 <dt><b>distance</b></dt>
1296 <dd>Pull along the vector connecting the two groups.
1297 Components can be selected with <b>pull-dim</b>.</dd>
1298 <dt><b>direction</b></dt>
1299 <dd>Pull in the direction of <b>pull-vec</b>.</dd>
1300 <dt><b>direction-periodic</b></dt>
1301 <dd>As <b>direction</b>, but allows the distance to be larger than
1302 half the box size. With this geometry the box should not be dynamic
1303 (e.g. no pressure scaling) in the pull dimensions and the pull force
1304 is not added to virial.</dd>
1305 <dt><b>cylinder</b></dt>
1306 <dd>Designed for pulling with respect to a layer where the reference COM
1307 is given by a local cylindrical part of the reference group.
1308 The pulling is in the direction of <b>pull-vec</b>.
1309 From the reference group a cylinder is selected around the axis going
1310 through the pull group with direction <b>pull-vec</b> using two radii.
1311 The radius <b>pull-r1</b> gives the radius within which all
1312 the relative weights are one, between <b>pull-r1</b> and
1313 <b>pull-r0</b> the weights are switched to zero. Mass weighting is also used.
1314 Note that the radii should be smaller than half the box size.
1315 For tilted cylinders they should be even smaller than half the box size
1316 since the distance of an atom in the reference group
1317 from the COM of the pull group has both a radial and an axial component.
1318 <dt><b>position</b></dt>
1319 <dd>Pull to the position of the reference group plus
1320 <b>pull-init</b> + time*<b>pull-rate</b>*<b>pull-vec</b>.</dd>
1322 <dt><b>pull-dim: (Y Y Y)</b></dt>
1323 <dd>the distance components to be used with geometry <b>distance</b>
1324 and <b>position</b>, and also sets which components are printed
1325 to the output files</dd>
1326 <dt><b>pull-r1: (1) [nm]</b></dt>
1327 <dd>the inner radius of the cylinder for geometry <b>cylinder</b></dd>
1328 <dt><b>pull-r0: (1) [nm]</b></dt>
1329 <dd>the outer radius of the cylinder for geometry <b>cylinder</b></dd>
1330 <dt><b>pull-constr-tol: (1e-6)</b></dt>
1331 <dd>the relative constraint tolerance for constraint pulling</dd>
1332 <dt><b>pull-start:</b></dt>
1335 <dd>do not modify <b>pull-init</b>
1337 <dd>add the COM distance of the starting conformation to <b>pull-init</b></dd>
1339 <dt><b>pull-nstxout: (10)</b></dt>
1340 <dd>frequency for writing out the COMs of all the pull group</dd>
1341 <dt><b>pull-nstfout: (1)</b></dt>
1342 <dd>frequency for writing out the force of all the pulled group</dd>
1343 <dt><b>pull-ngroups: (1)</b></dt>
1344 <dd>The number of pull groups, not including the reference group.
1345 If there is only one group, there is no difference in treatment
1346 of the reference and pulled group (except with the cylinder geometry).
1347 Below only the pull options for the reference group (ending on 0)
1348 and the first group (ending on 1) are given,
1349 further groups work analogously, but with the number 1 replaced
1350 by the group number.</dd>
1351 <dt><b>pull-group0: </b></dt>
1352 <dd>The name of the reference group. When this is empty an absolute reference
1353 of (0,0,0) is used. With an absolute reference the system is no longer
1354 translation invariant and one should think about what to do with
1355 the <A HREF="#run">center of mass motion</A>.</dd>
1356 <dt><b>pull-weights0: </b></dt>
1357 <dd>see <b>pull-weights1</b></dd>
1358 <dt><b>pull-pbcatom0: (0)</b></dt>
1359 <dd>see <b>pull-pbcatom1</b></dd>
1360 <dt><b>pull-group1: </b></dt>
1361 <dd>The name of the pull group.</dd>
1362 <dt><b>pull-weights1: </b></dt>
1363 <dd>Optional relative weights which are multiplied with the masses of the atoms
1364 to give the total weight for the COM. The number should be 0, meaning all 1,
1365 or the number of atoms in the pull group.</dd>
1366 <dt><b>pull-pbcatom1: (0)</b></dt>
1367 <dd>The reference atom for the treatment of periodic boundary conditions
1369 (this has no effect on the treatment of the pbc between groups).
1370 This option is only important when the diameter of the pull group
1371 is larger than half the shortest box vector.
1372 For determining the COM, all atoms in the group are put at their periodic image
1373 which is closest to <b>pull-pbcatom1</b>.
1374 A value of 0 means that the middle atom (number wise) is used.
1375 This parameter is not used with geometry <b>cylinder</b>.
1376 A value of -1 turns on cosine weighting, which is useful for a group
1377 of molecules in a periodic system, e.g. a water slab (see Engin et al.
1378 J. Chem. Phys. B 2010).</dd>
1379 <dt><b>pull-vec1: (0.0 0.0 0.0)</b></dt>
1380 <dd>The pull direction. <tt>grompp</tt> normalizes the vector.</dd>
1381 <dt><b>pull-init1: (0.0) / (0.0 0.0 0.0) [nm]</b></dt>
1382 <dd>The reference distance at t=0. This is a single value,
1383 except for geometry <b>position</b> which uses a vector.</dd>
1384 <dt><b>pull-rate1: (0) [nm/ps]</b></dt>
1385 <dd>The rate of change of the reference position.</dd>
1386 <dt><b>pull-k1: (0) [kJ mol<sup>-1</sup> nm<sup>-2</sup>] / [kJ mol<sup>-1</sup> nm<sup>-1</sup>]</b></dt>
1387 <dd>The force constant. For umbrella pulling this is the harmonic force
1388 constant in [kJ mol<sup>-1</sup> nm<sup>-2</sup>]. For constant force pulling
1389 this is the force constant of the linear potential, and thus minus (!)
1390 the constant force in [kJ mol<sup>-1</sup> nm<sup>-1</sup>].</dd>
1391 <dt><b>pull-kB1: (pull-k1) [kJ mol<sup>-1</sup> nm<sup>-2</sup>] / [kJ mol<sup>-1</sup> nm<sup>-1</sup>]</b></dt>
1392 <dd>As <b>pull-k1</b>, but for state B. This is only used when
1393 <A HREF="#free"><b>free-energy</b></A> is turned on.
1394 The force constant is then (1 - lambda)*<b>pull-k1</b> + lambda*<b>pull-kB1</b>.
1399 <h3><!--Idx-->NMR refinement<!--EIdx--></h3>
1401 <dt><b>disre:</b></dt>
1404 <dd>ignore <!--Idx-->distance restraint<!--EIdx--> information in topology file</dd>
1405 <dt><b>simple</b></dt>
1406 <dd>simple (per-molecule) distance restraints.
1407 <dt><b>ensemble</b></dt>
1408 <dd>distance restraints over an ensemble of molecules in one
1409 simulation box. Normally, one would perform ensemble averaging over
1410 multiple subsystems, each in a separate box, using <tt>mdrun -multi</tt>;s
1411 upply <tt>topol0.tpr</tt>, <tt>topol1.tpr</tt>, ... with different
1412 coordinates and/or velocities.
1413 The environment variable <tt>GMX_DISRE_ENSEMBLE_SIZE</tt> sets the number
1414 of systems within each ensemble (usually equal to the <tt>mdrun -multi</tt> value).</dd>
1417 <dt><b>disre-weighting:</b></dt>
1419 <dt><b>equal</b> (default)</dt>
1420 <dd>divide the restraint force equally over all atom pairs in the restraint</dd>
1421 <dt><b>conservative</b></dt>
1422 <dd>the forces are the derivative of the restraint potential,
1423 this results in an r<sup>-7</sup> weighting of the atom pairs.
1424 The forces are conservative when <tt>disre-tau</tt> is zero.</dd>
1426 <dt><b>disre-mixed:</b></dt>
1429 <dd>the violation used in the calculation of the restraint force is the
1430 time-averaged violation </dd>
1432 <dd>the violation used in the calculation of the restraint force is the
1433 square root of the product of the time-averaged violation and the instantaneous violation</dd>
1436 <dt><b>disre-fc: (1000) [kJ mol<sup>-1</sup> nm<sup>-2</sup>]</b></dt>
1437 <dd>force constant for distance restraints, which is multiplied by a
1438 (possibly) different factor for each restraint given in the <tt>fac</tt>
1439 column of the interaction in the topology file.</dd>
1441 <dt><b>disre-tau: (0) [ps]</b></dt>
1442 <dd>time constant for distance restraints running average. A value of zero turns off time averaging.</dd>
1444 <dt><b>nstdisreout: (100) [steps]</b></dt>
1445 <dd>period between steps when the running time-averaged and instantaneous distances
1446 of all atom pairs involved in restraints are written to the energy file
1447 (can make the energy file very large)</dd>
1450 <dt><b>orire:</b></dt>
1453 <dd>ignore <!--Idx-->orientation restraint<!--EIdx--> information in topology file</dd>
1455 <dd>use orientation restraints, ensemble averaging can be performed
1456 with <tt>mdrun -multi</tt></dd>
1458 <dt><b>orire-fc: (0) [kJ mol]</b></dt>
1459 <dd>force constant for orientation restraints, which is multiplied by a
1460 (possibly) different weight factor for each restraint, can be set to zero to
1461 obtain the orientations from a free simulation</dd>
1462 <dt><b>orire-tau: (0) [ps]</b></dt>
1463 <dd>time constant for orientation restraints running average. A value of zero turns off time averaging.</dd>
1464 <dt><b>orire-fitgrp: </b></dt>
1465 <dd>fit group for orientation restraining. This group of atoms is used
1466 to determine the rotation <b>R</b> of the system with respect to the
1467 reference orientation. The reference orientation is the starting
1468 conformation of the first subsystem. For a protein, backbone is a reasonable
1470 <dt><b>nstorireout: (100) [steps]</b></dt>
1471 <dd>period between steps when the running time-averaged and instantaneous orientations
1472 for all restraints, and the molecular order tensor are written to the energy file
1473 (can make the energy file very large)</dd>
1478 <h3>Free energy calculations<!--QuietIdx-->free energy calculations<!--EQuietIdx--></h3>
1481 <dt><b>free-energy:</b></dt>
1484 <dd>Only use topology A.</dd>
1486 <dd>Interpolate between topology A (lambda=0) to topology B (lambda=1)
1487 and write the derivative of the Hamiltonian with respect to lambda (as specified with <b>dhdl-derivatives</b>), or the Hamiltonian differences with respect to other lambda values (as specified with <b>foreign-lambda</b>) to
1488 the energy file and/or to <tt>dhdl.xvg</tt>, where they can be processed by, for example <tt>g_bar</tt>.
1489 The potentials, bond-lengths and angles are interpolated linearly as
1490 described in the manual. When <b>sc-alpha</b> is larger than zero, soft-core
1491 potentials are used for the LJ and Coulomb interactions.</dd>
1492 <dt><b>expanded</b></dt>
1493 <dd> Turns on expanded ensemble simulation, where the alchemical state becomes a dynamic variable, allowing jumping between different Hamiltonians. See the <A HREF="#expanded">expanded ensemble options</A> for controlling how expanded ensemble simulations are performed. The different Hamiltonians used in expanded ensemble simulations are defined by the other free energy options.</dd>
1495 <dt><b>init-lambda: (-1)</b></dt>
1496 <dd>starting value for lambda (float). Generally, this should only be used with slow growth (i.e. nonzero <b>delta-lambda</b>). In other cases, <b>init-lambda-state</b> should be specified instead. Must be greater than or equal to 0.</dd>
1497 <dt><b>delta-lambda: (0)</b></dt>
1498 <dd>increment per time step for lambda</dd>
1499 <dt><b>init-lambda-state: (-1)</b></dt>
1500 <dd>starting value for the lambda state (integer). Specifies which columm of the lambda vector (<b>coul-lambdas</b>, <b>vdw-lambdas</b>, <b>bonded-lambdas</b>, <b>restraint-lambdas</b>, <b>mass-lambdas</b>, <b>temperature-lambdas</b>, <b>fep-lambdas</b>) should be used. This is a zero-based index: <b>init-lambda-state</b> 0 means the first column, and so on.</dd>
1501 <dt><b>fep-lambdas: ()</b></dt>
1502 <dd>Zero, one or more lambda values for which Delta H values will
1503 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps.
1504 Values must be between 0 and 1.
1505 Free energy differences between different lambda values can then
1506 be determined with <tt>g_bar</tt>. <b>fep-lambdas</b> is different from the other -lambdas keywords because
1507 all components of the lambda vector that are not specified will use <b>fep-lambdas</b> (including restraint-lambdas and therefore the pull code restraints).</dd>
1508 <dt><b>coul-lambdas: ()</b></dt>
1509 <dd>Zero, one or more lambda values for which Delta H values will
1510 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps. Values must be between 0 and 1.
1511 Only the electrostatic interactions are controlled with this component of the lambda vector (and only if the lambda=0 and lambda=1 states have differing electrostatic interactions).</dd>
1512 <dt><b>vdw-lambdas: ()</b></dt>
1513 <dd>Zero, one or more lambda values for which Delta H values will
1514 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps. Values must be between 0 and 1.
1515 Only the van der Waals interactions are controlled with this component of the lambda vector.</dd>
1516 <dt><b>bonded-lambdas: ()</b></dt>
1517 <dd>Zero, one or more lambda values for which Delta H values will
1518 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps. Values must be between 0 and 1.
1519 Only the bonded interactions are controlled with this component of the lambda vector.</dd>
1520 <dt><b>restraint-lambdas: ()</b></dt>
1521 <dd>Zero, one or more lambda values for which Delta H values will
1522 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps. Values must be between 0 and 1.
1523 Only the restraint interactions: dihedral restraints, and the pull code restraints are controlled with this component of the lambda vector. </dd>
1524 <dt><b>mass-lambdas: ()</b></dt>
1525 <dd>Zero, one or more lambda values for which Delta H values will
1526 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps. Values must be between 0 and 1.
1527 Only the particle masses are controlled with this component of the lambda vector.</dd>
1528 <dt><b>temperature-lambdas: ()</b></dt>
1529 <dd>Zero, one or more lambda values for which Delta H values will
1530 be determined and written to dhdl.xvg every <b>nstdhdl</b> steps. Values must be between 0 and 1.
1531 Only the temperatures controlled with this component of the lambda vector.
1532 Note that these lambdas should not be used for replica exchange, only for simulated tempering.</dd>
1533 <dt><b>calc-lambda-neighbors (1)</b></dt>
1534 <dd>Controls the number of lambda values for which Delta H values will be
1535 calculated and written out, if <b>init-lambda-state</b> has been set. A
1536 positive value will limit the number of lambda points calculated to only the
1537 nth neighbors of <b>init-lambda-state</b>: for example, if
1538 <b>init-lambda-state</b> is 5 and this parameter has a value of 2, energies for
1539 lambda points 3-7 will be calculated and writen out. A value of -1 means all
1540 lambda points will be written out. For normal BAR such as with g_bar, a value
1541 of 1 is sufficient, while for MBAR -1 should be used.</dd>
1542 <dt><b>sc-alpha: (0)</b></dt>
1543 <dd>the soft-core alpha parameter, a value of 0 results in linear interpolation of the LJ and Coulomb interactions</dd>
1544 <dt><b>sc-r-power: (6)</b></dt>
1545 <dd>the power of the radial term in the soft-core equation. Possible values are 6 and 48. 6 is more standard, and is the default. When 48 is used, then sc-alpha should generally be much lower (between 0.001 and 0.003).</dd>
1546 <dt><b>sc-coul: (no)</b></dt>
1547 <dd>Whether to apply the soft core free energy interaction transformation to the Columbic interaction of a molecule. Default is no, as it is generally
1548 more efficient to turn off the Coulomic interactions linearly before turning off the van der Waals interactions.</dd>
1549 <dt><b>sc-power: (0)</b></dt>
1550 <dd>the power for lambda in the soft-core function, only the values 1 and 2 are supported</dd>
1551 <dt><b>sc-sigma: (0.3) [nm]</b></dt>
1552 <dd>the soft-core sigma for particles which have a C6 or C12 parameter equal
1553 to zero or a sigma smaller than <b>sc-sigma</b></dd>
1554 <dt><b>couple-moltype:</b></dt>
1555 <dd>Here one can supply a molecule type (as defined in the topology)
1556 for calculating solvation or coupling free energies.
1557 There is a special option <b>system</b> that couples all molecule types
1558 in the system. This can be useful for equilibrating a system
1559 starting from (nearly) random coordinates.
1560 <b>free-energy</b> has to be turned on.
1561 The Van der Waals interactions and/or charges in this molecule type can be
1562 turned on or off between lambda=0 and lambda=1, depending on the settings
1563 of <b>couple-lambda0</b> and <b>couple-lambda1</b>. If you want to decouple
1564 one of several copies of a molecule, you need to copy and rename
1565 the molecule definition in the topology.</dd>
1566 <dt><b>couple-lambda0:</b></dt>
1568 <dt><b>vdw-q</b></dt>
1569 <dd>all interactions are on at lambda=0
1571 <dd>the charges are zero (no Coulomb interactions) at lambda=0
1573 <dd>the Van der Waals interactions are turned at lambda=0; soft-core interactions will be required to avoid singularities
1574 <dt><b>none</b></dt>
1575 <dd>the Van der Waals interactions are turned off and the charges are zero at lambda=0; soft-core interactions will be required to avoid singularities.
1577 <dt><b>couple-lambda1:</b></dt>
1578 <dd> analogous to <b>couple-lambda1</b>, but for lambda=1
1579 <dt><b>couple-intramol:</b></dt>
1582 <dd>All intra-molecular non-bonded interactions for moleculetype <b>couple-moltype</b> are replaced by exclusions and explicit pair interactions. In this manner the decoupled state of the molecule corresponds to the proper vacuum state without periodicity effects.
1584 <dd>The intra-molecular Van der Waals and Coulomb interactions are also turned on/off. This can be useful for partitioning free-energies of relatively large molecules, where the intra-molecular non-bonded interactions might lead to kinetically trapped vacuum conformations. The 1-4 pair interactions are not turned off.
1586 <dt><b>nstdhdl: (100)</b></dt>
1587 <dd>the frequency for writing dH/dlambda and possibly Delta H to dhdl.xvg,
1588 0 means no ouput, should be a multiple of <b>nstcalcenergy</b></dd>.</dd>
1589 <dt><b>dhdl-derivatives: (yes)</b></dt>
1590 <dd>If yes (the default), the derivatives of the Hamiltonian with respect to lambda at each <b>nstdhdl</b> step are written out. These values are needed for interpolation of linear energy differences with <tt>g_bar</tt> (although the same can also be achieved with the right <b>foreign lambda</b> setting, that may not be as flexible), or with thermodynamic integration</dd>
1591 <dt><b>dhdl-print-energy: (no)</b></dt>
1592 <dd> Include the total energy in the dhdl file. This information is needed for later analysis if the states of interest in the free e energy calculation are at different temperatures. If all are at the same temperature, this information is not needed.</dd>
1593 <dt><b>separate-dhdl-file: (yes)</b></dt>
1596 <dd>the free energy values that are calculated (as specified with the <b>foreign-lambda</b> and <b>dhdl-derivatives</b> settings) are written out to a separate file, with the default name <tt>dhdl.xvg</tt>. This file can be used directly with <tt>g_bar</tt>.</dd>
1598 <dd>The free energy values are written out to the energy output file (<tt>ener.edr</tt>, in accumulated blocks at every <b>nstenergy</b> steps), where they can be extracted with <tt>g_energy</tt> or used directly with <tt>g_bar</tt>.</dd>
1600 <dt><b>dh-hist-size: (0)</b></dt>
1601 <dd>If nonzero, specifies the size of the histogram into which the Delta H values (specified with <b>foreign-lambda</b>) and the derivative dH/dl values are binned, and written to ener.edr. This can be used to save disk space while calculating free energy differences. One histogram gets written for each <b>foreign lambda</b> and two for the dH/dl, at every <b>nstenergy</b> step. Be aware that incorrect histogram settings (too small size or too wide bins) can introduce errors. Do not use histograms unless you're certain you need it.</dd>
1602 <dt><b>dh-hist-spacing (0.1)</b></dt>
1603 <dd>Specifies the bin width of the histograms, in energy units. Used in conjunction with <b>dh-hist-size</b>. This size limits the accuracy with which free energies can be calculated. Do not use histograms unless you're certain you need it.</dd>
1605 <A NAME="expanded"><br>
1607 <h3><!--Idx-->Expanded Ensemble calculations<!--EIdx--></h3>
1610 <dt><b>nstexpanded</b></dt> <dd>The number of integration steps beween attempted moves changing the system Hamiltonian in expanded ensemble simulations. Must be a multiple of <b>nstcalcenergy</b>, but can be greater or less than <b>nstdhdl</b>.</dd>
1611 <dt><b>lmc-stats:</b></dt>
1614 <dd>No Monte Carlo in state space is performed.</dd>
1615 <dt><b>metropolis-transition</b></dt>
1616 <dd> Uses the Metropolis weights to update the expanded ensemble weight of each state.
1617 Min{1,exp(-(beta_new u_new - beta_old u_old)}</dd>
1618 <dt><b>barker-transition</b></dt>
1619 <dd> Uses the Barker transition critera to update the expanded ensemble weight of each state i, defined by
1620 exp(-beta_new u_new)/[exp(-beta_new u_new)+exp(-beta_old u_old)</dd>
1621 <dt><b>wang-landau</b></dt>
1622 <dd>Uses the Wang-Landau algorithm (in state space, not energy space) to update the expanded ensemble weights.</dd>
1623 <dt><b>min-variance</b></dt>
1624 <dd>Uses the minimum variance updating method of Escobedo et al. to update the expanded ensemble weights. Weights
1625 will not be the free energies, but will rather emphasize states that need more sampling to give even uncertainty.</dd>
1627 <dt><b>lmc-mc-move:</b></dt>
1630 <dd>No Monte Carlo in state space is performed.</dd>
1631 <dt><b>metropolis-transition</b></dt>
1632 <dd> Randomly chooses a new state up or down, then uses the Metropolis critera to decide whether to accept or reject:
1633 Min{1,exp(-(beta_new u_new - beta_old u_old)}</dd>
1634 <dt><b>barker-transition</b></dt>
1635 <dd> Randomly chooses a new state up or down, then uses the Barker transition critera to decide whether to accept or reject: exp(-beta_new u_new)/[exp(-beta_new u_new)+exp(-beta_old u_old)]</dd>
1636 <dt><b>gibbs</b></dt>
1637 <dd> Uses the conditional weights of the state given the coordinate (exp(-beta_i u_i) / sum_k exp(beta_i u_i) to
1638 decide which state to move to.</dd>
1639 <dt><b>metropolized-gibbs</b></dt>
1641 <dd> Uses the conditional weights of the state given the coordinate (exp(-beta_i u_i) / sum_k exp(beta_i u_i) to
1642 decide which state to move to, EXCLUDING the current state, then uses a rejection step to ensure detailed
1643 balance. Always more efficient that Gibbs, though only marginally so in many situations, such as when only the nearest neighbors have decent phase space overlap.</dd>
1645 <dt><b>lmc-seed:</b></dt>
1646 <dd> random seed to use for Monte Carlo moves in state space. If not specified, <b>ld-seed</b> is used instead.</dd>
1647 <dt><b>mc-temperature:</b></dt>
1648 <dd> Temperature used for acceptance/rejection for Monte Carlo moves. If not specified, the temperature of the
1649 simulation specified in the first group of <b>ref_t</b> is used.</dd>
1650 <dt><b>wl-ratio: (0.8)</b></dt>
1651 <dd>The cutoff for the histogram of state occupancies to be reset, and the free energy incrementor to be reset as delta -> delta*wl-scale. If we define the Nratio = (number of samples at each histogram) / (average number of samples at each histogram). <b>wl-ratio</b> of 0.8 means that means that the histogram is only considered flat if all Nratio > 0.8 AND simultaneously all 1/Nratio > 0.8.</dd>
1652 <dt><b>wl-scale: (0.8)</b></dt>
1653 <dd> Each time the histogram is considered flat, then the current value of the Wang-Landau incrementor for the free energies is multiplied by <b>wl-scale</b>. Value must be between 0 and 1.</dd>
1654 <dt><b>init-wl-delta: (1.0)</b></dt>
1655 <dd>The initial value of the Wang-Landau incrementor in kT. Some value near 1 kT is usually most efficient, though sometimes a value of 2-3 in units of kT works better if the free energy differences are large.</dd>
1656 <dt><b>wl-oneovert: (no)</b></dt>
1657 <dd>Set Wang-Landau incrementor to scale with 1/(simulation time) in the large sample limit. There is significant evidence that the standard Wang-Landau algorithms in state space presented here result in free energies getting 'burned in' to incorrect values that depend on the initial state. when <b>wl-oneovert</b> is true, then when the incrementor becomes less than 1/N, where N is the mumber of samples collected (and thus proportional to the data collection time, hence '1 over t'), then the Wang-Lambda incrementor is set to 1/N, decreasing every step. Once this occurs, <b>wl-ratio</b> is ignored, but the weights will still stop updating when the equilibration criteria set in <b>lmc-weights-equil</b> is achieved.</dd>
1658 <dt><b>lmc-repeats: (1)</b></dt>
1659 <dd>Controls the number of times that each Monte Carlo swap type is performed each iteration. In the limit of large numbers of Monte Carlo repeats, then all methods converge to Gibbs sampling. The value will generally not need to be different from 1.</dd>
1660 <dt><b>lmc-gibbsdelta: (-1)</b></dt>
1661 <dd> Limit Gibbs sampling to selected numbers of neighboring states. For Gibbs sampling, it is sometimes inefficient to perform Gibbs sampling over all of the states that are defined. A positive value of <b>lmc-gibbsdelta</b> means that only states plus or minus <b>lmc-gibbsdelta</b> are considered in exchanges up and down. A value of -1 means that all states are considered. For less than 100 states, it is probably not that expensive to include all states.</dd>
1662 <dt><b>lmc-forced-nstart: (0)</b></dt>
1663 <dd> Force initial state space sampling to generate weights. In order to come up with reasonable initial weights, this setting allows the simulation to drive from the initial to the final lambda state, with <b>lmc-forced-nstart</b> steps at each state before moving on to the next lambda state. If <b>lmc-forced-nstart</b> is sufficiently long (thousands of steps, perhaps), then the weights will be close to correct. However, in most cases, it is probably better to simply run the standard weight equilibration algorithms.
1664 <dt><b>nst-transition-matrix: (-1)</b></dt>
1665 <dd>Frequency of outputting the expanded ensemble transition matrix. A negative number means it will only be printed at the end of the simulation.<dd>
1666 <dt><b>symmetrized-transition-matrix: (no) </b></dt>
1667 <dd>Whether to symmetrize the empirical transition matrix. In the infinite limit the matrix will be symmetric, but will diverge with statistical noise for short timescales. Forced symmetrization, by using the matrix T_sym = 1/2 (T + transpose(T)), removes problems like the existence of (small magnitude) negative eigenvalues.</dd>
1668 <dt><b>mininum-var-min: (100)</b></dt>
1669 <dd> The <b>min-variance</b> strategy (option of <b>lmc-stats</b> is only valid for larger number of samples, and can get stuck if too few samples are used at each state. <b>mininum-var-min</b> is the minimum number of samples that each state that are allowed before the <b>min-variance</b> strategy is activated if selected.</dd>
1670 <dt><b>init-lambda-weights: </b></dt>
1671 <dd>The initial weights (free energies) used for the expanded ensemble states. Default is a vector of zero weights. format is similar to the lambda vector settings in <b>fep-lambdas</b>, except the weights can be any floating point number. Units are kT. Its length must match the lambda vector lengths.</dd>
1672 <dt><b>lmc-weights-equil: (no)</b></dt>
1675 <dd>Expanded ensemble weights continue to be updated throughout the simulation.</dd>
1677 <dd>The input expanded ensemble weights are treated as equilibrated, and are not updated throughout the simulation.</dd>
1678 <dt><b>wl-delta</b></dt>
1679 <dd>Expanded ensemble weight updating is stopped when the Wang-Landau incrementor falls below the value specified by <b>weight-equil-wl-delta</b>.</dd>
1680 <dt><b>number-all-lambda</b></dt>
1681 <dd>Expanded ensemble weight updating is stopped when the number of samples at all of the lambda states is greater than the value specified by <b>weight-equil-number-all-lambda</b>.</dd>
1682 <dt><b>number-steps</b></dt>
1683 <dd>Expanded ensemble weight updating is stopped when the number of steps is greater than the level specified by <b>weight-equil-number-steps</b>.</dd>
1684 <dt><b>number-samples</b></dt>
1685 <dd>Expanded ensemble weight updating is stopped when the number of total samples across all lambda states is greater than the level specified by <b>weight-equil-number-samples</b>.</dd>
1686 <dt><b>count-ratio</b></dt>
1687 <dd>Expanded ensemble weight updating is stopped when the ratio of samples at the least sampled lambda state and most sampled lambda state greater than the value specified by <b>weight-equil-count-ratio</b>.</dd>
1689 <dt><b>simulated-tempering: (no)</b></dt>
1690 <dd>Turn simulated tempering on or off. Simulated tempering is implemented as expanded ensemble sampling with different temperatures instead of different Hamiltonians.</dd>
1691 <dt><b>sim-temp-low: (300)</b></dt>
1692 <dd>Low temperature for simulated tempering.</dd>
1693 <dt><b>sim-temp-high: (300)</b></dt>
1694 <dd>High temperature for simulated tempering.</dd>
1695 <dt><b>simulated-tempering-scaling: (linear)</b></dt>
1696 <dd>Controls the way that the temperatures at intermediate lambdas are calculated from the <b>temperature-lambda</b> part of the lambda vector.</dd>
1698 <dt><b>linear</b></dt>
1699 <dd>Linearly interpolates the temperatures using the values of <b>temperature-lambda</b>,i.e. if <b>sim-temp-low</b>=300, <b>sim-temp-high</b>=400, then lambda=0.5 correspond to a temperature of 350. A nonlinear set of temperatures can always be implemented with uneven spacing in lambda.</dd>
1700 <dt><b>geometric</b></dt>
1701 <dd> Interpolates temperatures geometrically between <b>sim-temp-low</b> and <b>sim-temp-high</b>. The i:th state has temperature <b>sim-temp-low</b> * (<b>sim-temp-high</b>/<b>sim-temp-low</b>) raised to the power of (i/(ntemps-1)). This should give roughly equal exchange for constant heat capacity, though of course things simulations that involve protein folding have very high heat capacity peaks.</dd>
1702 <dt><b>exponential</b></dt>
1703 <dd> Interpolates temperatures exponentially between <b>sim-temp-low</b> and <b>sim-temp-high</b>. The ith state has temperature
1704 <b>sim-temp-low</b> + (<b>sim-temp-high</b>-<b>sim-temp-low</b>)*((exp(<b>temperature-lambdas</b>[i])-1)/(exp(1.0)-1)).</dd>
1710 <h3>Non-equilibrium MD<!--QuietIdx-->non-equilibrium MD<!--EQuietIdx--></h3>
1713 <dt><b>acc-grps: </b></dt>
1714 <dd>groups for constant acceleration (e.g.: <tt>Protein Sol</tt>)
1715 all atoms in groups Protein and Sol will experience constant acceleration
1716 as specified in the <b>accelerate</b> line</dd>
1717 <dt><b>accelerate: (0) [nm ps<sup>-2</sup>]</b></dt>
1718 <dd>acceleration for <b>acc-grps</b>; x, y and z for each group
1719 (e.g. <tt>0.1 0.0 0.0 -0.1 0.0 0.0</tt> means that first group has constant
1720 acceleration of 0.1 nm ps<sup>-2</sup> in X direction, second group the
1722 <dt><b>freezegrps: </b></dt>
1723 <dd>Groups that are to be frozen (i.e. their X, Y, and/or Z position will
1724 not be updated; e.g. <tt>Lipid SOL</tt>). <b>freezedim</b> specifies for
1725 which dimension the freezing applies.
1726 To avoid spurious contibrutions to the virial and pressure due to large
1727 forces between completely frozen atoms you need to use
1728 <A HREF="#egexcl">energy group exclusions</A>, this also saves computing time.
1729 Note that coordinates of frozen atoms are not scaled by pressure-coupling
1731 <dt><b>freezedim: </b></dt>
1732 <dd>dimensions for which groups in <b>freezegrps</b> should be frozen,
1733 specify <tt>Y</tt> or <tt>N</tt> for X, Y and Z and for each group
1734 (e.g. <tt>Y Y N N N N</tt> means that particles in the first group
1735 can move only in Z direction. The particles in the second group can
1736 move in any direction).</dd>
1737 <dt><b>cos-acceleration: (0) [nm ps<sup>-2</sup>]</b></dt>
1738 <dd>the amplitude of the acceleration profile for calculating the
1739 <!--Idx-->viscosity<!--EIdx-->.
1740 The acceleration is in the X-direction and the magnitude is
1741 <b>cos-acceleration</b> cos(2 pi z/boxheight).
1742 Two terms are added to the energy file:
1743 the amplitude of the velocity profile and 1/viscosity.</dd>
1744 <dt><b><!--Idx-->deform<!--EIdx-->: (0 0 0 0 0 0) [nm ps<sup>-1</sup>]</b></dt>
1745 <dd>The velocities of deformation for the box elements:
1746 a(x) b(y) c(z) b(x) c(x) c(y). Each step the box elements
1747 for which <b>deform</b> is non-zero are calculated as:
1748 box(ts)+(t-ts)*deform, off-diagonal elements are corrected
1749 for periodicity. The coordinates are transformed accordingly.
1750 Frozen degrees of freedom are (purposely) also transformed.
1751 The time ts is set to t at the first step and at steps at which
1752 x and v are written to trajectory to ensure exact restarts.
1753 Deformation can be used together with semiisotropic or anisotropic
1754 pressure coupling when the appropriate compressibilities are set to zero.
1755 The diagonal elements can be used to <!--Idx-->strain<!--EIdx--> a solid.
1756 The off-diagonal elements can be used to <!--Idx-->shear<!--EIdx--> a solid
1762 <h3>Electric fields<!--QuietIdx-->electric field<!--EQuietIdx--></h3>
1765 <dt><b>E-x ; E-y ; E-z:</b></dt>
1766 <dd>If you want to use an electric field in a direction, enter 3 numbers
1767 after the appropriate <b>E-*</b>, the first number: the number of cosines,
1768 only 1 is implemented (with frequency 0) so enter 1,
1769 the second number: the strength of the electric field in
1770 <b>V nm<sup>-1</sup></b>,
1771 the third number: the phase of the cosine, you can enter any number here
1772 since a cosine of frequency zero has no phase.</dd>
1773 <dt><b>E-xt; E-yt; E-zt: </b></dt>
1774 <dd>not implemented yet</dd>
1780 <h3>Mixed quantum/classical molecular dynamics<!--QuietIdx>QM/MM<!--EQuietIdx--></h3>
1783 <dt><b>QMMM:</b></dt>
1784 <dd><dl compact="compact">
1788 <dd>Do a QM/MM simulation. Several groups can be described at
1789 different QM levels separately. These are specified in
1790 the <b>QMMM-grps</b> field separated by spaces. The level of <i>ab
1791 initio</i> theory at which the groups are described is specified
1792 by <b>QMmethod</b> and <b>QMbasis</b> Fields. Describing the
1793 groups at different levels of theory is only possible with the ONIOM
1794 QM/MM scheme, specified by <b>QMMMscheme</b>.</dd>
1797 <dt><b>QMMM-grps:</b></dt>
1798 <dd>groups to be descibed at the QM level</dd>
1800 <dt><b>QMMMscheme:</b></dt>
1801 <dd><dl compact="compact">
1802 <dt><b>normal</b></dt>
1803 <dd>normal QM/MM. There can only be one <b>QMMM-grps</b> that is modelled
1804 at the <b>QMmethod</b> and <b>QMbasis</b> level of <i>ab initio</i>
1805 theory. The rest of the system is described at the MM level. The QM
1806 and MM subsystems interact as follows: MM point charges are included
1807 in the QM one-electron hamiltonian and all Lennard-Jones interactions
1808 are described at the MM level.</dd>
1809 <dt><b>ONIOM</b></dt>
1810 <dd>The interaction between the subsystem is described using the ONIOM
1811 method by Morokuma and co-workers. There can be more than one <b>QMMM-grps</b> each modeled at a different level of QM theory
1812 (<b>QMmethod</b> and <b>QMbasis</b>).
1815 <dt><b>QMmethod: (RHF)</b></dt>
1816 <dd>Method used to compute the energy and gradients on the QM
1817 atoms. Available methods are AM1, PM3, RHF, UHF, DFT, B3LYP, MP2,
1818 CASSCF, and MMVB. For CASSCF, the number of electrons and orbitals
1819 included in the active space is specified by <b>CASelectrons</b>
1820 and <b>CASorbitals</b>. </dd>
1822 <dt><b>QMbasis: (STO-3G)</b></dt>
1823 <dd>Basis set used to expand the electronic wavefuntion. Only Gaussian
1824 basis sets are currently available, <i>i.e.</i> STO-3G, 3-21G, 3-21G*,
1825 3-21+G*, 6-21G, 6-31G, 6-31G*, 6-31+G*, and 6-311G.</dd>
1827 <dt><b>QMcharge: (0) [integer]</b></dt>
1828 <dd>The total charge in <tt>e</tt> of the <b>QMMM-grps</b>. In case
1829 there are more than one <b>QMMM-grps</b>, the total charge of each
1830 ONIOM layer needs to be specified separately.</dd>
1832 <dt><b>QMmult: (1) [integer]</b></dt>
1833 <dd>The multiplicity of the <b>QMMM-grps</b>. In case there are more
1834 than one <b>QMMM-grps</b>, the multiplicity of each ONIOM layer needs
1835 to be specified separately.</dd>
1837 <dt><b>CASorbitals: (0) [integer]</b></dt>
1838 <dd>The number of orbitals to be included in the active space when
1839 doing a CASSCF computation.</dd>
1841 <dt><b>CASelectrons: (0) [integer]</b></dt>
1842 <dd>The number of electrons to be included in the active space when
1843 doing a CASSCF computation.</dd>
1846 <dd><dl compact="compact">
1848 <dd>No surface hopping. The system is always in the electronic
1851 <dd>Do a QM/MM MD simulation on the excited state-potential energy
1852 surface and enforce a <i>diabatic</i> hop to the ground-state when the
1853 system hits the conical intersection hyperline in the course the
1854 simulation. This option only works in combination with the CASSCF
1861 <h3>Implicit solvent</h3>
1864 <dt><b>implicit-solvent:</b></dt>
1865 <dd><dl compact="compact">
1867 <dd>No implicit solvent</dd>
1868 <dt><b>GBSA</b></dt>
1869 <dd>Do a simulation with implicit solvent using the Generalized Born formalism.
1870 Three different methods for calculating the Born radii are available, Still, HCT and
1871 OBC. These are specified with the <b>gb-algorithm</b> field. The non-polar solvation
1872 is specified with the <b>sa-algorithm</b> field.</dd>
1875 <dt><b>gb-algorithm:</b></dt>
1876 <dd><dl compact="compact">
1877 <dt><b>Still</b></dt>
1878 <dd>Use the Still method to calculate the Born radii</dd>
1880 <dd>Use the Hawkins-Cramer-Truhlar method to calculate the Born radii</dd>
1882 <dd>Use the Onufriev-Bashford-Case method to calculate the Born radii</dd>
1885 <dt><b>nstgbradii: (1) [steps]</b></dt>
1886 <dd>Frequency to (re)-calculate the Born radii. For most practial purposes,
1887 setting a value larger than 1 violates energy conservation and leads to
1888 unstable trajectories.</dd>
1890 <dt><b>rgbradii: (1.0) [nm]</b></dt>
1891 <dd>Cut-off for the calculation of the Born radii. Currently must be equal to rlist</dd>
1893 <dt><b>gb-epsilon-solvent: (80)</b></dt>
1894 <dd>Dielectric constant for the implicit solvent</dd>
1896 <dt><b>gb-saltconc: (0) [M]</b></dt>
1897 <dd>Salt concentration for implicit solvent models, currently not used</dd>
1899 <dt><b>gb-obc-alpha (1); gb-obc-beta (0.8); gb-obc-gamma (4.85);</b></dt>
1900 <dd>Scale factors for the OBC model. Default values are OBC(II).
1901 Values for OBC(I) are 0.8, 0 and 2.91 respectively</dd>
1903 <dt><b>gb-dielectric-offset: (0.009) [nm]</b></dt>
1904 <dd>Distance for the di-electric offset when calculating the Born radii. This is
1905 the offset between the center of each atom the center of the polarization energy
1906 for the corresponding atom</dd>
1908 <dt><b>sa-algorithm</b></dt>
1909 <dd><dl compact="compact">
1910 <dt><b>Ace-approximation</b></dt>
1911 <dd>Use an Ace-type approximation (default)</dd>
1912 <dt><b>None</b></dt>
1913 <dd>No non-polar solvation calculation done. For GBSA only the polar part gets
1917 <dt><b>sa-surface-tension: [kJ mol<sup>-1</sup> nm<sup>-2</sup>]</b></dt>
1918 <dd>Default value for surface tension with SA algorithms. The default value is -1;
1919 Note that if this default value is not changed
1920 it will be overridden by <tt>grompp</tt> using values that are specific for the choice
1921 of radii algorithm (0.0049 kcal/mol/Angstrom<sup>2</sup> for Still, 0.0054 kcal/mol/Angstrom<sup>2</sup>
1924 Setting it to 0 will while using an sa-algorithm other than None means
1925 no non-polar calculations are done.
1929 <A NAME="adress"><br>
1931 <h3>Adaptive Resolution Simulation</h3>
1934 <dt><b>adress: (no)</b></dt>
1935 <dd>Decide whether the AdResS feature is turned on.</dd>
1936 <dt><b>adress-type: (Off)</b></dt>
1939 <dd>Do an AdResS simulation with weight equal 1, which is equivalent to an explicit (normal) MD simulation. The difference to disabled AdResS is that the AdResS variables are still read-in and hence are defined.</dd>
1940 <dt><b>Constant</b></dt>
1941 <dd>Do an AdResS simulation with a constant weight, <b>adress-const-wf</b> defines the value of the weight</dd>
1942 <dt><b>XSplit</b></dt>
1943 <dd>Do an AdResS simulation with simulation box split in x-direction, so basically the weight is only a function of the x coordinate and all distances are measured using the x coordinate only.</dd>
1944 <dt><b>Sphere</b></dt>
1945 <dd>Do an AdResS simulation with spherical explicit zone.</dd>
1947 <dt><b>adress-const-wf: (1)</b></dt>
1948 <dd>Provides the weight for a constant weight simulation (<b>adress-type</b>=Constant)</dd>
1949 <dt><b>adress-ex-width: (0)</b></dt>
1950 <dd>Width of the explicit zone, measured from <b>adress-reference-coords</b>.</dd>
1951 <dt><b>adress-hy-width: (0)</b></dt>
1952 <dd>Width of the hybrid zone.</dd>
1953 <dt><b>adress-reference-coords: (0,0,0)</b></dt>
1954 <dd>Position of the center of the explicit zone. Periodic boundary conditions apply for measuring the distance from it.</dd>
1955 <dt><b>adress-cg-grp-names</b></dt>
1956 <dd>The names of the coarse-grained energy groups. All other energy groups are considered explicit and their interactions will be automatically excluded with the coarse-grained groups.</dd>
1957 <dt><b>adress-site: (COM)</b>The mapping point from which the weight is calculated.</dt>
1960 <dd>The weight is calculated from the center of mass of each charge group.</dd>
1962 <dd>The weight is calculated from the center of geometry of each charge group.</dd>
1963 <dt><b>Atom</b></dt>
1964 <dd>The weight is calculated from the position of 1st atom of each charge group.</dd>
1965 <dt><b>AtomPerAtom</b></dt>
1966 <dd>The weight is calculated from the position of each individual atom.</dd>
1968 <dt><b>adress-interface-correction: (Off)</b></dt>
1971 <dd>Do not a apply any interface correction.</dd>
1972 <dt><b>thermoforce</b></dt>
1973 <dd>Apply thermodynamic force interface correction. The table can be specified using the <tt>-tabletf</tt> option of <tt>mdrun</tt>. The table should contain the potential and force (acting on molecules) as function of the distance from <b>adress-reference-coords</b>.</dd>
1975 <dt><b>adress-tf-grp-names</b></dt>
1976 <dd>The names of the energy groups to which the <b>thermoforce</b> is applied if enabled in <b>adress-interface-correction</b>. If no group is given the default table is applied.</dd>
1977 <dt><b>adress-ex-forcecap: (0)</b></dt>
1978 <dd>Cap the force in the hybrid region, useful for big molecules. 0 disables force capping.</dd>
1983 <h3>User defined thingies</h3>
1986 <dt><b>user1-grps; user2-grps: </b></dt>
1987 <dt><b>userint1 (0); userint2 (0); userint3 (0); userint4 (0)</b></dt>
1988 <dt><b>userreal1 (0); userreal2 (0); userreal3 (0); userreal4 (0)</b></dt>
1989 <dd>These you can use if you modify code. You can pass integers and
1990 reals to your subroutine. Check the inputrec definition in
1991 <tt>src/include/types/inputrec.h</tt></dd>
2002 <A HREF="#neq">acc-grps</A><br>
2003 <A HREF="#neq">accelerate</A><br>
2004 <A HREF="#sa">annealing</A><br>
2005 <A HREF="#sa">annealing-npoints</A><br>
2006 <A HREF="#sa">annealing-time</A><br>
2007 <A HREF="#sa">annealing-temp</A><br>
2008 <A HREF="#ld">bd-fric</A><br>
2009 <A HREF="#vdw">bDispCorr</A><br>
2010 <A HREF="#run">comm-mode</A><br>
2011 <A HREF="#run">comm-grps</A><br>
2012 <A HREF="#pc">compressibility</A><br>
2013 <A HREF="#bond">constraint-algorithm</A><br>
2014 <A HREF="#bond">constraints</A><br>
2015 <A HREF="#neq">cos-acceleration</A><br>
2016 <A HREF="#el">coulombtype</A><br>
2017 <A HREF="#el">coulomb-modifier</A><br>
2018 <A HREF="#free">couple-intramol</A><br>
2019 <A HREF="#free">couple-lambda0</A><br>
2020 <A HREF="#free">couple-lambda1</A><br>
2021 <A HREF="#free">couple-moltype</A><br>
2022 <A HREF="#nl">cutoff-scheme</A><br>
2023 <A HREF="#pp">define</A><br>
2024 <A HREF="#neq">deform</A><br>
2025 <A HREF="#free">delta-lambda</A><br>
2026 <A HREF="#nmr">disre</A><br>
2027 <A HREF="#nmr">disre-weighting</A><br>
2028 <A HREF="#nmr">disre-mixed</A><br>
2029 <A HREF="#nmr">disre-fc</A><br>
2030 <A HREF="#nmr">disre-tau</A><br>
2031 <A HREF="#run">dt</A><br>
2032 <A HREF="#em">emstep</A><br>
2033 <A HREF="#em">emtol</A><br>
2034 <A HREF="#egexcl">energygrp-excl</A><br>
2035 <A HREF="#table">energygrp-table</A><br>
2036 <A HREF="#out">energygrps</A><br>
2037 <A HREF="#el2">epsilon-r</A><br>
2038 <A HREF="#el2">epsilon-rf</A><br>
2039 <A HREF="#ewald">ewald-rtol</A><br>
2040 <A HREF="#ewald">ewald-geometry</A><br>
2041 <A HREF="#ewald">epsilon-surface</A><br>
2042 <A HREF="#ef">E-x</A><br>
2043 <A HREF="#ef">E-xt</A><br>
2044 <A HREF="#ef">E-y</A><br>
2045 <A HREF="#ef">E-yt</A><br>
2046 <A HREF="#ef">E-z</A><br>
2047 <A HREF="#ef">E-zt </A><br>
2048 <A HREF="#xmdrun">fcstep</A><br>
2049 <A HREF="#ewald">fourier-nx</A><br>
2050 <A HREF="#ewald">fourier-ny</A><br>
2051 <A HREF="#ewald">fourier-nz</A><br>
2052 <A HREF="#ewald">fourierspacing</A><br>
2053 <A HREF="#free">free-energy</A><br>
2054 <A HREF="#neq">freezedim </A><br>
2055 <A HREF="#neq">freezegrps</A><br>
2056 <A HREF="#vel">gen-seed</A><br>
2057 <A HREF="#vel">gen-temp</A><br>
2058 <A HREF="#vel">gen-vel</A><br>
2059 <A HREF="#pp">include</A><br>
2060 <A HREF="#free">init-lambda</A><br>
2061 <A HREF="#expanded">init-lambda-weights</A><br>
2062 <A HREF="#run">init-step</A><br>
2063 <A HREF="#expanded">initial-wl-delta</A><br>
2064 <A HREF="#run">integrator</A><br>
2065 <A HREF="#ld">ld-seed</A><br>
2066 <A HREF="#bond2">lincs-iter</A><br>
2067 <A HREF="#bond2">lincs-order</A><br>
2068 <A HREF="#bond2">lincs-warnangle</A><br>
2069 <A HREF="#expanded">lmc-forced-nstart</A><br>
2070 <A HREF="#expanded">lmc-gibbsdelta</A><br>
2071 <A HREF="#expanded">lmc-mc-move</A><br>
2072 <A HREF="#expanded">lmc-seed</A><br>
2073 <A HREF="#expanded">lmc-stats</A><br>
2074 <A HREF="#expanded">lmc-weights-equil</A><br>
2075 <A HREF="#expanded">mc-temperature</A><br>
2076 <A HREF="#expanded">mininum-var-min</A><br>
2077 <A HREF="#bond2">morse</A><br>
2078 <A HREF="#em">nbfgscorr</A><br>
2079 <A HREF="#xmdrun">niter</A><br>
2080 <A HREF="#tc">nh-chain-length</A><br>
2081 <A HREF="#em">nstcgsteep</A><br>
2082 <A HREF="#out">nstcalcenergy</A><br>
2083 <A HREF="#run">nstcomm</A><br>
2084 <A HREF="#nmr">nstdisreout</A><br>
2085 <A HREF="#out">nstenergy</A><br>
2086 <A HREF="#run">nsteps</A><br>
2087 <A HREF="#out">nstfout</A><br>
2088 <A HREF="#nl">nstlist</A><br>
2089 <A HREF="#out">nstlog</A><br>
2090 <A HREF="#pc">nstpcouple</A><br>
2091 <A HREF="#tc">nsttcouple</A><br>
2092 <A HREF="#out">nstvout</A><br>
2093 <A HREF="#out">nstxout</A><br>
2094 <A HREF="#out">nstxtcout</A><br>
2095 <A HREF="#expanded">nst-transition-matrix</A><br>
2096 <A HREF="#nl">ns-type</A><br>
2097 <A HREF="#wall">nwall</A><br>
2098 <A HREF="#ewald">optimize-fft</A><br>
2099 <A HREF="#nmr2">orire</A><br>
2100 <A HREF="#nmr2">orire-fc</A><br>
2101 <A HREF="#nmr2">orire-tau</A><br>
2102 <A HREF="#nmr2">orire-fitgrp</A><br>
2103 <A HREF="#nmr2">nstorireout</A><br>
2104 <A HREF="#nl">pbc</A><br>
2105 <A HREF="#pc">pcoupl</A><br>
2106 <A HREF="#pc">pcoupltype</A><br>
2107 <A HREF="#nl">periodic-molecules</A><br>
2108 <A HREF="#ewald">pme-order</A><br>
2109 <A HREF="#pull">pull</A><br>
2110 <A HREF="#pc">refcoord-scaling</A><br>
2111 <A HREF="#pc">ref-p</A><br>
2112 <A HREF="#tc">ref-t</A><br>
2113 <A HREF="#el2">rcoulomb-switch</A><br>
2114 <A HREF="#el2">rcoulomb</A><br>
2115 <A HREF="#nl">rlist</A><br>
2116 <A HREF="#nl">rlistlong</A><br>
2117 <A HREF="#tpi">rtpi</A><br>
2118 <A HREF="#vdw">rvdw-switch</A><br>
2119 <A HREF="#vdw">rvdw</A><br>
2120 <A HREF="#free">sc-alpha</A><br>
2121 <A HREF="#free">sc-power</A><br>
2122 <A HREF="#free">sc-sigma</A><br>
2123 <A HREF="#bond2">shake-tol</A><br>
2124 <A HREF="#expanded">sim-temp-low</A><br>
2125 <A HREF="#expanded">sim-temp-high</A><br>
2126 <A HREF="#expanded">simulated-tempering</A><br>
2127 <A HREF="#expanded">simulated-tempering-scaling</A><br>
2128 <A HREF="#expanded">symmetrized-transition-matrix</A><br>
2129 <A HREF="#table">table-extension</A><br>
2130 <A HREF="#pc">tau-p</A><br>
2131 <A HREF="#tc">tau-t</A><br>
2132 <A HREF="#tc">tc-grps</A><br>
2133 <A HREF="#tc">tcoupl</A><br>
2134 <A HREF="#run">tinit</A><br>
2135 <A HREF="#bond">continuation</A><br>
2136 <A HREF="#user">user1-grps</A><br>
2137 <A HREF="#user">user2-grps</A><br>
2138 <A HREF="#user">userint1</A><br>
2139 <A HREF="#user">userint2</A><br>
2140 <A HREF="#user">userint3</A><br>
2141 <A HREF="#user">userint4</A><br>
2142 <A HREF="#user">userreal1</A><br>
2143 <A HREF="#user">userreal2</A><br>
2144 <A HREF="#user">userreal3</A><br>
2145 <A HREF="#user">userreal4</A><br>
2146 <A HREF="#vdw">vdwtype</A><br>
2147 <A HREF="#vdw">vdw-modifier</A><br>
2148 <A HREF="#nl">verlet-buffer-drift</A><br>
2149 <A HREF="#out">xtc-grps</A><br>
2150 <A HREF="#out">xtc-precision</A><br>
2151 <A HREF="#sa">zero-temp-time</A><br>
2152 <A HREF="#walls">wall-atomtype</A><br>
2153 <A HREF="#walls">wall-density</A><br>
2154 <A HREF="#walls">wall-ewald-zfac</A><br>
2155 <A HREF="#walls">wall-r-linpot</A><br>
2156 <A HREF="#walls">wall-type</A><br>
2157 <A HREF="#expanded">weight-equil-count-ratio</A><br>
2158 <A HREF="#expanded">weight-equil-number-all-lambda</A><br>
2159 <A HREF="#expanded">weight-equil-number-samples</A><br>
2160 <A HREF="#expanded">weight-equil-number-steps</A><br>
2161 <A HREF="#expanded">weight-equil-wl-delta</A><br>
2162 <A HREF="#expanded">wl-ratio</A><br>
2163 <A HREF="#expanded">wl-scale</A><br>
2168 <font size="-1"><a href="http://www.gromacs.org">http://www.gromacs.org</a></font><br>
biod.pnpi.spb.ru / alexxy / gromacs.git / blob