Re: [AMBER] Problem from ala scanning

From: Bill Miller III <>
Date: Fri, 30 Apr 2010 10:52:37 -0400

This means there is an inconsistency somewhere in your mutant topology
files. The alanine mutation was only in the ligand, correct? So does that
mean that receptor_prmtop and mutant_receptor_prmtop are the same files? Did
tleap provide any errors or warnings when you were making the mutant
prmtops? Have you checked both the mutant_complex_prmtop and the
mutant_ligand_prmtop to make sure the correct residue was changed from LYS
to ALA? The mutation should be present in *both* of these prmtops if the
mutation is in the ligand. Without seeing the prmtops or the leap.log it is
difficult to pinpoint the exact location of the problem. These are simply
suggestions for you to try to find the error.

Good luck! I hope this helps.


On Fri, Apr 30, 2010 at 10:31 AM, Rilei Yu <>wrote:

> Dear amber users,
> When I try to perform ala scanning on my system, an error appeared in my
> output file: WARNINGS: Invalid alanine scanning topology file(s)! It will
> not be performed.
> As a result, no mutational energy was calculated.
> I read the manual carefully, and try to delete the side chain of Lys to ALA
> (only one mutation on the ligand). The name is also changed. Then the
> mutant_ligand_prmtop, mutant_complex_prmtop and mutant_receptor_prmtop were
> produced using leap. Can anyone tell what is wrong?
> I appreciated for your help!
> Rilei Yu
> _______________________________________________
> AMBER mailing list
AMBER mailing list
Received on Fri Apr 30 2010 - 08:00:09 PDT
Custom Search