DOCK 3
Jump to navigation
Jump to search
DOCK 3 is the version of DOCK used, maintained and developed in the Shoichet Laboratory. It is the engine behind DOCK Blaster and the basis for all the docking work published from the lab. For more information, please see the flyer Why Use DOCK].
The current distributed version of DOCK 3 is DOCK 3.7. DOCK Blaster still uses DOCK 3.6. We are actively working to switch to DOCK 3.7.
History
- DOCK 3.0 was initially released in 1992 by the Kuntz Laboratory.
- DOCK 3.5 was released in 1993.
- From 1994-2002, DOCK 3.5 was developed in the group of Brian Shoichet, first at the University of Oregon, then at Northwestern University Medical School. The major author of the changes was David Lorber. BinQing Wei and other lab members also contributed.
- DOCK 3.5 returned to UCSF in 2003 as DOCK 3.5.54 when the Shoichet Laboratory moved there.
- DOCK 3.5.54 remained largely unchanged except for minor bugfixes from 2003-2008.
- Brian Shoichet wrote solvmap.
- Michael Mysinger wrote code to read gzipped database files.
- Niu Huang wrote flexible water handling code, based on BinQing Wei's flexible receptor code. This has not been incorporated into the germ line version of DOCK 3.
- From 2008 - May 2010, a number of changes were made. These changes (below) were rolled up and called DOCK 3.6 in May 2010.
- MMM improved handling of ligand desolvation maps
- Mike Carchia speeded up the already fast code from 3X to 5X using compiler optimizations, data duplication, and other techniques.
- Ryan Coleman improved the handling of ligand hierarchies by improving the algorithms in mol2db and dock for sampling ligands. Additional work was put into clash-checking ligands, checking to make sure the ligands do not fall outside of the grid boundaries, and general code cleanup.
- From May 2010 until the present (May 2011), more changes have been made, but have not yet been released.
- In September of 2013 DOCK 3.7 was released, for details of the changes see coleman et al.
Relationship to DOCK 6
DOCK 6 has the same goal as DOCK 3, but it is a completely different program, with different inputs, outputs and algorithms.