<html>
<head><title>MCCCS Towhee (input_style 'advanced connectivity map')</title></head>
<body bgcolor="#FFFFFF" text="#000000">
<table width="800" border="0" cellspacing="0" cellpadding="0" height="590">
<tr>
<td colspan="2" height="29">
<div align="center"> <font size="5"> <b><font face="Arial, Helvetica, sans-serif"><a name="top"></a>
MCCCS Towhee (input_style 'advanced connectivity map')</font></b </font>
</div>
</td>
</tr>
<A href="http://sourceforge.net">
<IMG src="http://sourceforge.net/sflogo.php?group_id=87039&type=5" width="210" height="62" border="0" alt="SourceForge.net Logo" align="right"/>
</A>
<tr>
<td width="18" height="371" valign="top">
<p> </p>
<p> </p>
</td>
<td width="700" valign="top">
This section describes the input variables associated with an <b>input_style</b> setting of 'advanced connectivity map'.
This option adds additional flexibility compared to the similar <a href="inpstyle_2.html">basic connectivity map</a> and is designed to replace
that option.
This documentation is only maintained for the current version of the code.
This molecule assembly option is a powerful and relatively easy way to set up the molecular interactions by listing the atom types and providing
their bond partners and rudimentary information about the bond orders.
This option is designed to work with the force fields and atom names listed in the <a href="../towhee_capabilities.html">Towhee Capabilities</a> section.
This option determines all of the vibration types, bending angles, bending types, regular torsion angles, regular torsion types, angle-angle terms,
angle-angle types, and improper torsion types that are implied by the bonding structure of the molecule. It also provides an option for a rule-based
determination of improper torsions based upon the bonding pattern.
<p> </p>
<dt><a name="nunit"><b>nunit (integer)</b></a>
<ul>
<li> The number of atoms (or united-atoms) in this molecule. Must be less than or equal to NUMAX
(see <a href="../code/code_manual.html#preproc">preproc.h</a>).
</li>
</ul>
</dt>
<dt><a name="nmaxcbmc"><b>nmaxcbmc (integer)</b></a>
<ul>
<li> The maximum number of atoms to regrow during a <a href="../code/cbmc.html">configurational-bias</a> regrowth. It is suggested to set this to
the same value as <b>nunit</b>, but some molecules are so large that almost none of the moves which regrow large portions are accepted.
In those cases setting a lower value of <b>nmaxcbmc</b> focused the software on moves that are likely to be accepted.
</li>
</ul>
</dt>
<dt><a name="lpdbnames"><b>lpdbnames (logical)</b></a>
<ul>
<li>.TRUE. : to enable the input of information about the pdb (protein data bank) atom name, amino acid number, amino acid name. This
information is needed in order to use the cartoon feature of certain pdb viewers (such as <a href="../software.html#rasmol">Rasmol</a>).
</li>
<li>.FALSE. : to disable the input of additional pdb information. This does not disable the output of pdb files, it just means thing like
the <a href="../software.html#rasmol">Rasmol</a> cartoon feature will not work properly.
</li>
</ul>
</dt>
<dt><a name="forcefield"><b>forcefield (character*10)</b></a>
<ul>
<li>The Towhee shorthand name for the forcefield that you want to use to build this molecule.
See <a href="../towhee_capabilities.html">Towhee Capabilities</a> for a complete list of the forcefields included with the Towhee distribution.
</li>
</ul>
</dt>
<dt><a name="charge_assignment"><b>charge_assignment (character*30)</b></a>
<ul>
<li>'bond increment': the bond increment method is used to assign the charges on each atom and the variable <b>charge</b> is not required. Note that
this method is not functional for all forcefields.
</li>
<li>'manual': the charges on each atom are manually specified in the towhee_input file as the variable <b>charge</b> in the following section.</li>
<li>'none': a zero charge is assigned to each atom and the variable <b>charge</b> is not required.</li>
</ul>
</dt>
<dt><a name="improper_assignment"><b>improper_assignment (character*30)</b></a>
<ul>
<li>'3-bond: single improper': atoms that are bonded to exactly three neighbors are assigned a single improper torsions automatically.
The three neighbors are automatically assigned in increasing order of their nonbonded integer type number.
Originally implemented for use with the <a href="../forcefields/mmff94.html">MMFF94</a> force field.
The improper torsion variables are not required in the subsequent section.
</li>
<li>'manual': the improper torsions each atom are manually specified in the subsequent section.</li>
<li>'none': no improper torsions are assigned for this molecule and the improper torsion variables are not required in the subsequent section.</li>
</ul>
</dt>
<dt><a name="match_style"><b>match_style (character*30)</b></a>
<ul>
<li>'standard' : determines matching interactions for a given forcefield by checking for exact type matches first, and then utilizing
a procedure that checks for an increasing number of wildcards. This is the approach recommended for the majority of forcefields and is the
default value used by most of the other molecule assembly options.
</li>
<li>'stereoselective' : very similar to the 'standard' option, but also requires the input of a list of torsions that have a specific stereochemistry.
This allows the process to distinguish between cis and trans dihedrals when combined with a forcefield that makes such a distinction. When using
this option the <a href="#special_torsion_count"><b>special_torsion_count</b></a> variables are required after the usual input of the connectivity.
</li>
<li>'MMFF checkdown' : determines matching interactions for a given forcefield using the procedure described in the
<a href="../forcefields/mmff94.html">MMFF94</a> forcefield papers. This uses an internal checkdown procedure based upon atom names that
are implemented as a 10 character string that contains 5 2-character substrings.
</li>
</ul>
</dt>
<p> </p>
<hr></hr>
<font color="red"> The variables in this section are required for each atom in the molecule (determined by <b>nunit</b>), one atom at a time.</font>
<dt><a name="unit"><b>unit (integer), type (character), charge (double precision)</b></a>
<ul>
<li><b>unit</b> is the number of the atom in order starting from atom number 1.</li>
<li><b>ntype</b> is the character string that contains the atom type for this atom. Information about valid atomtypes is found in individual
forcefield documentation (see the <a href="../towhee_capabilities.html">Towhee Capabilities</a> manual).
</li>
<li><b>charge</b> is the charge on this atom. This is only required if the <b>charge_assignment</b> variable is set to 'manual'.</li>
</ul>
</dt>
<dt><a name="pdbname"><b>pdbname (character), aminonum (integer), aminoshort (character)</b></a>
<ul>
<dt><font color="green">Note: These variables are only listed if <b>lpdbnames</b> = .TRUE.</font></dt>
<li> pdbname: A four character string that is output in the pdb file. The precise spacing is important if you want most pdb viewers to recognize
the atoms as the pdb file is extremely specific.
</li>
<li> aminonum: The number of each amino acid starting from the N-terminus.</li>
<li> aminoshort: The three letter code for each amino acid, or other group (such as caps on the C or N termini).</li>
</ul>
</dt>
<dt><a name="vibration"><b>vibration</b></a>
<ul>
<li>The first line under the vibration heading is the number of atoms that are bonded to the current atom. Must be a number between
0 and NNBOND (see <a href="../code/code_manual.html#preproc">preproc.h</a>).
</li>
<li>For each vibration a subsequent line contains the atom number (integer) of the bond partner and the
vibration order (character string a10) of the bond. Commonly used vibration orders are listed here.
<ul>
<li>'any': matches any bond order listed in the force field file. This effectively disables the vibration order searching. This entry is
only valid in the towhee_input file, and not in an ff*.F file.
</li>
<li>'aromatic': aromatic bond</li>
<li>'single': single bond</li>
<li>'double': double bond</li>
<li>'triple': triple bond</li>
<li>'wild': matches with any type of bond, but only if there is not an exact match. This is only a valid entry in an ff*.F file, and not
in the towhee_input file.
<li>
</ul>
</li>
</ul>
</dt>
<dt><b>improper torsion</b>
<ul>
<dt><font color="green">
Note: These variables are only listed for certain settings of <a href="#improper_assignment"><b>improper_assignment</b></a>
</font></dt>
<li>The first line under the improper heading is the number of improper torsions (any form) that have the central atom located at the current atom.
You must list all improper torsions that have the current atom at the central position, but you do not list improper torsions that only contain
the current atom at one of the ends. Must be a number between 0 and <b>MAXIMPROP</b>
(see <a href="../code/code_manual.html#preproc">preproc.h</a>).
</li>
<li>For each improper torsion specified above a line with the following information is required. A list of the three other atoms in the
improper torsion followed by the appropriate improper type for the force field. The code currently only allows an improper torsion where the
three other atoms are all bonded to the first atom. If you want to enable the automatic determination of the improper torsion force field
parameters then set the improper force field type to 0.
</li>
</ul>
</dt>
<dt><font color="red"> This is the end of the section that is repeated for each atom</font></dt>
<dt><a name="special_torsion_count"><b>special_torsion_count</b></a>
<ul>
<font color="green">Note: These variables are only listed for certain settings of <a href="#match_style"><b>match_style</b></a></font>
<li>The first line under the special_torsion_count heading is the number of special torsion assignments that involve a torsion order other than 'wild'.
If this value is not 0, then a subsequent line is required for each value of this variable.
<li>
<li>For each value of the special_torsion_count specified above, a line with the following information is required.
A list of the integer values of the 4 atoms that make up the special torsion, followed by a character string that describes the special
torsion. The character string is checked against the torsion order specified in the various forcefield files in order to determine a match.
The torsions only need to be specified in a single order, so if there was a special torsion between atoms 1,2,3, and 4 it is only required to
list the 1 2 3 4 'special flag' direction and not the 4 3 2 1 'special flag' direction. The special torsion order character string depends
upon the force field, but typical values are listed here.
<ul>
<li>'wild' : default value if none is specified. This matches up with torsions that do not have a specified torsion order as the default
output for the torsion order is 'wild'. There is no reason to go through the effort of listing this value since it is the default, but
it would result in a valid match with the default torsions so it is allowed.
</li>
<li>'cis' : matches up with a torsion that is in the cis conformation only. Typically occurs for double bonded carbons that are then bonded
to dissimilar atoms.
</li>
<li>'trans' : matches up with a torsion that is in the trans conformation only. Typically occurs for double bonded carbons that are then bonded
to dissimilar atoms.
</li>
</ul>
</li>
</ul>
</dt>
<hr></hr>
</ul>
<a href="../index.html">Return to the main towhee web page</a>
<p> </p>
</td>
</tr>
</table>
<hr width="715" align="left">
<i><font size="2">Send comments to:</font></i>
<font size="2"> <a href="mailto:marcus_martin@users.sourceforge.net">Marcus G. Martin</a>
<br></br>
<i>Last updated:</i><!-- #BeginDate format:Am1 -->January 08, 2007<!-- #EndDate -->
</font>
<br></br>
</body>
</html>
distrib
>
Fedora
>
14
>
x86_64
>
media
>
updates
>
by-pkgid
>
2f8321c8e2a11ea8b160a642cfc9fd7f
>
files
>
240
