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

CCP4BB March 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

I/sigma continued

From:

Phil Evans <[log in to unmask]>

Reply-To:

Phil Evans <[log in to unmask]>

Date:

Mon, 30 Mar 2009 15:26:07 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (81 lines)

“I/sigma” statistics  seem to be contentious & confusing (see recent  
discussions on CCP4BB), particularly in what the various measures  
should be called (and how they should be labelled in a table, where  
there is only room for a very short name). I thought it worth  
commenting on this issue at a little more length.

There are several interacting issues:

1) Statistics can be calculated either for individual observations Ihl  
or for intensities averaged over multiple (symmetry-related or  
replicate) measurements Ih(avg): both are useful, but they need to be  
distinguished

2) The statistic can be (a) the ratio of means <I>/<sigma> or (b) the  
mean of ratios <I/sigma> . These are not the same.

3)The “sigma” used in 2(a) can be either (a) the estimated corrected  
SD or (b) the RMS scatter of observations ie the RMS deviation (which  
is itself generally used to estimate a “correction” to the SD). The  
RMS scatter cannot be used for 2(b) of course, since that needs  
individual sigmas for each reflection.

4) Values will depend on how many outliers have been rejected.

For what it’s worth, Scala outputs two such statistics:-

(i) “I/sigma”: this is calculated for individual observations Ihl and  
is the (mean intensity <Ihl>)/(RMS scatter of Ihl). RMS scatter = RMS  
[Ihl – Ih(avg)]. This is some measure of the average significance of  
individual observations, but does not take into account multiplicity.  
In my new program under development  (a Scala replacement) I have  
relabelled this column “I/RMS” but I don’t really know what best to  
call it. This value is a ratio of means (see 2(a) above).

(ii) “Mn(I/sd)”: this is the mean value of (Ih(avg)/sd(Ih(avg))),  
where Ih(avg) is the (weighted) average over all observations for  
reflection h, and sd(Ih(avg)) is the estimated SD of this average,  
after any “corrections” have been applied. This is, I think, the best  
estimate of “signal-to-noise ratio”, but does depend on realistic  
estimates of sd(Ih(avg)), which is not entirely straightforward (and  
certainly doesn’t allow for systematic errors!). This value is a mean  
of ratios (see 2(b) above).



The “corrected” sd(Ihl) is calculated in Scala for each observation as
		sd(Ihl)corrected =  SdFac * sqrt{sd(I)**2 + SdB*Ihl*LP +  
(SdAdd*Ihl)**2}
with the parameters SdFac, SdB & SdAdd determined by trying to make  
the RMS normalised deviation Delta(hl) = (Ihl - Ih(avg))/ 
sd(Ihl)corrected = 1.0 for all intensity ranges (different parameters  
for each run). If the sd estimates are correct, then the distribution  
of Delta(hl) should have SD = 1.0, and this “correction” tries to  
enforce this.  This is more or less equivalent to making the RMS  
scatter == average SD. However the uncertainties in how best to  
estimate the real error do then influence the reliability of the Mn(I/ 
sd) statistic (see (ii) above)

So what statistics do we want to look at? Probably the main reason for  
looking at signal/noise statistics is to choose a “real resolution”  
cutoff, from some sort of signal/noise ratio. It isn’t clear (to me)  
what is the best way of doing this, and it is particularly difficult  
if the data are significantly anisotropic. The multiplicity needs to  
be taken into account, so the individual “I/sigma” (see (i) above)  
isn’t the best guide. Personally, I generally cut data at around the  
point where Mn(I/sd) =~ 2, but I would cut off at <2 for anisotropic  
data. I also find a useful guide from the correlation coefficient  
between Ih(avg) (Imean) pairs in half-datasets (plotted by Scala): the  
CC should be >0.5 at least, I think.

Note that the overall value of any of these statistics over all  
resolution ranges is not very useful and can be confusing, depending  
on the distribution of intensities, since it mixes up strong low  
resolution data (high signal/noise) with weak high resolution data  
(low signal/noise).

That leaves the question of how to label these statistics in a  
consistent, clear and concise way: suggestions?

Phil Evans

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