Thank you, guys. My problem has been solved. AutoMR in CCP4 removed the
insertion code. But I used it before, and it did not mess up with the
insertion code at those times.
Rain
On Thu, Jun 27, 2013 at 12:56 PM, Ian Tickle wrote:
> Last time I checked pdbset doesn't renumber the LINK, CISPE
Last time I checked pdbset doesn't renumber the LINK, CISPEP, SSBOND
records at the same time (but maybe it was fixed).
-- Ian
On 26 June 2013 07:41, Francois Berenger wrote:
> I think pdbset from CCP4 can renumber a PDB and hence get rid of the uggly
> insertion codes.
>
>
> On 06/26/2013 03:
-Ursprüngliche Nachricht-
Von: CCP4 bulletin board [mailto:CCP4BB@JISCMAIL.AC.UK] Im Auftrag von Francois
Berenger
Gesendet: Mittwoch, 26. Juni 2013 08:42
An: CCP4BB@JISCMAIL.AC.UK
Betreff: Re: [ccp4bb] AW: [ccp4bb] insertion code problem
I think pdbset from CCP4 can renumber a PDB and hence get
I think pdbset from CCP4 can renumber a PDB and hence get rid of the
uggly insertion codes.
On 06/26/2013 03:33 PM, herman.schreu...@sanofi.com wrote:
Dear Rain,
Insertion codes are still a sore point for many CCP4 programs and one of
the reasons I prefer Buster over Refmac. Refmac5 does not re
Dear Rain,
Insertion codes are still a sore point for many CCP4 programs and one of the
reasons I prefer Buster over Refmac. Refmac5 does not remove insertion codes so
I suspect the problem was with autoMR. The easiest is to superimpose your
search model with insertion codes onto the pdb file w
