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  February 2009

CCP4BB February 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: unstable refinement

From:

"George M. Sheldrick" <[log in to unmask]>

Reply-To:

George M. Sheldrick

Date:

Mon, 16 Feb 2009 12:23:37 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (80 lines)

Dear Ian,

That was in fact one of my reasons for only calculating the free R
at the end of a SHELXL refinement run (the other reason, now less 
important, was to save some CPU time). I have to add that I am no
longer completely convinced that I made the right decision all 
those years ago. A stable refinement in which R decreases but 
Rfree goes through a minimum and then starts to rise might be a 
useful indication of overfitting?!

Best wishes, George 

Prof. George M. Sheldrick FRS
Dept. Structural Chemistry,
University of Goettingen,
Tammannstr. 4,
D37077 Goettingen, Germany
Tel. +49-551-39-3021 or -3068
Fax. +49-551-39-22582


On Mon, 16 Feb 2009, Ian Tickle wrote:

> Clemens, I know we've had this discussion several times before, but I'd
> like to take you up on the point you made that reducing Rfree-R is
> necessarily always a 'good thing'.  Suppose the refinement had started
> from a point where Rfree was biased, e.g. the test set in use had
> previously been part of the working set, so that Rfree-R was too small.
> In that case one would hope and indeed expect that Rfree-R would
> increase on further refinement now excluding the test set.  Shouldn't
> the criterion be that Rfree-R should attain its expected value
> (dependent of course on the observation/parameter ratio and the
> weighting parameters), so a high value of |(Rfree-R) - <Rfree-R>| is
> bad, i.e. any significant deviations of (Rfree-R) from its expectation
> are bad?
> 
> I would go further than that and say that anyway Rfree is meaningless
> unless the refinement has converged, i.e. reached its maximum (local or
> global) total likelihood (i.e. data+restraints).  So one simply cannot
> compare the Rfree (or Rfree-R) values at the beginning and end of a run.
> The purpose of Rfree (or better free likelihood) is surely to compare
> the *results* of *different* runs where convergence has been attained
> and where the *refinement protocol* (i.e. selection of parameters to
> vary and weighting parameters) has been varied, and then to choose as
> the optimal protocol (and therefore optimal result) the one that gave
> the lowest Rfree (or highest free likelihood).
> 
> Rfree-R is then used as a subsidiary test to verify that it has attained
> its expected value, if not then something is wrong, i.e. either the
> refinement didn't converge (Rfree-R lower than <Rfree-R>) or there are
> non-random errors (Rfree-R higher than <Rfree-R>), or a combination of
> factors.
> 
> Cheers
> 
> -- Ian
> 
> > -----Original Message-----
> > From: [log in to unmask] [mailto:[log in to unmask]]
> On
> > Behalf Of Clemens Vonrhein
> > Sent: 13 February 2009 17:15
> > To: [log in to unmask]
> > Subject: Re: [ccp4bb] unstable refinement
> > 
> > * you don't mention if the R and Rfree move up identically - or if you
> >   have a faster increase in R than in Rfree, which would mean that
> >   your R-factors are increasing (bad I guess) but your Rfree-R gap is
> >   closing down (good).
> > 
> >   So moving from R/Rfree=0.20/0.35 to R/Rfree=0.32/37 is different
> >   than moving from R/Rfree=0.20/0.25 to R/Rfree=0.23/0.28.
> 
> 
> Disclaimer
> This communication is confidential and may contain privileged information intended solely for the named addressee(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient you must not review, use, disclose, copy, distribute or take any action in reliance upon it. If you have received this communication in error, please notify Astex Therapeutics Ltd by emailing [log in to unmask] and destroy all copies of the message and any attached documents. 
> Astex Therapeutics Ltd monitors, controls and protects all its messaging traffic in compliance with its corporate email policy. The Company accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the Astex Therapeutics domain.  Unless expressly stated, opinions in this message are those of the individual sender and not of Astex Therapeutics Ltd. The recipient should check this email and any attachments for the presence of computer viruses. Astex Therapeutics Ltd accepts no liability for damage caused by any virus transmitted by this email. E-mail is susceptible to data corruption, interception, unauthorized amendment, and tampering, Astex Therapeutics Ltd only send and receive e-mails on the basis that the Company is not liable for any such alteration or any consequences thereof.
> Astex Therapeutics Ltd., Registered in England at 436 Cambridge Science Park, Cambridge CB4 0QA under number 3751674
> 

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