| MBO(N)D |


> /pathname/mbond.exe < run_name.inp > run_name.out &Alternatively, you can put these commands into a file like the one below:
#commentsIf the command file is called run.com, and the name of the simulation is run_name, you can enter at the UNIX prompt:
#comments
#comments
/pathname/mbond.exe < $1.inp > $1.out
> run.com run_name &to submit the simulation.
Other input files
The other input files for an MBO(N)D CHARMm simulation are:
Substructured molecular dynamics is invoked by using the MBOND option of the regular CHARMm DYNAmics command. This enables several keywords particular to MBO(N)D and disables some that are not supported. In general, however, all the standard DYNAmics keywords are supported, unless specifically mentioned here.
Bodies must have been defined prior to invoking MBO(N)D dynamics (see SUBStructure). If no modes have been loaded (or generated) for the bodies, they are assumed to be rigid.
Only velocity scaling is supported for heating and equilibration protocols. However, the initial velocities may be assigned using any of the CHARMm options (including using a restart file). The thermostat that is available is a simple Berendsen method.
A typical protocol is to heat a system using an atomistic simulation, then equilibrate it and generate modes. When the switch is made to a substructured simulation, the system needs to be equilibrated once more before the data-collection stage of dynamics can begin.
Multiple time scales are supported in MBO(N)D. As usual, the MTS keyword must precede dynamics simulation. The MASS and DISTANCE keywords must be specified. They segregate nonbond interaction updating by combined mass/distance criterion (Multiple time scales). You can specify the number of stages for the MTS via the ratios keyword or allow it to be computed automatically.
The following CHARMm features are not supported in multibody simulations: SHAKE constraints (although bond length constraints between bodies and particles are supported with the HINGE BOND command), constant-pressure dynamics, Nosé-Hoover temperature control, Langevin dynamics.
The integrators that MBO(N)D does support are Lobatto and MTS Lobatto. The leapfrog and 4D Verlet algorithms cannot be used.
General outline of command input file
The most important elements in an MBO(N)D input script are:

Dynamics commands
Output commands