Alanine scanning¶
This example estimates the effect of mutating receptor residue Tyr23 to alanine in a protein-protein complex. It uses the same solvated simulation, frame range, and GB-Neck2 model as the decomposition and stability examples. The multiple-mutant example below extends this calculation to two receptor residues mutated together.
-
Analysis
Computational alanine scanning
-
Mutation
Single: Tyr23 to Ala
Multiple: Thr13 + Tyr23 to Ala or Gly
-
Solvent model
GB-Neck2 (
igb=8) -
Bundled test
gmx_MMPBSA_test -t 12
Before you begin¶
The manual workflow uses the following files and selections:
-
Calculation settings
mmpbsa.in(-i) -
GROMACS system
Structure
com.tpr(-cs) and topologytopol.top(-cp). Keep thetoppardirectory containing the referenced*.itpfiles besidetopol.top. -
Trajectory
PBC-corrected and fitted trajectory
com_traj.xtc(-ct) -
Molecular selections
Index
index.ndx(-ci) with theSOLU_chain1andSOLU_chain2groups (-cg)
The folder includes the solvated system snapshot com.pdb, matching the corresponding files in the decomposition and stability examples. The 608-atom reference.pdb structure (-cr) preserves the chain ID and residue number used by mutant_res="R:23". See the complete command-line reference for all options.
Run the example¶
Run the bundled test¶
The quickest way to reproduce this example is through the test runner:
See the gmx_MMPBSA_test documentation for download, selection, and cleanup options.
Run it manually¶
Download the Alanine Scanning example as a ZIP archive.
Extract the archive, change to the Alanine_scanning directory, and choose either the serial or MPI command. You can also view the example files on GitHub before downloading them.
Configure the calculation¶
The example uses the minimal mmpbsa.in shown first below. The all-options version was generated with gmx_MMPBSA --create_input gb ala and then adapted with the same example-specific values. The concise block is the runnable starting point; the generated block includes additional options and defaults, so the two blocks are not textually identical. Both blocks therefore describe the same MM/GBSA alanine-scanning calculation.
Keep in mind
This input provides a practical starting point and can serve as the basis for production calculations. Review the available input-file options, their accepted values, and adjust settings that depend on your system or protocol. Additional sample inputs are available here.
How this example works¶
The single-trajectory calculation selects the 608-atom protein-protein solute from the solvated source trajectory. It processes frames 1 through 10 with GB-Neck2 (igb=8), the matching mbondi3 radii (PBRadii=4), and a salt concentration of 0.15 M.
mutant_res="R:23" identifies Tyr23 in receptor chain R, and mutant="ALA" creates the corresponding alanine variant without requiring a separately prepared mutant topology. With mutant_only=0, the calculation evaluates both the original and mutant systems. Because tyrosine is classified as polar, cas_intdiel=1 applies intdiel_polar=3 to the relevant GB calculations.
Run a multiple alanine or glycine mutant¶
To estimate the combined effect of two mutations, select Thr13 and Tyr23 together with mutant_res="R/13,23". Both residues are present in chain R of the supplied reference.pdb and belong to the receptor. With mutant="ALA", this produces the T13A/Y23A multiple alanine mutant. With mutant="GLY", it produces the T13G/Y23G multiple glycine mutant.
Make a separate copy of the example folder for each variant so its inputs and results stay together. Save one of the following inputs as mmpbsa_multiple.in in that folder. Both variants use the same trajectory frames, radii, salt concentration, and internal dielectric.
Multiple mutations require cas_intdiel=0; choose the dielectric explicitly in the solvent-model namelist. Here, intdiel=3 matches the dielectric applied to the single Tyr23 mutation above. For comparisons with other single mutants, use the same explicit dielectric and the same frame range in every calculation. All selected residues must belong to one component and use the same target, either ALA or GLY.
From the folder containing the chosen input, run:
gmx_MMPBSA -O \
-i mmpbsa_multiple.in \
-cs com.tpr \
-ct com_traj.xtc \
-ci index.ndx \
-cg SOLU_chain1 SOLU_chain2 \
-cp topol.top \
-cr reference.pdb \
-o MULTIPLE_MUTANT_RESULTS.dat \
-eo MULTIPLE_MUTANT_RESULTS.csv
For MPI, prepend mpirun -np 2 to the same command.
Interpret the multiple-mutant result¶
With mutant_only=0, the output includes the original system, the multiple mutant, and their difference. The mutation effect is the change in binding energy for both substitutions together, relative to the original system. This run does not calculate separate T13A and Y23A effects (or T13G and Y23G effects); run each selection separately if those individual effects are needed. The combined effect need not equal the sum of the individual effects.
The program generates mutant topologies and trajectory coordinates from the original system. Check that both selected residues have become ALA or GLY in the generated mutant structures before interpreting the result.
Verify the mutation selection¶
Residue selection depends on stable chain IDs and residue numbers. Supplying reference.pdb with -cr makes the mapping explicit while com.pdb retains the complete solvated snapshot for consistency. Confirm the selected mutation in _GMXMMPBSA_COM_FIXED.pdb and the generated mutant structures before interpreting results.
One run can mutate a single residue or change several residues together to produce a multiple alanine mutant or a multiple glycine mutant. It does not independently scan each selected residue. mutant_res also accepts CHAIN/RESNUM notation and insertion codes as described in the alanine-scanning input options.
Expected outputs¶
A successful calculation produces:
FINAL_RESULTS_MMPBSA.dat: the original, mutant, and alanine-scanning energy summaries.FINAL_RESULTS_MMPBSA.csv: the per-frame energy terms requested with-eo.
Analyze the results¶
Open the results with gmx_MMPBSA_ana for interactive inspection and plotting. See the gmx_MMPBSA_ana documentation for usage details.
Created: February 8, 2021 07:10:13