Re: [ccp4bb] shelx anamalous data

2013-11-17 Thread Tim Gruene
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear Yarrow,

the data in the phs-file are not the original data, they are density
modified, which includes the amplitudes. If you convert them to mtz,
you should really know what you are doing - you might end up
depositing a PDB file refined against modified data sets.

Best,
Tim

On 11/16/2013 11:16 AM, Eleanor Dodson wrote:
 It is easy enough if you still ant to do it.
 
 I would feed both into f2mtz separately to make a mysadIplus.mtz
 and a mysadImin.mtz then use CAD to combine and change the default
 labels to something like I(+) SIGI(+) and I(-) SIGI(-)
 
 But as George says Why do you want it? That will change the way you
 proceed.
 
 Eleanor On 14 Nov 2013, at 21:08, George Sheldrick wrote:
 
 I'm not sure why you want to do that. If you wish to look at a
 map or poly-Ala trace from SHELXE, just read the .pdb and then
 .phs files into Coot directly. If you want to use them to make
 pictures with PYMOL, use Tim Gruene's SHELX2map. For further
 information please go to the SHELX homepage (Google knows where
 it is).
 
 George
 
 On 11/14/2013 10:09 PM, Yarrow Madrona wrote:
 I'm sorry,
 
 I have not used shelx before and didn't realize in my last post
 that the anamolous data is kept separate. I am planning on
 converting both the mysad.phs and mysad.pha to mtz files and
 then merge them. However, I am not sure of the column lables in
 mysad.pha. Does anyone know how to get this info?
 
 -Yarrow
 
 
 
 -- Prof. George M. Sheldrick FRS Dept. Structural Chemistry, 
 University of Goettingen, Tammannstr. 4, D37077 Goettingen,
 Germany Tel. +49-551-39-33021 or -33068 Fax. +49-551-39-22582
 

- -- 
Dr Tim Gruene
Institut fuer anorganische Chemie
Tammannstr. 4
D-37077 Goettingen

GPG Key ID = A46BEE1A
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFSiSXeUxlJ7aRr7hoRAs3BAJ4qX4aQNx3FEMVZJQnT47dus4C08ACdHB9C
XZf6c/Ljr7bKlmbtwyT4sZQ=
=r68S
-END PGP SIGNATURE-


[ccp4bb] BCA Winter Meeting 2013 (second flyer with correct deadline).

2013-11-17 Thread Cooper, Jon
BCA Winter Meeting 2013


Title: New X-ray Developments and Macromolecular Structures in the Bragg 
Centenary Year.

Venue: King's College London (New Hunt's House, Guy's Campus, London Bridge, 
SE1 1UL).

Date: 16th December 2013.

Organisers: The Randall Division of Cell  Molecular Biophysics, KCL.

 - - - - - - -

Invited speakers include:

Bonnie Wallace, Birkbeck College London. Voltage-gated Sodium Channels: 
Complementary Insights into Structure and Function and Disease using 
Crystallography and Spectroscopy

David Stuart, University of Oxford. In silico drug design - perhaps it really 
works

James Naismith, St. Andrew's University. The UK plans for XFEL: what it can do 
for crystallography

Ivan Laponogov, King's College London. Structure of an 'open' clamp type II 
topoisomerase-DNA complex provides a mechanism for DNA capture and transport

David Leys, University of Manchester. Structural studies on poly-ADP-ribose 
glycohydrolases

Stefano Pernigo, King's College London. Structural basis of kinesin-1:cargo 
interaction

Liz Carpenter, SGC Oxford. A novel structure for a nuclear membrane zinc 
metalloprotease involved in premature ageing diseases

 - - - - - - - -

For details and registration, please visit the meeting website:

http://crystallography.org.uk/bsg-winter-meeting-2013/

Registration deadline: Wednesday 11 December 2013.

 - - - - - - - -

Contacts: Dr Mark Sanderson (mark.sander...@kcl.ac.uk) and Dr Yu Wai Chen 
(yu-wai.c...@kcl.ac.uk)



Re: [ccp4bb] Problematic PDBs

2013-11-17 Thread MARTYN SYMMONS
Hmm
So the backstory for the problematic ligand R12 in this thread is that a 
sharp-eyed worker at the wwPDB recently spotted that there was an error 
compared with the original 1999 paper. Correcting the R12 ligand is a friendly 
gesture from the PDB as it appears that the error must have been the authors' - 
the atom correcting the R12 ligand has been inserted by the PDB staff rather 
than retreived from a deposited structure.
 
It is a shame the same helpful approach is not always applied. One current 
example I spotted is a separate 'problematic ligand' 5AX which has been added 
by the wwPDB to at least four other authors' entries, starting in 2006 with the 
latest in 2009. 
 
5AX is basically a fragment ligand which the PDB software produces if a NAG has 
wandered too far from its Asn sidechain during refinement. If 5AX is generated 
during the PDB processing of a deposition, then it really should be highlighted 
for the authors as a geometric issue - rather than, as in these cases, being 
simply added to the coordinates. 
 
Reading the authors' papers for the 5AX-containing entries makes it clear that 
they never expected anything other than NAG to appear in their deposited 
coordinates.
 
And given its artifactual production during deposition, 5AX should never have 
'escaped into the wild'. 
 
So if a retrospective fix can be applied to R12 (which similar in lacking an 
atom) then it seems to me that, in fairness, a clean up of the 5AX entries 
should be arranged. 
 
Yours (not holding his breath),
Martyn
 
 

  


 From: Rachel Kramer Green kra...@rcsb.rutgers.edu
To: CCP4BB@JISCMAIL.AC.UK 
Sent: Wednesday, 6 November 2013, 16:49
Subject: Re: [ccp4bb] Problematic PDBs
  


Dear Martyn,

wwPDB staff regularly reviews and remediates PDB data and related
  dictionaries such as the Chemical Component Dictionary (CCD).

As part of our on-going remediation efforts, the chemical
  components in the archive are regularly reviewed to ensure the
  correctness and the completeness of the chemical representation.
  Such reviews show that in some cases, the author has failed to
  provide a complete description of the chemistry. To address any
  such errors, the definitions are corrected. The chemical name and
  formula are changed in the PDB file, but the coordinates are not
  changed.

In the case of entry 3CBS, issues were found with the chemical
  component definition for its ligand R12. The methyl group was not
  in the deposited coordinates and it was missing from the original
  definition. In addition, the bond order in one of the
  carbon-carbon bonds was incorrectly defined. The CCD definition
  for R12 was updated in 2011 to add the methyl group and to correct
  the bond order based on information in the primary citation. The
  coordinates for this PDB entry were not changed. Therefore, in
  accordance with wwPDB policy, the file was not obsoleted.

Sincerely,
Rachel Green


 


  
Rachel Kramer Green, Ph.D. 
RCSB PDB 
kra...@rcsb.rutgers.edu 
  
  
Twitter: https://twitter.com/#!/buildmodels 
Facebook: http://www.facebook.com/RCSBPDB 
   
On 10/21/2013 6:28 AM, MARTYN SYMMONS wrote:
 
As a postscript it might be worth mentioning one problematic ligand that 
suggested to me a way to correct some of the errors mentioned in this thread 

R12 is indicated as 9-(4-HYDROXY-2,6-DIMETHYL-PHENYL)-3 in the  most 
recent Coot monomer library. But in the PDB ligand description it is 
9-(4-hydroxy-2,3,6-trimethylphenyl)-3,7-dimethylnona-2,4,6,8-tetraenoic acid 
with an additional carbon C16. To make a long story short this ligand was 
originally deposited missing this extra methyl goup in 1999 (as part of 3CBS) 
and then apparently updated in 2011 by the PDB. 

 
(the relevant lines in the cif are 
snip 
R12 C16 C16 C 0 1 N N N ?      ?      ?      -6.631 1.502  0.990  C16 R12 44  
R12 H1  H1  H 0 1 N N N ?      ?      ?      -6.602 1.511  2.080  H1  R12 45  
R12 H23 H23 H 0 1 N N N ?      ?      ?      -6.422 2.503  0.613  H23 R12 46  
R12 H24 H24 H 0 1 N N N ?      ?      ?      -7.619 1.186  0.656  H24 R12 47  
snip  

 
with the ? ? ? indicating that refined coordinates were not available at the 
time of the update. There was initially an explanation line at the end of the 
cif: 

 
snip 
R12 Other modification 2011-10-25 RCSB CS 'add missing methyl group, 
re-define bond order based on publication' 
snip 

 
But this has mutated for some reason (premature stop codon?) over the past 
year to the following. 

 
snip   
R12 Other modification 2011-10-25 RCSB  
snip 

 
Obviously the full correct ligand could not have been incorporated into the 
PDB entry coordinates without these undergoing a full obsolete - supersede 
process (somewhat embarrassing perhaps as one author is now a wwPDB PI ;) 

 
But it is frustrating for users of the PDB that in such cases easily 
correctable