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

CCP4BB June 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: ctruncate bug?

From:

Andrew Leslie <[log in to unmask]>

Reply-To:

Andrew Leslie <[log in to unmask]>

Date:

Thu, 20 Jun 2013 12:08:33 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (87 lines)

The integration programs report a negative intensity simply because that is the observation. 

Because of noise in the Xray background, in a large sample of intensity estimates for reflections whose true intensity is very very small one will inevitably get some measurements that are negative. These must not be rejected because this will lead to bias (because some of these intensities for symmetry mates will be estimated too large rather than too small). It is not unusual for the intensity to remain negative even after averaging symmetry mates.

Andrew


On 20 Jun 2013, at 11:49, Douglas Theobald <[log in to unmask]> wrote:

> Seems to me that the negative Is should be dealt with early on, in the integration step.  Why exactly do integration programs report negative Is to begin with?
> 
> 
> On Jun 20, 2013, at 12:45 PM, Dom Bellini <[log in to unmask]> wrote:
> 
>> Wouldnt be possible to take advantage of negative Is to extrapolate/estimate the decay of scattering background (kind of Wilson plot of background scattering) to flat out the background and push all the Is to positive values?
>> 
>> More of a question rather than a suggestion ...
>> 
>> D
>> 
>> 
>> 
>> From: CCP4 bulletin board [mailto:[log in to unmask]] On Behalf Of Ian Tickle
>> Sent: 20 June 2013 17:34
>> To: ccp4bb
>> Subject: Re: [ccp4bb] ctruncate bug?
>> 
>> Yes higher R factors is the usual reason people don't like I-based refinement!
>> 
>> Anyway, refining against Is doesn't solve the problem, it only postpones it: you still need the Fs for maps! (though errors in Fs may be less critical then).
>> -- Ian
>> 
>> On 20 June 2013 17:20, Dale Tronrud <[log in to unmask]<mailto:[log in to unmask]>> wrote:
>>  If you are refining against F's you have to find some way to avoid
>> calculating the square root of a negative number.  That is why people
>> have historically rejected negative I's and why Truncate and cTruncate
>> were invented.
>> 
>>  When refining against I, the calculation of (Iobs - Icalc)^2 couldn't
>> care less if Iobs happens to be negative.
>> 
>>  As for why people still refine against F...  When I was distributing
>> a refinement package it could refine against I but no one wanted to do
>> that.  The "R values" ended up higher, but they were looking at R
>> values calculated from F's.  Of course the F based R values are lower
>> when you refine against F's, that means nothing.
>> 
>>  If we could get the PDB to report both the F and I based R values
>> for all models maybe we could get a start toward moving to intensity
>> refinement.
>> 
>> Dale Tronrud
>> 
>> 
>> On 06/20/2013 09:06 AM, Douglas Theobald wrote:
>> Just trying to understand the basic issues here.  How could refining directly against intensities solve the fundamental problem of negative intensity values?
>> 
>> 
>> On Jun 20, 2013, at 11:34 AM, Bernhard Rupp <[log in to unmask]<mailto:[log in to unmask]>> wrote:
>> As a maybe better alternative, we should (once again) consider to refine against intensities (and I guess George Sheldrick would agree here).
>> 
>> I have a simple question - what exactly, short of some sort of historic inertia (or memory lapse), is the reason NOT to refine against intensities?
>> 
>> Best, BR
>> 
>> 
>> 
>> 
>> -- 
>> 
>> This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
>> 
>> Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
>> 
>> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
>> 
>> Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 

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