Like the Chimera AutoDock Vina tool, the vina command runs single-ligand docking calculations with AutoDock Vina.
** Requires installing AutoDock Vina locally **
As of 4/30/2020, the AutoDock Vina web service from the National Biomedical Computation Resource (NBCR) has been discontinued. Without the web service, the vina command will no longer work unless you download and install the AutoDock Vina program on your own computer and use the backend local and location options of the command.
|The vina command is a simplified interface that allows a limited range of options and parameter values. For more intensive sampling, as needed for most research applications, or access to other options such as ligand database search, we recommend running the locally installed copy of AutoDock Vina directly (not using Chimera). Chimera can still be used to view the output. (Other limitations...)|
Users should cite:
AutoDock Vina: improving the speed and accuracy of docking with a new scoring function, efficient optimization, and multithreading. Trott O, Olson AJ. J Comput Chem. 2010 Jan 30;31(2):455-61.The receptor and ligand structures should be opened as separate models in Chimera and specified with the receptor and ligand keywords, respectively. The entire models containing the specified atoms will be used.
If the receptor contains MSE (selenomethionine) residues, incomplete side chains, or atoms with alternate locations, running Dock Prep beforehand to correct those issues is recommended. The vina command runs accessory scripts locally to further prepare the structures, such as to add hydrogens if they have not been added already with Chimera. These accessory scripts were originally available for previous versons of AutoDock.
Docking results will be shown automatically in ViewDock. Please see the AutoDock Vina manual for a description of the output values.
Option keywords for vina can be truncated to unique strings and their case does not matter. A vertical bar “|” designates mutually exclusive options, and default values are indicated with bold. Synonyms for true: True, 1. Synonyms for false: False, 0.
Pathname (location and filename prefix) of output files. If the run is successful, the following files will be generated:
If name is not specified, a temporary filename prefix and location will be used.
- name - docking results in PDBQT (Protein Data Bank with partial charge Q and atom type T) format, automatically read into ViewDock when the calculation finishes
- name.receptor.pdb - receptor PDB file from Chimera, input to the AutoDock receptor preparation script
- name.receptor.pdbqt - processed receptor in PDBQT format, input to AutoDock Vina
- name.ligand.pdb - ligand PDB file from Chimera, input to the AutoDock ligand preparation script
- name.ligand.pdbqt - processed ligand in PDBQT format, input to AutoDock Vina
- name.conf - AutoDock Vina configuration file
prep true | false
Whether to run only the preparation steps, not AutoDock Vina. If true, the output will not include the docking results file.
wait true | falseThe default box in which to sample ligand positions will enclose the entire receptor, with extra space on all sides. If the region of interest is smaller, the desired box center and size should be specified to allow for a more efficient search. Both must be supplied; if only the center or only the box size is specified, it will be ignored.
Whether to wait for the calculation to finish before exiting Chimera. Must be set to true for running vina with Chimera in nogui mode.
In the receptor coordinate system, location of the center of the box in which to sample ligand positions.
search_size xlen,ylen,zlenSettings for the AutoDock receptor preparation script:
In the receptor coordinate system, dimensions along X, Y, and Z of the box in which to sample ligand positions.
r_addh true | false
Whether to add hydrogens in Chimera (see addh) before calling the script. The receptor prep script will check for hydrogens and add them if they are missing. AutoDock Vina needs the polar (potentially H-bonding) hydrogens to identify atom types for scoring purposes.
r_nphs true | false
Whether to merge charges and remove nonpolar hydrogens. Note AutoDock Vina does not use charges or nonpolar hydrogens, so this setting is not expected to affect results except for the presence or absence of nonpolar hydrogens in the processed receptor.
r_lps true | false
Whether to merge charges and remove lone pairs. Note AutoDock Vina does not use charges or lone pairs, so this setting is not expected to affect results except for the presence or absence of lone pairs in the processed receptor (and there may not have been any lone pairs to start with).
r_waters true | false
Whether to remove water residues.
r_nonstdres true | false
Whether to remove chains composed entirely of residues other than the 20 standard amino acids.
r_nonstd true | falseSettings for the AutoDock ligand preparation script (see limitations):
Whether to remove all residues other than the 20 standard amino acids.
The ligand prep script will check for hydrogens and add them if they are missing. AutoDock Vina needs the polar (potentially H-bonding) hydrogens to identify atom types for scoring purposes.
l_nphs true | false
Whether to merge charges and remove nonpolar hydrogens. Note AutoDock Vina does not use charges or nonpolar hydrogens, so this setting is not expected to affect results except for the presence or absence of nonpolar hydrogens in the ligand output files.
l_lps true | falseDocking parameters:
Whether to merge charges and remove lone pairs. Note AutoDock Vina does not use charges or lone pairs, so this setting is not expected to affect results except for the presence or absence of lone pairs in the ligand output files (and there may not have been any lone pairs to start with).
Maximum number of binding modes to generate (default 9).
Thoroughness of search, roughly proportional to time (default 8).
energy_range rangeExecutable location:
Maximum difference in score (default 3.0 kcal/mol); binding modes with scores not within range of the best score will be discarded.
backend opal | local
Whether to use an Opal web service (default) or a locally installed executable.
location opal-URL | local-path
Depending on the backend setting, the URL of the web service (default is the URL for the service provided by the NBCR) or the pathname of the local executable. Since the NBCR web service has been retired, users would need to download AutoDock Vina and use both the backend local and location options.