On Mar 19, 2009, at 3:26 AM, Andrew Purkiss-Trew wrote:
On Wed, 2009-03-18 at 18:19 +0000, Frank von Delft wrote:
Maybe, but images without experimental context (sequence? ligands?
purification? crystallization format? -- PURPOSE OF EXPERIMENT!?!!
relationship to the other 15 similar datasets) are as good as no
images. And as far as I know, there's no good discussion on the
table
for that. At least, no-one on the thread mentioned it, so they're
probably not thinking about it either.
I suppose efforts like PIMS or are a start, and maybe they can even
have
enough information (my feeling is they currently don't). But that's
where the discussion should start: how to index (in sense of
annotate)
the datasets. The technicalities are just that: technicalities.
Or even closer to home: does ANY detector/beamline write even
timestamps
into the image header...? Never mind ring current, intensity of the
beam, size of beam, size of crystal, length of direct beam path, etc
etc...
As far as I know, most detectors write the current time into the image
header. Certainly our in house MAR image plate systems do, as do the
detectors at Diamond and ESRF (for those that I've looked at this
morning).
FYI at my beamline (ALS 12.3.1), in addition to the usual useful
metadata, we also put in the beamline ID and the serial number of the
detector. In theory anything can be added if you take the time to
customize the detector code.
HEADER_BYTES= 512;
DIM=2;
BYTE_ORDER=little_endian;
TYPE=unsigned_short;
SIZE1=3072;
SIZE2=3072;
PIXEL_SIZE=0.102592;
BIN=2x2;
BIN_TYPE=HW;
ADC=fast;
CREV=1;
BEAMLINE=ALS1231;
DETECTOR_SN=907;
DATE=Tue Feb 3 11:07:38 2009;
TIME=10.000000;
ACC_TIME=11516;
DISTANCE=649.80;
TWOTHETA=0.00;
PHI=191.310;
OSC_START=191.310;
OSC_RANGE=1.000;
WAVELENGTH=1.033184;
BEAM_CENTER_X=155.70;
BEAM_CENTER_Y=157.40;
DENZO_X_BEAM=157.76;
DENZO_Y_BEAM=155.70;
Scott
