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  September 2013

CCP4BB September 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Resolution, R factors and data quality

From:

Robbie Joosten <[log in to unmask]>

Reply-To:

Robbie Joosten <[log in to unmask]>

Date:

Mon, 2 Sep 2013 13:17:30 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (127 lines)

Hi Frank and Ian,

We struggled with the small changes in free R-factors when we implementing
the paired refinement for resolution cut-offs in PDB_REDO. It's not just the
lack of a proper test of significance for (weighted) R-factor changes, it's
also a more philosophical problem. When should you reject a higher
resolution cut-off? 
a) When it gives significantly higher R-factors (lenient)
b) When it gives numerically higher R-factors (less lenient, but takes away
the need for a significance test)
c) When it does not give significantly lower R-factors (very strict; if I
take X*sigma(R-free) as a cut-off, with X > 1.0, in most cases I should
reject the higher cut-off).

PDB_REDO uses b), similar to Karplus and Diederichs in their Science paper.

Then the next question is which metric are you going to use? R-free,
weighted R-free, free log likelihood and CCfree are all written out by
Refmac. At least the latter two have proper significance tests (likelihood
ratios and transformation Z-scores respectively). Note that we use different
models, constructed with different (but very much overlapping) data, but the
metrics are calculated with the same data. The different metrics do not
necessarily move in the same direction when moving to a higher resolution.

We ended up using all 4 in PDB_REDO. By default a higher resolution cut-off
is rejected if more than 1 metric gets (numerically) worse, but this can be
changed by the user.

Next question is the size of the resolution steps. How big should those be
and how should they be set up? Karplus and Diederichs used equal steps in
Angstrom, PDB_REDO uses equal steps in number of reflections. That way you
add the same amount of data (but not usable information) with each step.
Anyway, a different choice of steps will give a different final resolution
cut-off. And the exact cut-off doesn't matter that much (see Evans and
Murshudov). Different (versions of) refinement programs will probably also
give somewhat different results. 

We tested our implementation on a number of structures in the PDB with data
extending to higher resolution than marked in the PDB file and we observed
that quite a lot had very conservative resolution cut-offs. In some cases we
could use so much extra data that we could move to a more complex B-factor
model and seriously improve R-factors.

The best resolution cut-off is unclear and may change over time with
improving methods. So whatever you choose, please deposit all the data that
you can get even if you don't use it yourself. I think that the Karplus and
Diederichs papers show us that you should at least realize that your
resolution cut-off is a methodological choice that you should describe and
should be able to defend if somebody asks you why you made that particular
choice.

Cheers,
Robbie


> On 1 September 2013 11:31, Frank von Delft <[log in to unmask]>
> wrote:
> 
> 
> 
> 	2.
> 	I'm struck by how small the improvements in R/Rfree are in
> Diederichs & Karplus (ActaD 2013,
> http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3689524/
> <http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3689524/> );  the authors
> don't discuss it, but what's current thinking on how to estimate the
expected
> variation in R/Rfree - does the Tickle formalism (1998) still apply for ML
with
> very weak data?
> 
> 
> 
> Frank, our paper is still relevant, unfortunately just not to the question
> you're trying to answer!  We were trying to answer 2 questions: 1) what
> value of Rfree would you expect to get if the structure were free of
> systematic error and only random errors were present, so that could be
used
> as a baseline (assuming a fixed cross-validation test set) to identify
models
> with gross (e.g. chain-tracing) errors; and 2) how much would you expect
> Rfree to vary assuming a fixed starting model but with a different random
> sampling of the test set (i.e. the "sampling standard deviation").  The
latter is
> relevant if say you want to compare the same structure (at the same
> resolution obviously) done independently in 2 labs, since it tells you how
big
> the difference in Rfree for an arbitrary choice of test set needs to be
before
> you can claim that it's statistically significant.
> 
> 
> In this case the questions are different because you're certainly not
> comparing different models using the same test set, neither I suspect are
> you comparing the same model with different randomly selected test sets.
I
> assume in this case that the test sets for different resolution cut-offs
are
> highly correlated, which I suspect makes it quite difficult to say what is
a
> significant difference in Rfree (I have not attempted to do the algebra!).
> 
> 
> Rfree is one of a number of "model selection criteria" (see
> http://en.wikipedia.org/wiki/Model_selection#Criteria_for_model_selectio
> n) whose purpose is to provide a metric for comparison of different models
> given specific data, i.e. as for the likelihood function they all take the
form
> f(model | data), so in all cases you're varying the model with fixed data.
It's
> use in the form f(data | model), i.e. where you're varying the data with a
> fixed model I would say is somewhat questionable and certainly requires
> careful analysis to determine whether the results are statistically
significant.
> Even assuming we can argue our way around the inappropriate application of
> model selection methodology to a different problem, unfortunately Rfree is
> far from an ideal criterion in this respect; a better one would surely be
the
> free log-likelihood as originally proposed by Gerard Bricogne.
> 
> 
> Cheers
> 
> 
> -- Ian
> 

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