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  December 2008

CCP4BB December 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Transferring a Free R set.

From:

Ian Tickle <[log in to unmask]>

Reply-To:

Ian Tickle <[log in to unmask]>

Date:

Fri, 19 Dec 2008 12:07:12 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (202 lines)

Alun,

There's only any point doing it if they're truly isomorphous (e.g. by
the Crick-Magdoff test), otherwise pairs of reflections with equal
indices won't sample the same points in the transforms, so you could
still end up with contamination.

Slow cooling or pseudo-MD such as randomly shifting co-ordinates
actually moves you away from convergence, and as I said convergence is
where you need to be for Rfree to be meaningful and to completely erase
'memories' in the structure.  Also it's a progressive thing, the closer
you get to convergence, the more meaningful Rfree becomes and the more
the memories are erased.  Of course convergence is very elusive, just
because the parameter shifts appear to be getting smaller doesn't
guarantee convergence (e.g. the series 1+1/2+1/3+1/4+1/5+... diverges to
infinity!), so by all means try slow-cooling, just be prepared to
carefully evaluate the results.

Cheers

-- Ian

> -----Original Message-----
> From: [log in to unmask] 
> [mailto:[log in to unmask]] On Behalf Of Alun R. Coker
> Sent: 19 December 2008 10:37
> To: [log in to unmask]
> Cc: CCP4 bulletin board
> Subject: Re: [ccp4bb] Transferring a Free R set.
> 
> Hi Ian, Gerard,
> 
> Thanks for your replies.
> 
> Perhaps my hypothetical example wasn't a good one and may 
> have clouded 
> the issue.  Could I just confirm whether or not you think its 
> necessary 
> to transfer initial free R assignment to any new data sets or to 
> isomorphous data sets such as substrate complexes. 
> 
> Thanks,
> 
> Alun.
> 
> Ian Tickle wrote:
> > Hi Alun
> >
> > I've never seen a soaked ligand-bound structure that's 
> truly isomorphous
> > with the native - simply soaking & freezing the crystal is virtually
> > guaranteed to introduce very serious non-isomorphism, e.g. up to 5%
> > change in one or more cell parameters.  At least, we always 
> have a MR
> > step to solve the structure, as rigid-body refinement alone 
> often fails
> > to pull it in, so the R-factors always start high (> 0.4) 
> anyway.  This
> > renders the concept of a common test set totally 
> meaningless, since the
> > native & ligand-bound reflections with the same indices 
> (except maybe
> > the low res ones) will not be in equivalent positions in reciprocal
> > space, and in any case once it has been refined down & been 
> through a
> > few rounds of rebuilding any bias will very quickly disappear.
> >
> > Note that Rfree is a meaningful statistic only at convergence at the
> > likelihood maximum, and at convergence all previous 
> 'memories' of the
> > structure are erased: bias due to 'contamination' of the 
> test set only
> > occurs as a result of failure to ensure convergence.  Also I don't
> > believe that any of the cases of deposited ligand structures where
> > either there is clearly no density for the ligand, or the 
> ligand is in
> > the wrong place, or even the wrong ligand has been built, 
> can be laid at
> > the door of the test set that was used.  Plain incompetence and/or
> > wishful thinking is a much more likely explanation.  So personally I
> > think you're worrying over nothing.
> >
> > Just my 2p's worth.
> >
> > Cheers & Seasons greetings to Steve & Jon!
> >
> > -- Ian
> >
> >   
> >> -----Original Message-----
> >> From: [log in to unmask] 
> >> [mailto:[log in to unmask]] On Behalf Of Alun R. Coker
> >> Sent: 18 December 2008 22:45
> >> To: CCP4 bulletin board
> >> Subject: Re: [ccp4bb] Transferring a Free R set.
> >>
> >> Hi All,
> >>
> >> I suspect using a new free assignment for each data set is a 
> >> fairly wide 
> >> spread mistake, which would be hard to pick up by a reviewer. 
> >>  It would 
> >> be interesting to survey the pdb for ligand bound structures 
> >> which have 
> >> a different free R set from their parent (isomorphous) native 
> >> structures.  I have heard from a colleague involved in testing 
> >> refinement programs that there is a surprising number of deposited 
> >> ligand structures where re-refinement shows that the 
> ligand is built 
> >> into noise.
> >>
> >> Would it be fair to say that in the case of a ligand structure, 
> >> isomorphous with the native structure but where different 
> R-free sets 
> >> have been used, we cannot use the R-free to validate 
> >> refinement of the 
> >> ligand?  My understanding is that it would be contaminated by 
> >> the phases 
> >> brought over with the model from the native data set, and is 
> >> no longer 
> >> independent, so any ligand density could just arise from over 
> >> fitting.  
> >> How could we test/retrieve such a situation?  Will omit maps 
> >> made after 
> >> a round of REFMAC refinement  without the ligand still have a 
> >> memory of 
> >> our over fitted model which would persist through to new 
> maps? If so, 
> >> would this be the case after a slow cool in CNS? 
> >>
> >> Does the community still think it is valid to use a slow cool 
> >> to "reset" 
> >> the free R?
> >>
> >> Alun.
> >>
> >> -- 
> >> Alun R. Coker
> >> University College London
> >> Division of Medicine, Royal Free Campus
> >> Centre for Amyloidosis and Acute Phase Proteins
> >> Rowland Hill Street
> >> London
> >> NW32PF
> >>
> >> Tel: +44(0)20 7433 2764
> >> Fax: +44(0)20 7433 2776
> >>
> >>
> >>     
> >
> >
> > 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
> >   
> 
> -- 
> Alun R. Coker
> University College London
> Division of Medicine, Royal Free Campus
> Centre for Amyloidosis and Acute Phase Proteins
> Rowland Hill Street
> London
> NW32PF
> 
> Tel: +44(0)20 7433 2764
> Fax: +44(0)20 7433 2776
> 
> 


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

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