<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.docking.org/index.php?action=history&amp;feed=atom&amp;title=Running_DOCK_3.7</id>
	<title>Running DOCK 3.7 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.docking.org/index.php?action=history&amp;feed=atom&amp;title=Running_DOCK_3.7"/>
	<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Running_DOCK_3.7&amp;action=history"/>
	<updated>2026-04-07T17:42:25Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Running_DOCK_3.7&amp;diff=5752&amp;oldid=prev</id>
		<title>Frodo: Created page with &quot;Setting up an alias for the dock37tools directory in $DOCK_BASE/src/dock37tools/ is highly recommended, though you don&#039;t need it if you don&#039;t want it. Assume you have it set a...&quot;</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Running_DOCK_3.7&amp;diff=5752&amp;oldid=prev"/>
		<updated>2014-02-13T21:40:02Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Setting up an alias for the dock37tools directory in $DOCK_BASE/src/dock37tools/ is highly recommended, though you don&amp;#039;t need it if you don&amp;#039;t want it. Assume you have it set a...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Setting up an alias for the dock37tools directory in $DOCK_BASE/src/dock37tools/ is highly recommended, though you don&amp;#039;t need it if you don&amp;#039;t want it. Assume you have it set as $d37 from here on out with a command line this&lt;br /&gt;
 setenv d37 $DOCK_BASE/src/dock37tools/&lt;br /&gt;
In that directory, there are 3 scripts for setting up a dock run. The first script will send setup a docking run where each file will be relegated to a separate node, fine for quick jobs.&lt;br /&gt;
 $d37/setup_db2.csh /full/path/to/db2/files/&lt;br /&gt;
Another script, useful for testing on DUD-E targets, is:&lt;br /&gt;
 $d37/setup_db2_own.csh /full/path/to/db2/files/&lt;br /&gt;
A file script, useful for running many db2.gz files, sometimes with a few files grouped together, like for prospective screening against lead-like is:&lt;br /&gt;
 $d37/setup_db2_lots.py desiredDirectoryCount prefixName  /full/path/to/db2/files/&lt;br /&gt;
After setting up any of these runs, you can run them with the following:&lt;br /&gt;
 $d37/submit.csh&lt;br /&gt;
or $d37/subdock.csh /path/to/dock.csh if you have compiled your own version of DOCK3.7.&lt;br /&gt;
&lt;br /&gt;
Runs should proceed on the cluster. Problems will show up in the stderr files, further diagnosis can be attempted by looking at the various OUTDOCK files produced. If you&amp;#039;ve used lots of sampling, expect slower results. If you&amp;#039;ve asked for hundreds of poses, expect large files. You should not combine prospective screening, hundreds of poses and high sampling.&lt;br /&gt;
&lt;br /&gt;
If a few jobs crash (shouldn&amp;#039;t happen but anything is possible) and you need to complete them, run&lt;br /&gt;
&lt;br /&gt;
 $d37/restart.py -f&lt;br /&gt;
&lt;br /&gt;
{{Template:CC-BY-SA-30}}&lt;br /&gt;
{{Template:Coleman}}&lt;br /&gt;
[[Category:DOCK 3.7]]&lt;/div&gt;</summary>
		<author><name>Frodo</name></author>
	</entry>
</feed>