[chimera-dev] Moving atoms from HETATM to ATOM entries

Eric Pettersen pett at cgl.ucsf.edu
Fri Jan 24 11:06:10 PST 2014

Hi JD,
	Perhaps this could be improved, but the decision over whether a residue is written with ATOM or HETATM records depends on whether the residue type is considered standard or not.  Control over this is provided by chimera.PDBio's addStandardResidue and removeStandardResidue functions.  So in your case change:

a.residue.isHet = False



	Of course, this will write all residues of that type using HETATM records, not just those in the current selection.  Therefore you may instead need to change the type of the modified residues and not bother with removeStandardResidue.  Basically it is impossible to make Chimera write some residues of a particular type using ATOM records and others of the same type using HETATM records into the same file.


                        Eric Pettersen
                        UCSF Computer Graphics Lab

On Jan 24, 2014, at 12:49 AM, Jean-Didier Maréchall wrote:

> Dear all, 
> I am working with some chemically modified residues. For consistency with MMTK, I have to move non-natural atoms in the ATOM list of the pdb. I would like to do that directly from chimera and not editing the pdbfile. 
>  I thought that I could alter the heteroatom value of chimera's residues to get there. But whether this is not the right attribute  or I miss something. 
> What I do is:
> build my system, select the atoms of the non-natural and  natural part of the residue. Make a new residue and then, having selected it:
> atoms=chimera.selection.currentAtoms()
> for a in atoms:
>      a.residue.isHet=False
> This indeed changes the isHet attribute but when saving the pdb, the residue is in the  HETATM field. 
> Any pointer?
> Best,
> JD

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://plato.cgl.ucsf.edu/pipermail/chimera-dev/attachments/20140124/904f82c0/attachment.html>

More information about the Chimera-dev mailing list