SUBDOCK on C7: Difference between revisions

From DISI
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
These are C7 specific notes for running [[SUBDOCK_DOCK3.8|SUBDOCK]] with [[DOCK 3.8]] on [[Cluster 7]].
SUBDOCK on C7
For the full SUBDOCK reference, see [[SUBDOCK_DOCK3.8]].


== What SUBDOCK does ==
This page is for C7-specific notes on [[SUBDOCK_DOCK3.8|SUBDOCK]]. For the full SUBDOCK documentation, see [[SUBDOCK_DOCK3.8]].
SUBDOCK submits many DOCK jobs to a scheduler.
On C7, the scheduler is SLURM, so SUBDOCK submits jobs with sbatch.


== Main C7 Rule ==
== C7 setup ==
C7 uses SLURM. Do not use SGE on C7.
 
Load DOCK:
 
module load dock
echo $DOCK_INSTALL_PATH
echo $DOCKBASE
 
SUBDOCK is inside the DOCK install:
 
${DOCK_INSTALL_PATH}/SUBDOCK/subdock.bash
${DOCK_INSTALL_PATH}/SUBDOCK/rundock.bash
 
`subdock.bash` expects `rundock.bash` to be in the same directory.
 
== Scheduler ==
 
C7 runs this workflow through SLURM (`sbatch`). Set the controller explicitly:
 
export USE_SLURM=true
export USE_SGE=false
export USE_PARALLEL=false
export USE_CHARITY=false
 
If more than one controller is enabled, SUBDOCK exits with:
 
cannot select more than one job controller!


== Required variables ==
== Required variables ==
SUBDOCK needs four main paths:
EXPORT_DEST
INPUT_SOURCE
DOCKFILES
DOCKEXEC


# EXPORT_DEST is where results and logs go.
SUBDOCK needs:
# INPUT_SOURCE is the file listing the ligand database files to dock.
# DOCKFILES is the directory containing the prepared docking files.
# DOCKEXEC is the DOCK executable.


On C7, after `module load dock`, the DOCK executable is usually:
export EXPORT_DEST=/path/to/output
  ${DOCK_INSTALL_PATH}/dock3/dock64
export INPUT_SOURCE=/path/to/split_database_index
export DOCKFILES=/path/to/dockfiles
  export DOCKEXEC=${DOCK_INSTALL_PATH}/dock3/dock64


== C7 path warning ==
Use paths in your own workspace. Do not write output into the shared DOCK install, e.g. avoid:
Do not write output into the shared DOCK installation.
Use a directory in your own workspace instead.


== Checking jobs ==
${DOCK_INSTALL_PATH}/test/docking/output


While jobs are running:
== Run ==
squeue -u $USER


For one job:
Example:
 
mkdir -p output
export EXPORT_DEST="$(pwd)/output"
export INPUT_SOURCE="$(pwd)/split_database_index"
export DOCKFILES="$(pwd)/dockfiles"
export DOCKEXEC="${DOCK_INSTALL_PATH}/dock3/dock64"
bash ${DOCK_INSTALL_PATH}/SUBDOCK/subdock.bash
 
Successful submission looks like:
 
submitting N out of N jobs
Submitted batch job <jobid>
 
== Check jobs ==
 
squeue -u $USER
  squeue -j <jobid>
  squeue -j <jobid>
After jobs finish, check the logs in the output directory.
 
`sacct` may not work on C7 if SLURM accounting is disabled. Check logs after completion:
 
ls output/logs
less output/logs/1.out
 
Success usually includes:
 
starting DOCK vers=3.8
finished!


== Related pages ==
== Related pages ==
Line 43: Line 81:
* [[DOCK 3.8]]
* [[DOCK 3.8]]


[[Category:Buyan]]
[[Category:DOCK_3.8]]
[[Category:DOCK_3.8]]
[[Category:Cluster 7]]
[[Category:Cluster 7]]

Revision as of 21:10, 22 June 2026

SUBDOCK on C7

This page is for C7-specific notes on SUBDOCK. For the full SUBDOCK documentation, see SUBDOCK_DOCK3.8.

C7 setup

Load DOCK:

module load dock
echo $DOCK_INSTALL_PATH
echo $DOCKBASE

SUBDOCK is inside the DOCK install:

${DOCK_INSTALL_PATH}/SUBDOCK/subdock.bash
${DOCK_INSTALL_PATH}/SUBDOCK/rundock.bash

`subdock.bash` expects `rundock.bash` to be in the same directory.

Scheduler

C7 runs this workflow through SLURM (`sbatch`). Set the controller explicitly:

export USE_SLURM=true
export USE_SGE=false
export USE_PARALLEL=false
export USE_CHARITY=false

If more than one controller is enabled, SUBDOCK exits with:

cannot select more than one job controller!

Required variables

SUBDOCK needs:

export EXPORT_DEST=/path/to/output
export INPUT_SOURCE=/path/to/split_database_index
export DOCKFILES=/path/to/dockfiles
export DOCKEXEC=${DOCK_INSTALL_PATH}/dock3/dock64

Use paths in your own workspace. Do not write output into the shared DOCK install, e.g. avoid:

${DOCK_INSTALL_PATH}/test/docking/output

Run

Example:

mkdir -p output
export EXPORT_DEST="$(pwd)/output"
export INPUT_SOURCE="$(pwd)/split_database_index"
export DOCKFILES="$(pwd)/dockfiles"
export DOCKEXEC="${DOCK_INSTALL_PATH}/dock3/dock64"
bash ${DOCK_INSTALL_PATH}/SUBDOCK/subdock.bash

Successful submission looks like:

submitting N out of N jobs
Submitted batch job <jobid>

Check jobs

squeue -u $USER
squeue -j <jobid>

`sacct` may not work on C7 if SLURM accounting is disabled. Check logs after completion:

ls output/logs
less output/logs/1.out

Success usually includes:

starting DOCK vers=3.8
finished!

Related pages