Download ADF User's Guide

Transcript
http://www.scm.com/Doc/Doc2006.01/ADF/ADFUsersGuide/print.html
connection numbers zero, then for one that has only a bond length specification, etc. If the Z-matrix is not
properly defined, for instance if more than one atom occurs with all three connection numbers equal to zero,
or when not every atom is somehow connected to all others, the program will abort.
F=Fragment
Specifies that the atom belongs to a particular fragment. The fragment name must be of the form fragtype/n,
where fragtype is the name of one of the types of fragments in the molecule. The integer n, after the slash,
counts the individual fragments of that type. The numbering suffix /n is not required if there is only one
fragment of that type.
When f=fragment is omitted altogether, the fragment type is taken to be the atom type that was specified
earlier on the same line. (The numbering /n is then added automatically by the program, by counting the
number of times that this single-atom fragment type occurs in the list of atoms).
Mopac
The MOPAC style input requires that the records in the data block have the following format:
atomtype distance idist angle iangle dihedral idehedral
The three internal coordinate values (distance, angle, dihedral) are each followed directly by the connection
number.
Atom type is not identical to chemical element: an atom type is defined by all characteristics of the basic
atom to which it in fact refers: the nuclear charge, the basis functions, the frozen core, the density
functional and any other features that were applied in generating that basic atom.
As mentioned before, the point group symmetry specified in input with a Schönfliess type symbol puts
restrictions on the orientation of the atomic system. Unless the input-specified symmetry equals the true
symmetry of the nuclear frame (in which case adf will adjust the orientation of the molecule, if necessary),
the user must take care of this by supplying the Cartesian coordinates (in the appropriate orientation). If a
subgroup of the true nuclear symmetry is used and Z-matrix format is used for the coordinates, the program
will place the atoms in the standard Z-matrix frame: first atom at the origin, second on the positive x-axis,
third in the xy-plane with positive y-value.
Dummy atoms may be placed asymmetrically. If the atomic coordinates are input as Cartesians, any dummy
atoms are irrelevant. Their coordinates will be printed but otherwise they are ignored.
Input items are generally case insensitive. Exceptions are the names of files and directories. Since (to be
discussed below) the name of the fragment type as it is defined under atoms (explicitly with the f=option, or
implicitly as the name of the atom type) might also directly indicate the fragment file, the specification of
fragment types is in principle case-sensitive. Errors may occur if you are sloppy in this respect.
However, you must not give different fragment types names that differ only by case: at various places in the
program fragment type names are compared in a case-insensitive way.
Mixed Cartesian and Z-matrix coordinates
The key ATOMS can also be used to supply coordinates in a format that gives the values for the cartesian
coordinates and the connection matrix, which defines a Z-matrix.
ATOMS ZCart
{N} Atom Coords {F=Fragment}
...
End
6/30/06 10:27 AM
39 of 258