Action: FIXEDATOM

Module vatom
Description Usage
Add a virtual atom in a fixed position. used in 3 tutorialsused in 23 eggs
This action outputs data to a file. You can read more about how PLUMED manages output files here

Input

The atoms that serve as the input for this action are specified using one or more of the keywords in the following table.

Keyword Type Description
ATOMS atoms the list of atoms which are involved the virtual atom's definition

Further details and examples

Add a virtual atom in a fixed position.

This action creates a virtual atom at a fixed position. The example input below illustrates how this idea can be used to compute the angle between the vector connecting atoms 15 and 20 and the z axis and how this quantity can then be restrained so that the angle stays close to zero.

Click on the labels of the actions for more information on what each action computes
tested on2.11
a: FIXEDATOMAdd a virtual atom in a fixed position. This action has hidden defaults. More details ATcoordinates of the virtual atom=0,0,0
b: FIXEDATOMAdd a virtual atom in a fixed position. This action has hidden defaults. More details ATcoordinates of the virtual atom=0,0,1
an: ANGLECalculate one or multiple angle/s. More details ATOMSthe list of atoms involved in this collective variable (either 3 or 4 atoms)=a,b,15,20
RESTRAINTAdds harmonic and/or linear restraints on one or more variables. More details ARGthe values the harmonic restraint acts upon=an ATthe position of the restraint=0.0 KAPPA specifies that the restraint is harmonic and what the values of the force constants on each of the variables are=100.0

By default PLUMED assumes that any coordinates specified using the AT keyword specified are the cartesian coordinates of the fixed atom. However, if you use the SCALED_COMPONENTS flag the coordinates specified using the AT keyword are interpretted as scaled coordinates. It is also possible to assign a predefined charge or mass to the atom by using the SET_MASS and SET_CHARGE keywords.

[!CAUTION] This action, like POSITION is not invariant for translation of the system so adding a force on it can cause trouble.

The problem is that the vector connecting any atom and a virtual atom created using the FIXEDATOM atoms command is not invariant to translation. However, if, as has been done in the following example input, one first aligns atoms to a reference using FIT_TO_TEMPLATE, then it is safe to add further fixed atoms without breaking translational invariance.

Click on the labels of the actions for more information on what each action computes
tested on2.11
#SETTINGS INPUTFILES=regtest/basic/rt63/align.pdb
FIT_TO_TEMPLATEThis action is used to align a molecule to a template. More details STRIDE the frequency with which molecules are reassembled=1 REFERENCEa file in pdb format containing the reference structure and the atoms involved in the CV=
regtest/basic/rt63/align.pdb
Click here to see an extract from this file.
×

FILE: regtest/basic/rt63/align.pdb

ATOM      1 HH31 ACE     1      -0.000  -0.000  00.000  1.00  0.00            
ATOM      2 HH31 ACE     1      -0.000  -0.000  00.000  0.50  0.00            
END
TYPE the manner in which RMSD alignment is performed=SIMPLE a: FIXEDATOMAdd a virtual atom in a fixed position. This action has hidden defaults. More details ATcoordinates of the virtual atom=10,20,30 d: DISTANCECalculate the distance/s between pairs of atoms. More details ATOMSthe pair of atom that we are calculating the distance between=a,20 PRINTPrint quantities to a file. More details ARGthe labels of the values that you would like to print to the file=d FILEthe name of the file on which to output these quantities=colvar

Syntax

The following table describes the keywords and options that can be used with this action

Keyword Type Default Description
ATOMS input none the list of atoms which are involved the virtual atom's definition
AT compulsory none coordinates of the virtual atom
SET_MASS compulsory 1 mass of the virtual atom
SET_CHARGE compulsory 0 charge of the virtual atom
SCALED_COMPONENTS optional false use scaled components