Lesson · 40 min · Free
Running AutoDock Vina
Running AutoDock Vina body { font-family: sans-serif; line-height: 1.6; margin: 20px; } h1, h2 { color: #2c3e50; } pre { background-color: #ecf0f1; padding: 15px; border-radius: 5px; overflow-x: auto; } code { font-famil
Running AutoDock Vina
Welcome to the practical session on running AutoDock Vina! In this lesson, we will walk through the essential steps to execute a docking simulation using AutoDock Vina. By the end of this module, you will be able to set up and run a basic docking job, interpret its output, and understand the core parameters involved. This is a crucial step in predicting ligand-protein interactions, a fundamental aspect of drug discovery and development. Before we begin, ensure you have AutoDock Vina installed on your system and that the executable is accessible from your command line or terminal. We assume you have already prepared your receptor and ligand files in PDBQT format, as discussed in previous lessons. The PDBQT format is critical because it contains atomic partial charges and desolvation parameters necessary for Vina's scoring function.
The Vina Configuration File
AutoDock Vina is typically run using a configuration file (often named conf.txt or config.txt ). This file specifies all the necessary parameters for the docking run, including the receptor, ligand, and the search space (defined by a grid box). Using a configuration file makes your docking runs reproducible and easier to manage, especially when performing multiple simulations or parameter optimizations. Here's a breakdown of the essential parameters you'll include in your configuration file: receptor : Path to your prepared receptor PDBQT file. ligand : Path to your prepared ligand PDBQT file. center_x , center_y , center_z : The X, Y, and Z coordinates of the center of your docking box. These coordinates define the central point around which Vina will search for binding poses. You can determine these coordinates using molecular visualization software (e.g., PyMOL, ChimeraX) by selecting residues in the active site. size_x , size_y , size_z : The dimensions (in Angstroms) of your docking box along the X, Y, and Z axes. A larger box increases the search space but also increases computational time. A typical box size ranges from 20 to 30 Angstroms per side. out : The desired output file name for the docked poses (e.g., ligand_docked.pdbqt ). This file will contain multiple predicted poses of the ligand within the receptor binding site, ranked by their binding affinities. log : An optional parameter to specify a log file for Vina's output (e.g., vina_log.txt ). This file records details about the docking process, including the calculated binding affinities and the parameters used. cpu : An optional parameter to specify the number of CPU cores to use. Utilizing more cores can significantly speed up the docking process. num_modes : An optional parameter specifying the maximum number of binding modes to generate. The default is 9. energy_range : An optional parameter specifying the maximum energy difference between the best binding mode and the worst binding mode displayed (in kcal/mol). The default is 3. Let's create a sample configuration file named conf.txt : # conf.txt receptor = receptor.pdbqt ligand = ligand.pdbqt center_x = 15.0 center_y = 20.0 center_z = -5.0 size_x = 25.0 size_y = 25.0 size_z = 25.0 out = ligand_docked.pdbqt log = vina_output.log cpu = 8 num_modes = 10 energy_range = 4 In this example, we assume receptor.pdbqt and ligand.pdbqt are in the same directory as your conf.txt file. The center coordinates (15.0, 20.0, -5.0) and box sizes (25.0 Angstroms in all dimensions) are illustrative; you would replace these with values specific to your target protein's active site.
Executing AutoDock Vina
Once your configuration file is ready, you can run AutoDock Vina from your terminal or command prompt. Navigate to the directory containing your receptor, ligand, and configuration files. The basic command structure is straightforward: vina --config conf.txt If the AutoDock Vina executable ( vina ) is not in your system's PATH, you might need to specify its full path, for example: /path/to/your/vina --config conf.txt . Upon execution, Vina will display progress updates in the terminal and write more detailed information to the specified log file ( vina_output.log in our example). The output file ( ligand_docked.pdbqt ) will contain the predicted binding poses, each separated by MODEL and ENDMDL markers, along with their calculated binding affinities. The poses are typically ordered from the most favorable (lowest binding affinity, highest negative value) to the least favorable.
Interpreting the Output
The vina_output.log file will contain a summary table similar to this: # Vina output log snippet ... ############################################################################ # Search space (Angstroms) : # center_x = 15.0, center_y = 20.0, center_z = -5.0 # size_x = 25.0, size_y = 25.0, size_z = 25.0 # Ligand: ligand.pdbqt # Receptor: receptor.pdbqt # # Exhaustiveness: 8 # Number of CPU cores used: 8 # Number of modes requested: 10 # Energy range: 4.0 ############################################################################ ... (some progress messages) ... mode | affinity | dist from best mode | (kcal/mol) | rmsd l.b. | rmsd u.b. -----+------------+-----------+---------- 1 -9.5 0.000 0.000 2 -9.1 1.254 1.678 3 -8.8 2.103 2.567 4 -8.5 3.456 3.987 5 -8.2 0.890 1.234 6 -8.0 4.567 5.123 7 -7.8 1.567 1.987 8 -7.5 6.123 6.789 9 -7.3 2.345 2.890 10 -7.0 7.012 7.567 The most important column here is 'affinity (kcal/mol)', which represents the predicted binding free energy. A more negative value indicates a stronger predicted binding affinity. The 'rmsd l.b.' and 'rmsd u.b.' columns refer to the Root Mean Square Deviation (RMSD) of the current pose relative to the best pose, providing an indication of structural similarity between different predicted binding modes. Lower RMSD values indicate greater similarity.
Key Takeaways
AutoDock Vina typically uses a configuration file to specify docking parameters. Essential parameters include receptor and ligand paths, grid box center and size, and output file names. The grid box defines the search space for ligand binding. The command vina --config conf.txt executes the docking simulation. Output includes docked ligand poses in PDBQT format and a log file with binding affinities. More negative binding affinity values indicate stronger predicted binding.
Practice Exercise
Imagine you are tasked with docking a novel small molecule ( drugX.pdbqt ) to an active site of a specific protein ( target_protein.pdbqt ). You have determined the active site's geometric center to be at X=35.2, Y=10.5, Z=-12.8, and you want to define a cubic docking box with sides of 22 Angstroms. You need to generate 15 binding modes and save the output to drugX_docked.pdbqt and the log to drugX_vina.log . Create the appropriate configuration file ( my_docking_conf.txt ) and write down the command you would use to run AutoDock Vina for this scenario.
Watch the full lesson — free
This topic is part of Molecular Docking with AutoDock Vina, a complete AI-narrated video course. Press play once and watch the entire lecture like a movie.
Start the course free →