Binding free energy from native AMBER files¶
This example calculates the binding free energy of the RAS-RAF protein-protein complex directly from AMBER topologies and a trajectory. It uses amber_MMPBSA, so no GROMACS structure, index, trajectory, or topology is required.
-
Protocol
Single trajectory
-
Input format
Native AMBER files
-
Solvent model
GB-HCT (
igb=1) -
Bundled test
gmx_MMPBSA_test -t 25
Representative system
This tutorial uses a protein-protein complex to demonstrate the native AMBER workflow. Native AMBER support is not limited to protein-protein systems: other receptor-ligand compositions can be analyzed when their AMBER topologies, trajectories, and component selections are compatible with amber_MMPBSA. Individual calculation methods may impose additional restrictions.
Before you begin¶
The manual workflow uses the following files and residue selections:
-
Calculation settings
mmpbsa.in(-i) -
Complex
Topology
ras-raf_complex.prmtop(-cp) and trajectoryprod_complex.mdcrd(-ct) -
Component topologies
Receptor
ras.prmtop(-rp) and ligandraf.prmtop(-lp) -
Component selections
Receptor mask
:1-166and ligand mask:167-242(-cm)
The folder also contains ras-raf_complex.inpcrd, a coordinate snapshot matching the complex topology. It is useful for inspection and provenance but is not required by the command below. See the complete amber_MMPBSA reference for all supported inputs and 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 native AMBER example as a ZIP archive.
Extract the archive, change to the AMBER 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 concise mmpbsa.in shown first below. The all-options version was generated with amber_MMPBSA --create_input gb 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 native AMBER MM/GBSA calculation.
| mmpbsa.in | |
|---|---|
Keep in mind
This five-frame calculation provides a practical, runnable introduction to native AMBER inputs. For production work, verify sampling convergence and adjust the frame range, implicit-solvent model, salt concentration, and other system-dependent settings. See the available input-file options before extending the protocol.
How this example works¶
The ST approximation evaluates the complex, receptor, and ligand using coordinates from the same five trajectory frames. The complex masks assign residues 1-166 to RAS and residues 167-242 to RAF. The supplied ras.prmtop and raf.prmtop provide the component parameters; if -rp or -lp is omitted, amber_MMPBSA instead extracts that component topology from the complex.
The three bundled topologies store mbondi radii. This example therefore uses the conventionally matched GB-HCT model (igb=1) with a salt concentration of 0.10 M. Native AMBER topologies already contain atomic parameters, charges, radii, and screening values. The legacy topology-preparation settings do not rebuild or replace those data during the normal native AMBER workflow.
Native topology radii¶
amber_MMPBSA preserves the RADII, SCREEN, and RADIUS_SET data stored in each input topology. If the selected igb does not conventionally match the stored radius set, the program warns but does not alter the topology. Choose the desired radius set when creating the topology in tleap; see the amber_MMPBSA reference for conventional igb/radius pairings and precedence details.
Multiple-trajectory calculations¶
For the MT approximation, provide the unbound receptor topology, mask, and trajectory with -rp, -rm, and -rt, and the corresponding ligand inputs with -lp, -lm, and -lt. The selected complex, receptor, and ligand trajectories must contain the same number of frames after applying startframe, endframe, and interval.
When multiple files are supplied to one trajectory option, they are concatenated in command-line order and analyzed as one pooled trajectory. They are not treated as independent replicas.
Mask selections¶
Native AMBER masks in this workflow select whole residues. Non-contiguous residue ranges are supported; for example, the following selection assigns residues 1-120 and 181-260 to the receptor and residues 121-180 to the ligand:
Atom-name and boolean mask expressions are not accepted for these component selections.
Explicit receptor waters¶
For an explicit-water AMBER calculation, supply a matching solvated -cp/-ct pair, omit -rp and -lp, and set explicit_waters, explicit_waters_mask, and solvated_trajectory=1 in the input. The -cm masks must select only the solute components. Selected waters are assigned to the receptor, while the ligand topology remains dry. See the explicit-water details in the command reference for supported models and water-selection behavior.
Expected outputs¶
A successful calculation produces:
FINAL_RESULTS_MMPBSA.dat: the MM/GBSA summary and binding-energy statistics.FINAL_RESULTS_MMPBSA.csv: the per-frame energy terms requested with-eo.
Analyze the results¶
Open the result with gmx_MMPBSA_ana for interactive inspection and plotting. See the gmx_MMPBSA_ana documentation for usage details.
Created: July 11, 2026 06:19:03