Skip to content

Commit 33db834

Browse files
authored
Update README.md
Added documentation for flexible docking.
1 parent 050d230 commit 33db834

File tree

1 file changed

+13
-8
lines changed

1 file changed

+13
-8
lines changed

README.md

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
A.V.A is designed to automate the docking of multiple ligands to a single target protein in AutoDock Vina. A.V.A automates large parts of the workflow associated with ligand docking including:
44

5-
- Preparing ligand config file for AutoDock Vina
5+
- Preparing ligand config files for AutoDock Vina
66
- Running AutoDock Vina
77
- Producing technical replicates of ligand docking simulations
88
- Visualising ligand docking simulations
@@ -13,7 +13,7 @@ Dependencies for A.V.A can be found in requirements.txt. A.V.A also requires Py
1313

1414
### Future Updates
1515
Future updates to A.V.A may include:
16-
- Introducing flexible residues in the target protein
16+
- Introducing flexible residues in the target protein (added 14/02/22, v1.1.0)
1717
- Docking for multiple target proteins to a set of ligands
1818

1919
## Installation on MacOSX and Linux
@@ -42,7 +42,7 @@ Alternatively, A.V.A can be run from an IDE.
4242
In this scenario, we will run predict how 3 ligands (Ligand1, Ligand2 & Ligand3) bind to the active site of the target protein (ProteinX). To ensure reproducibility of results, each ligand docking will be run 3 times with 3 unique seeds: 22, 495 & 1,000.
4343

4444
### Pre-processing for A.V.A
45-
Before running A.V.A, all files must be prepared in the appropriate format for AutoDock Vina (.pdbqt files). This must be done for ligands and the target protein. Additionally, the size and location of the search space must be determined for the target protein. These tasks can be achieved using AutoDock Tools.
45+
Before running A.V.A, all files must be prepared in the appropriate format for AutoDock Vina (.pdbqt files). This must be done for ligands and the target protein. Additionally, the size and location of the search space must be determined for the target protein. These tasks can also be achieved using AutoDock Tools.
4646

4747
In our scenario, we will create the 4 following files: Ligand1.pdbqt, Ligand2.pdbqt, Ligand3.pdbqt & ProteinX.pdbqt . Using AutoDock Tools, we identified the co-ordinates for active site (10,-5,88) and the dimensions of the box needed to cover the area (20, 20, 20).
4848

@@ -53,13 +53,18 @@ Working directory:
5353
- The path to the directory containing all pre-processed files.
5454
- e.g MyWorkingDirectory
5555

56-
Ligand(s):
57-
- The file name for each ligand separated by a space
58-
- e.g: Ligand1.pdbqt Ligand2.pdbqt Ligand3.pdbqt
59-
6056
Receptor:
6157
- The file name of the target protein
6258
- e.g: ProteinX.pdbqt
59+
60+
(Optional) Flexible Receptor:
61+
- A.V.A will prompt you to choose whether you want to perform flexible docking. If so provide file name of the flexible receptor.
62+
- e.g: ProteinX-flex.pdbqt
63+
- If selected, exhaustiveness is set to 32 by default. (This option may dramatically slow down run time)
64+
65+
Ligand(s):
66+
- The file name for each ligand separated by a space
67+
- e.g: Ligand1.pdbqt Ligand2.pdbqt Ligand3.pdbqt
6368

6469
Coordinates:
6570
- The coordinates of the search area separated by spaces formatted as x y z
@@ -72,7 +77,7 @@ Seed(s):
7277
- The integers used to seed the docking experiment(s) separated by spaces
7378
- e.g: 20 400 1000
7479
- The default seed used is 0, if left blank
75-
80+
7681
Autodock Vina will begin running as soon as all parameters are provided.
7782

7883
### A.V.A Outputs

0 commit comments

Comments
 (0)