RDF input file consists of several parts: RDF-calculation parameters (&Parameters
), definition of Coarse-Grain atom types (&CGTypes
), the list of RDFs to calculate (&RDFsNB, &RDFsB, &RDFsA
) and optional declaration (&SameAsBond
) that some bonds in different molecules are equivalent, which means that their distributions are averaged, and they are assigned the same bonded potential in the CG model. The later is a formal way to have the same type of bond in several different molecular types.
&Parameters ... &EndParameters
)
The following parameters shall be specified:
NFORM
.CG.mmol
), having the same name as the
molecular type.
(&CGTypes, ... , &EndCGTypes)
<Name of CG-type>:<NameBead1 NameBead2 NameBead3>
, one line per each type, bead names are space separated.
Note that the order of bead type lines will define indexes of the bead types in the .mcm
-files.
(&RDFsNB, ... , &EndRDFsNB)
add: all
This will generate automatically a list of RDFs which includes all possible RDFs based on pair combinations of CG-atom types.
For each pair of CG-atom types a RDF will be determined, which includes all pairs of CG atoms of
the specified types, and effective potential for this pair of atom types will be calculated
on the next stage. With this option, all possible NB-RDFs will be taken into account. This is the
most common regime.
add: <CGType> -- <CGType>
Create a list of CG-atom pairs having the given CG-atom types, and include it into calculation of RDFs. This will add a single RDF to the list.
add: <CGType1> -- <CGType2>: AName1 AName2, AName3 AName4
Explicitly add pairs of atoms AName1-AName2, AName3-AName4 to the RDF for the given pair of
CG-atom types. This is the most precise way of setting the atom-pairs list for a given RDF.
del: <CGType> -- <CGType>
Remove a specific RDF (interaction) from the set of RDFs generated up to this line.
del: <CGType> -- <CGType>: AName1 AName2, AName3 AName4
Exclude a specific pair of atoms from the RDF for given atom types.
(&RDFsB, ... , &EndRDFsB)
In this section reference distributions for pairwise bonds (e.g. bond length distributions) are specified. Note that this determines bonding in the CG molecule, and thus has to be specified explicitly.
For each independent pairwise bond type one need to specify the molecular type it
belongs to, the relative index of the bond, and list of atom pairs connected by the bonds of this type.
This is done in a single line record:
add: <MolType>: <BondIndex>: <AName1> <AName2>, <AName3> <AName4>
where <MolType>
the molecular type, <BondIndex>
the bond type index in
the given molecular type, and pairs <AName1> <AName2>, <AName3> <AName4>,...
determine
CG atoms within the molecule connected by bonds of the <BondIndex>
bond type.
(&RDFsA, ... , &EndRDFsA)
add: all
Automatically deduce angle-bending bonds for all molecular types of the system
add: MolType : all
Automatically deduce angle-bending bonds in the given molecular type
add: <MolType>: <BondIndex>: <AName1> <AName2> <AName3>, ..., ...
Explicitly add triplet (triplets) of atoms to the given angle-bending bond of the given molecular type
del: MolType : all
Discard all angle-bending bonds in the given molecular type
del: MolType : <BondIndex>
Discard the given A-bond
del: MolType : <BondIndex>: <AName1> <AName2> <AName3>, ...,
Remove given atoms from the defined previously A-bond
&SameAsBond ... &EndSameAsBond
)
OriginalBond = LikedBond1, LinkedBond2,...
.
MolecularTypeName:BondNumber
, see example below.
&SameAsBond DMPC.CG:1 = DMPC.CG:3, DMPC.CG:4 DMPC.CG:2 = DMPC2.CG:1 &EndSameAsBond