I'd like to comment on Kay's statement, "People using a cutoff of 2 (or 3, or 1) for
the mean I/sigI are just using an arbitrary number, as if it were magic."
That may be true for values of 1 or 3, but 45 years ago, I was told by Lyle
Jensen why a 2sigma(I) cutoff was appropriate.
When people
> The ideas was to cut all datasets at say 30% CC1/2 to see how they differ in
> resolution I/sigI etc. for that given CC1/2 …
not sure which insight that would give you. CC1/2 and mean I/sigI of the merged
data are related quantities; that relation is given in (1). The formula given
in "Box 1
The ideas was to cut all datasets at say 30% CC1/2 to see how they differ in
resolution I/sigI etc. for that given CC1/2 …
From: Eleanor Dodson
Date: Friday, 27. October 2017 at 23:12
To: "Schulz, Eike-Christian"
Cc: "CCP4BB@JISCMAIL.AC.UK"
Subject: Re: [ccp4bb] u
Do you mean the CC1/2 for the 15 merged data sets? Doesnt AIMLESS give you
this - treat each one as a seperate run, and you get the stats for each
run, as well as the overall result.
Then you can check where CC1/2 reaches your chosen limit..\
Eleanor
PS - not sure if it is an absolute criteria -
Dear all,
I would like to compare > 15 datasets and would like to use a common CC1/2
value as an objective criterion to determine the resolution cut-off.
All data were integrated in XDS.
Is there a convenient way to apply this in XSCALE or in any of its alternatives?
With best regards,
Eike
