Documentation (VF 2.0)
VF HomepageTutorialsGitHub Repos
  • Documentation
    • Introduction
    • General Features
    • Installation
      • Prerequisities
      • VirtualFlow 2.0
      • VFTools 2.0
      • Uninstallation
    • Backgrounds and Principles
      • Directory Structure
      • Input & Output Databases
      • Job Organization
    • Using VirtualFlow 2.0
      • VirtualFlow 2.0 Commands
      • Preparing the Workflow
      • Starting the Workflow
      • Controlling the Workflow
      • Monitoring the Workflow
      • The Completed Workflow
    • Running VirtualFlow 2.0 in the Cloud
    • Troubleshooting
    • Version History
    • Further Resources
  • VFLP 2.0
    • Introduction
    • Features
    • Installation
      • Prerequisities
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Using VFLP 2.0
    • Troubleshooting
    • Version History
  • VFVS 2.0
    • Introduction
    • Features
    • Installation
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Supported docking programs and scoring functions
    • Using VFVS 2.0
      • Preparing the Workflow
      • Monitoring the Workflow
      • The Completed Workflow
    • Troubleshooting
    • Version History
  • VFU 2.0
    • Introduction
    • Features
    • Installation
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Using VFVS
      • Preparing the Workflow
      • Monitoring the Workflow
      • The Completed Workflow
    • Troubleshooting
    • Version History
  • VFTOOLS 2.0
    • Introduction
    • Installation
Powered by GitBook
On this page
  • AutoDock-GPU
  • AutoDock4/AutoDock-CPU
  • AutoDock-ZN
  • AutoDockVina 1.2
  • AutoDockVina 1.1.2
  • ADFR
  • AutoDock Koto
  • CovDock
  • GlideHTVS
  • GlideSP
  • GlideXP
  • DOCK6.0
  • Flexx
  • FitDock
  • Gnina
  • GalaxyDock3
  • GOLD
  • GWOVina
  • HDock
  • idock
  • iGemDock
  • LeDock
  • LigandFit
  • LightDock
  • MDock
  • MCDock
  • Molegro
  • MpSDockZN
  • PSOVina
  • PLANTS
  • QuickVina2
  • QuickVina-W
  • QuickVina_gpu
  • QuickVina-W-gpu
  • rDock
  • Rosetta-Ligand
  • RLDock
  • SEED
  • SMINA
  • VinaCarb
  • VinaXB16
  • Vina-Gpu
  • Vina-Gpu-2.0
  • Scoring with NNScore2.0
  • Scoring with rf-score-vs
  • Scoring with smina
  • Scoring with gnina
  • Scoring with AutoDock4
  • Scoring with Vinandro
  • Scoring with vina
  1. VFVS 2.0

Supported docking programs and scoring functions

PreviousInput & Output DatabasesNextUsing VFVS 2.0

Last updated 2 years ago

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 .

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 .

  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 .

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 .

  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 .

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

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

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

ADFR

  1. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=adfr

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

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

GlideHTVS

  1. Installation of the external docking program not required.

  2. In all.ctrl file, set

ligand_library_format=smi
docking_scenario_programs=GlideHTVS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

QuickVina_gpu

  1. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_gpu

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

rDock

  1. In all.ctrl file, set

ligand_library_format=mol2
docking_scenario_programs=rDock

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

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

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

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

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

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

Vina-Gpu

  1. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_w_gpu

Vina-Gpu-2.0

  1. In all.ctrl file, set

ligand_library_format=pdbqt
docking_scenario_programs=qvina_w_gpu

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

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

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

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

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

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

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

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

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 .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

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

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

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

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

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

For an example of theconfig.txt file, please refer to .

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

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

For an example of theconfig.txt file, please refer to .

the VituralFlow 2.0 github repository
here
the VituralFlow 2.0 github repository
here
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
here
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
here
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
download instructions
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
here
the VituralFlow 2.0 github repository
here
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository
the VituralFlow 2.0 github repository