SGE Cluster Docking: Difference between revisions

From DISI
Jump to navigation Jump to search
No edit summary
No edit summary
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== SGE Cluster Information ==
== SGE Cluster Information ==


*'sgehead.compbio.ucsf.edu' is the submit machine for the Sun Grid Engine (SGE) cluster.
*'sgehead.compbio.ucsf.edu' is the submit machine for the Sun Grid Engine (SGE) cluster. wilco is also authorized to submit jobs.
*'sgemaster.compbio.ucsf.edu' is the admin machine for the SGE cluster.
*There are around 250 cluster nodes providing 600 total cores to run jobs in the sge queue as of May, 2009, named like 'node-1-1' through 'node-3-36' where the first number is the rack # and the second is the slot # in that rack.
*There are around 250 cluster nodes availabe as of July, 2007, named like 'node-1-1' through 'node-3-36'.


== SGE Commands ==
== SGE Commands ==
*sgestat: high level overview of cluster status
*qsub: submit jobs<br>
*qsub: submit jobs<br>
*qstat: check job status<br>
*qstat: check job status<br>
Line 12: Line 12:
*man sge_intro: start of manpage documentation<br>
*man sge_intro: start of manpage documentation<br>


== Typical Docking Workflow ==


== Typical Docking Workflow ==
*Generate spheres and grids - See [[Using MakeDOCK]] for more information, including how to prepare the receptor and ligand
  ssh sgehead.compbio.ucsf.edu  # ssh to SGE submit machine
  ssh sgehead.compbio.ucsf.edu  # ssh to SGE submit machine
  mkdir example                  # make docking directory
  mkdir example                  # make docking directory
Line 19: Line 20:
  cp <somedir>/rec.pdb .        # copy or create rec.pdb
  cp <somedir>/rec.pdb .        # copy or create rec.pdb
  cp <somedir>/xtal-lig.mol2 .  # copy or create xtal-lig.mol2 (or even xtal-lig.pdb)
  cp <somedir>/xtal-lig.mol2 .  # copy or create xtal-lig.mol2 (or even xtal-lig.pdb)
  touch .only_spheres            # stop after grid generation
  startdockblaster5             # create spheres and grids                 
startdockblaster4             # create spheres and grids
                                # Check output for WARNING messages, correct as needed
tail -f stdout                 # follow grid preparation as it happens (control-C to terminate)
 
cat stderr                    # check for any error messages during grid peparation
* Setting up a docking run
  cp calibrate/INDOCK.1.A INDOCK # copy or create INDOCK
  cp calibrate/INDOCK.1.A INDOCK # copy or create INDOCK
  mksdir2.csh 2 50              # create directories for fragment-like in ~50 chunks
  md4db.csh bysubset 2 100      # create directories for docking run with 100 chunks
  cd run.2                      # chdir into run directory
                                # 2 indicates we want the fragment-like subset of ZINC (See http://zinc.docking.org/subset1)
  startdockbks3                  # submit database chunks to SGE cluster
  cd run.2                      # chdir into run.2 directory
 
* Everything else
  See [[MUD - Michael's Utilities for Docking]] for how to submit, check, and analyse the docking run.
 
For information on which ZINC
 
[[Category:Internal]]
[[Category:Tutorials]]
[[Category:Cluster]]

Latest revision as of 21:36, 27 February 2014

SGE Cluster Information

  • 'sgehead.compbio.ucsf.edu' is the submit machine for the Sun Grid Engine (SGE) cluster. wilco is also authorized to submit jobs.
  • There are around 250 cluster nodes providing 600 total cores to run jobs in the sge queue as of May, 2009, named like 'node-1-1' through 'node-3-36' where the first number is the rack # and the second is the slot # in that rack.

SGE Commands

  • sgestat: high level overview of cluster status
  • qsub: submit jobs
  • qstat: check job status
  • qdel: remove jobs
  • qhost: check cluster status
  • man sge_intro: start of manpage documentation

Typical Docking Workflow

  • Generate spheres and grids - See Using MakeDOCK for more information, including how to prepare the receptor and ligand
ssh sgehead.compbio.ucsf.edu   # ssh to SGE submit machine
mkdir example                  # make docking directory
cd example                     # change to docking directory
cp <somedir>/rec.pdb .         # copy or create rec.pdb
cp <somedir>/xtal-lig.mol2 .   # copy or create xtal-lig.mol2 (or even xtal-lig.pdb)
startdockblaster5              # create spheres and grids                 
                               # Check output for WARNING messages, correct as needed
  • Setting up a docking run
cp calibrate/INDOCK.1.A INDOCK # copy or create INDOCK
md4db.csh bysubset 2 100       # create directories for docking run with 100 chunks
                               # 2 indicates we want the fragment-like subset of ZINC (See http://zinc.docking.org/subset1)
cd run.2                       # chdir into run.2 directory
  • Everything else
See MUD - Michael's Utilities for Docking for how to submit, check, and analyse the docking run.

For information on which ZINC

Retrieved from "http://wiki.docking.org/index.php?title=SGE_Cluster_Docking&oldid=6321"