Supported docking programs and scoring functions

VFVS 2.0 supports many docking programs and scoring functions that run on both CPUs and GPUs. For using docking programs and scoring functions on GPUs, please modify the job submission file (/tools/templates/template1.slurm.sh) to indicate access to GPU nodes for running docking. To use a specific docking program or a scoring function of interest, the following modification may be required:

  1. Properly install the executable binary programs.

  2. Modify the all.ctrl file located in the tools/templates directory to specify the format of the ligands to be screened and the name of the docking program to be used.

  3. Create the configuration file (config.txt) to provide the parameters required by the docking program to dock. Examples of how the config.txt file looks like for each docking program are displayed in the VituralFlow 2.0 github repository.

AutoDock-GPU

  1. The AutoDock_GPU executable program (of name 'autodock_gpu') should be placed in the/tools/bin directory. The corresponding executable program needs to be compiled based on the user’s system using the instructions described here.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=autodock_gpu
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

AutoDock4/AutoDock-CPU

  1. The autodock4 executable program (of name 'autodock_cpu') should be placed in the/tools/bindirectory. The corresponding executable program needs to be compiled based on the user’s system using the instructions described here.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=autodock_cpu
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

AutoDock-ZN

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=AutodockZN
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

AutoDockVina 1.2

  1. Installation of the external docking program not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=AutodockVina_1.2
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

AutoDockVina 1.1.2

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=AutodockVina_1.1.2
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

ADFR

  1. The ADFR executable program (of name adfr) should be placed in the/tools/bin directory. The corresponding executable program needs to be compiled based on the user’s system using the instructions described here.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=adfr
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

AutoDock Koto

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=autodock_koto
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

CovDock

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=CovDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

GlideHTVS

  1. Installation of the external docking program not required.

  2. In all.ctrl file, set

ligand_library_format=smi
docking_scenario_programs=GlideHTVS
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

GlideSP

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=smi
docking_scenario_programs=GlideSP
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

GlideXP

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=smi
docking_scenario_programs=GlideXP
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

DOCK6.0

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=dock6
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Flexx

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=flexx
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

FitDock

  1. The FitDock executable program (of name 'FitDock') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=FitDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Gnina

  1. The Gnina executable program (of name 'Gnina') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=gnina
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

GalaxyDock3

  1. The GalaxyDock3 executable program (of name 'GalaxyDock3') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=GalaxyDock3
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

GOLD

  1. The GOLD executable program (of name 'gold_auto') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=gold
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

GWOVina

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=gwovina
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

HDock

  1. The HDock executable program (of name 'hdock') and the createpl executable program (of name 'createpl') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=pdb
docking_scenario_programs=HDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

idock

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=idock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

iGemDock

  1. The iGemDock executable program (of name 'mod_ga') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=iGemDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

LeDock

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=ledock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

LigandFit

  1. The LigandFit executable program (of name 'ligandfit') should be placed in the/tools/bindirectory.

  2. In all.ctrl file, set

ligand_library_format=pdb
docking_scenario_programs=LigandFit
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

LightDock

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdb
docking_scenario_programs=LightDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

MDock

  1. The MDock executable program (of name 'MDock_linux') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=M-Dock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

MCDock

  1. The MCDock executable program (of name 'mcdock') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=xyz
docking_scenario_programs=MCDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Molegro

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=Molegro
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

MpSDockZN

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=MpSDockZN
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

PSOVina

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=PSOVina
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

PLANTS

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=plants
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

QuickVina2

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

QuickVina-W

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_w
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

QuickVina_gpu

  1. The qvina_gpu executable program (of name 'qvina_gpu') should be placed in the/tools/bin directory. Instructions for compilation can be found here.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_gpu
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

QuickVina-W-gpu

  1. The QuickVina-W-gpu executable program (of name 'qvina_w_gpu') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_w_gpu
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

rDock

  1. The key word 'rbdock' must be able to activate the program (see download instructions, or, download with conda: conda install -c bioconda rdock)

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=rDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Rosetta-Ligand

  1. Please ensure that obabel is loaded into the environment (module load openbabel for Slurm)

  2. In all.ctrl file, set

ligand_library_format=sdf
docking_scenario_programs=rosetta-ligand
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

RLDock

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=RLDock
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

SEED

  1. The SEED executable program (of name 'seed4') should be placed in the/tools/bin directory. In addtion, AmberTools needs to be loaded in order to use SEED.

  2. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=SEED
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

SMINA

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=smina
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

VinaCarb

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=nina_carb
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

VinaXB16

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=vina_xb
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Vina-Gpu

  1. The qvina_gpu executable program (of name 'qvina_w_gpu') should be placed in the/tools/bin directory. Instructions for compilation can be found here.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_w_gpu
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Vina-Gpu-2.0

  1. The qvina_gpu executable program (of name 'qvina_w_gpu') should be placed in the/tools/bin directory. Instructions for compilation can be found here.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_w_gpu
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with NNScore2.0

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=nnscore2.0
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with rf-score-vs

  1. The rf-score-vs executable program (of name 'rf-score-vs') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=rf-score-vs
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with smina

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=smina_scoring
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with gnina

  1. The gnina executable program (of name 'gnina') should be placed in the/tools/bin directory.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=gnina_scoring
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with AutoDock4

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=ad4_scoring
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with Vinandro

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=vinandro_scoring
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Scoring with vina

  1. Installation of the external docking program is not required.

  2. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=vina_scoring
  1. For an example of theconfig.txt file, please refer to the VituralFlow 2.0 github repository.

Last updated