JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCP4BB Archives


CCP4BB Archives

CCP4BB Archives


CCP4BB@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCP4BB Home

CCP4BB Home

CCP4BB  April 2014

CCP4BB April 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: crystallographic confusion [SEC=UNCLASSIFIED]

From:

"Edward A. Berry" <[log in to unmask]>

Reply-To:

Edward A. Berry

Date:

Sat, 19 Apr 2014 13:25:46 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (142 lines)

There are three places in a pdb file where resolution is defined.
Unfortunately by current conventions I believe they are all required
to show the same value. If one of them could be redefined to be
"effective resolution", with a comment to explain how that was
arrived at, it would take the pressure off of resolution cuttoff
to serve double duty as the principal indicator of quality.

I guess you can entitle your paper "2.2 A structure of XYZ" even if
the pdb file shows the resolution to be 1.92 with 22% completeness
in the last shell, which could appease some reviewers but make
problems with others.
eab

DUFF, Anthony wrote:
> I thought...  we had a definition for reportable resolution: The resolution at which <I/sig(I)> = 2, and completeness > 50%
>
> This reported resolution is not to be confused with data cutoff.  We give the software all the scaled and merged data and let it down-weight the weak data.  At the edge, we might happily have Rmerge=50%, multiplicity = 1.1, <I/sig(I)> = 1.  The resolution of the edge data should not be reported as the resolution of the data.
>
> This reportable resolution is actually useful in refinement.  Very very roughly, you are done when the R-factor equals reportable resolution divided by 10.  25% for 2.5A data.  15% for 1.5A data.
>
>
> Anthony Duff
>
> -----Original Message-----
> From: CCP4 bulletin board [mailto:[log in to unmask]] On Behalf Of Tom Peat
> Sent: Saturday, 19 April 2014 6:03 PM
> To: [log in to unmask]
> Subject: Re: [ccp4bb] crystallographic confusion
>
> As has been alluded to, people (and not just crystallographers) are looking for a simple number to indicate the quality of a structure.
> Unfortunately this doesn't exist, but it doesn't keep people from wanting such a number.
> Most crystallographers (I think) now agree that throwing data away is a bad idea and will make maps worse.
> The real question is not whether to throw data away, but what to call the resolution of a map/ structure.
> A structure that has been refined with data that is ~90% complete at 3.6 Angstrom resolution but that has 2% completeness at 2.8 Angstrom would be considered to be ?  (Just to pull one instance from the PDB).
> If we as crystallographers could agree to some definition as to what our arbitrary resolution number is, life would probably be easier for the non-crystallographers (as well as for the crystallographers in some instances- particularly in the process of reviewing papers).
>
> cheers, tom
>
>
> Tom Peat
> Biophysics Group
> CSIRO, CMSE
> 343 Royal Parade
> Parkville, VIC, 3052
> +613 9662 7304
> +614 57 539 419
> [log in to unmask]
> ________________________________________
> From: CCP4 bulletin board [[log in to unmask]] on behalf of William G. Scott [[log in to unmask]]
> Sent: Saturday, April 19, 2014 11:41 AM
> To: [log in to unmask]
> Subject: Re: [ccp4bb] crystallographic confusion
>
> Dear Arnon et al:
>
> My understanding of the Shannon/Nyquist sampling theorem is admittedly extremely rudimentary, but I think aliasing can result if an arbitrary brick-wall resolution cut-off to the data is applied.
>
> So let's say there are real data are to 2.0 Å resolution. Applying the 2.2 Å cutoff will result in aliasing artifacts in the electron density map corresponding to an outer shell reciprocal space volume equal but opposite to the cut out data.
>
> The alternative, which is to process and keep all the measured reflections, should help to minimize this.  An effective resolution can be calculated and quoted.  This becomes a significant problem with nucleic acids and their complexes, which often diffract with significant anisotropy.
>
> The idea that 85% completeness in the outer shell should dictate its rejection seems rather surprising and arbitrary. The aliasing artifacts in that case would probably be significant.  The map image quality, after all, is what we are after, not beautiful Table 1 statistics.
>
> Bill
>
>
> William G. Scott
> Professor
> Department of Chemistry and Biochemistry and The Center for the Molecular Biology of RNA University of California at Santa Cruz Santa Cruz, California 95064 USA http://scottlab.ucsc.edu/scottlab/
>
>
>
> On Apr 18, 2014, at 5:22 PM, Lavie, Arnon <[log in to unmask]> wrote:
>
>> Dear Kay.
>>
>> Arguably, the resolution of a structure is the most important number
>> to look at; it is definitely the first to be examined, and often the
>> only one examined by non-structural biologists.
>>
>> Since this number conveys so much concerning the quality/reliability
>> of the the structure, it is not surprising that we need to get this
>> one parameter right.
>>
>> Let us examine a hypothetical situation, in which a data set at the
>> 2.2-2.0 resolution shell has 20% completeness. Is this a 2.0 A
>> resolution structure?  While you make a sound argument that including
>> that data may result in a better refined model (more observations,
>> more restraints), I would not consider that model the same quality as
>> one refined against a data set that has >90% completeness at that resolution shell.
>>
>> As I see it, there are two issues here: one, is whether to include
>> such data in refinement?  I am not sure if low completeness
>> (especially if not
>> random) can be detrimental to a correct model, but I will let other
>> weigh in on that.
>>
>> The second question is where to declare the resolution limit of a
>> particular data set?  To my mind, here high completeness (the term "high"
>> needs a precise definition) better describes the true resolution limit
>> of the diffraction, and with this what I can conclude about the
>> quality of the refined model.
>>
>> My two cents.
>>
>> Arnon Lavie
>>
>> On Fri, April 18, 2014 6:51 pm, Kay Diederichs wrote:
>>> Hi everybody,
>>>
>>> since we seem to have a little Easter discussion about
>>> crystallographic statistics anyway, I would like to bring up one more topic.
>>>
>>> A recent email sent to me said: "Another referee complained that the
>>> completeness in that bin was too low at 85%" - my answer was that I
>>> consider the referee's assertion as indicating a (unfortunately not
>>> untypical case of) severe statistical confusion. Actually, there is
>>> no reason at all to discard a resolution shell just because it is not
>>> complete, and what would be a cutoff, if there were one? What
>>> constitutes "too low"?
>>>
>>> The benefit of including also incomplete resolution shells is that
>>> every reflection constitutes a restraint in refinement (and thus
>>> reduces overfitting), and contributes its little bit of detail to the
>>> electron density map. Some people may be mis-lead by a wrong
>>> understanding of the "cats and ducks" examples by Kevin Cowtan:
>>> omitting further data from maps makes Fourier ripples/artifacts worse, not better.
>>>
>>> The unfortunate consequence of the referee's opinion (and its
>>> enforcement and implementation in papers) is that the structures that
>>> result from the enforced re-refinement against truncated data are
>>> _worse_ than the original data that included the "incomplete"
>>> resolution shells.
>>>
>>> So could we as a community please abandon this inappropriate and
>>> un-justified practice - of course after proper discussion here?
>>>
>>> Kay
>>>
>>>
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager