Kuntz Home / DOCK Home / DOCKumentation Contents / DOCK
prev section prev toc up next next section

What's New in DOCK 3.5

New Features / File Format Changes / Usage / Backwards Compatibility / Internal Changes

New Features - An Overview

DOCK 3.5 introduces several new features which increase the power of DOCK's existing algorithms. These are described in brief here and in greater detail in the corresponding manual sections.

File Format Changes

All of the new file formats begin with a header line that begins with DOCK as the first four characters, the version number (3.5) and a file type keyword. This expands as follows:

header line                            file type
DOCK 3.5 ligand_atoms                  DOCK 3.5 ligand database
DOCK 3.5 receptor_spheres              receptor sphere clusters/site points
DOCK 3.5 parameter                     INDOCK
DOCK 3.5 option                        DOCKOPT
This first line is of variable length and free format, with spaces separating the fields. The sphere cluster file now contains integer labels assigned to each sphere. The new format is described under
sphgen. The new format file contains a list of all of the spheres generated at the end of the file as cluster 0. This obviates the need for the tosph program, which is now no longer distributed. The ligand database file also contains atom labels; see the mol2db section for a description of the new format. Both sphere and ligand files now contain color tables, which are simply lists of the colors (labels), near the beginning of the file, and in the same format for both spheres and ligands. If the user decides not to do atom or sphere coloring, the color table is empty, and the atom and sphere colors are set to 0, which means uncolored. No provision has been made for coloring ligand spheres, since there is no obvious way to do it. New formats for the INDOCK and DOCKOPT files are described in the dock3.5 section. The new format uses keywords, rather than position in the file, to identify input variables.

Usage

Backward Compatibility

A large effort has been made to make DOCK as backward compatible as possible. DOCK 3.5 can read any combination of old (3.0) and new (3.5) format ligand database, sphere cluster, INDOCK and DOCKOPT files. Of course, labeled matching can take place only if the first three of these files are in the new format. The new versions of
sphgen, cluster, showsphere, and showbox read and write both new and old format sphere cluster files. mkdb and convsyb write only earlier format ligand database files (i.e., without labeled atoms).

Internal Changes Invisible to the User

The .com compilation shell scripts have been replaced by a Makefile for the main directory and each subdirectory. The Unix make command will recompile only those source files that have changed since the last compilation. Each Makefile contains rules regarding what source files an object file depends upon, and which object files an executable file depends upon. The programmer must keep the Makefile up to date, taking into account new files and new dependencies as they occur. If there is an error in the Makefile, the compiled program will have a bug in it. For example, if two source files share a common block in an include file, and one of the source files does not have this include file listed in its dependency list, it will not be recompiled when the include file changes, and the two .o object files will have incompatible common blocks.

Many DOCK arrays and variables that were previously passed as subroutinearguments are now located in new common blocks in new include (.h) files. Matching code that was located in four source files (single.f, search.f, fractm.f, and sfract.f) is now coalesced into one source file: match.f. Scoring code from these four files has similarly been coalesced into a single file: mscore.f. The keyword parameter reading code is in keyword.f.


prev section prev toc up next next section

Curator: Daniel Gschwend, gschwend@cgl.ucsf.edu (rev. 1 September 1995)