I agree absolutely with James - be as succinct as you like in a table
but include the verbose definition for each entry in the log file - or
at the very least in the manual. It should be easy to search for with
the table tag.
People will not go and read a reference..
Eleanor
James Holton wrot
James Holton schrieb:
Frank von Delft wrote:
So, what statistic do we want to look at? That depends on what you
are trying to do with the data. There is no way for Phil to know
this, so it is good that he prints out lots of different
statistics. That said, when talking about the data quali
ion between PDB and
mmCIF formats but that is for another day...)
-Original Message-
From: CCP4 bulletin board [mailto:ccp...@jiscmail.ac.uk] On Behalf Of
Anastassis Perrakis
Sent: Monday, March 30, 2009 11:40 AM
To: CCP4BB@JISCMAIL.AC.UK
Subject: Re: [ccp4bb] I/sigma continued
On 30 Mar
On 30 Mar 2009, at 20:30, James Holton wrote:
Frank von Delft wrote:
So, what statistic do we want to look at? That depends on what you
are trying to do with the data. There is no way for Phil to know
this, so it is good that he prints out lots of different
statistics. That said, when talki
Frank von Delft wrote:
So, what statistic do we want to look at? That depends on what you
are trying to do with the data. There is no way for Phil to know
this, so it is good that he prints out lots of different
statistics. That said, when talking about the data quality
requirements for st
So, what statistic do we want to look at? That depends on what you
are trying to do with the data. There is no way for Phil to know
this, so it is good that he prints out lots of different statistics.
That said, when talking about the data quality requirements for
structure solution by MAD/
I think the best way to deal with issues like this can be found in
Strunk & White "The Elements of Style" (1918). Among other things,
these authors put forward a rather simple yet often overlooked rule to
writing in general, which I think applies equally well to computer programs:
"Be clear."
That leaves the question of how to label these statistics in a consistent,
clear and concise way: suggestions?
Phil Evans
Here is a suggestion. :)
FWIW, dtscaleaverage labels the mean I/sigmaI of the individual input
reflections as "I/sig unavg". That is, before any averaging is
performed
“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 a
