Re: [AMBER] idecomp does not work for canonical-residues

From: Jason Swails <jason.swails.gmail.com>
Date: Sun, 27 Oct 2013 12:05:54 -0400

On Sun, Oct 27, 2013 at 9:01 AM, kurisaki <
kurisaki.ncube.human.nagoya-u.ac.jp> wrote:

> Dear Jason,
>
> Thank you for your reply.
> As you pointed out,
> Energies for TDC and SDC were calculated.
> (I just saw BDC...).
>
> > The total and sidechain energies, however, should be non-zero.
> Yes, I found that total and sidechain energies showed the same value.
>
> Now..
> >The backbone is only defined for common residues, so the BDC values for
> the
> ligand.
> If I contains ligand in protein, will sander give backbone energies for
> BDC?
>

The backbone energies will be computed for all 'backbone' atoms. These
include the C, Calpha, O, and N atoms of amino acids, for instance. I
believe these atoms are hard-coded into the sander source code, so if you
want sander to designate some atoms of your as 'backbone' and the rest as
'sidechain', you'll have to modify the appropriate parts of
$AMBERHOME/src/sander/group.F90 to do so.


> Or is there any alternative way to set backbone information
> to obtain BDC for ligand?
>

The total decomposition energy will not change if you designate some atoms
as 'backbone' (the sidechain contributions will decrease by the amount of
the backbone contributions). If, for whatever reason, you want to separate
the contribution from a 'backbone', you will have to modify the source code
as I mentioned. As a warning, this part of the code looks a bit obfuscated
to me (it is quite old), so modifying it may be challenging.

HTH,
Jason

-- 
Jason M. Swails
BioMaPS,
Rutgers University
Postdoctoral Researcher
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Sun Oct 27 2013 - 09:30:02 PDT
Custom Search