Hi
I'd guess from the input file that the beam centre may be defined in a
different reference frame to that which Mosflm expects in the image
header; other possibilities are that the distance, wavelength, or
something else (!) is wrong. Indexing is critically dependent on having
the beam centre, distance and wavelength all being pretty close to the
true values, though some indexing routines allow more latitude than
others.
My understanding (IMWBW) is that other programs (such as XDS or HKL2000)
don't use the information in the image headers, and expect the parameters
to be supplied by the user. With Mosflm, we try to make the user's life
easier by trusting this information, especially from images collected at
synchrotron beamlines; sometimes this trust is not warranted, and the user
has to intervene!
processing data collected on APS beamline BM17 on a MAR165 detector
causes unexpected troubles. Even though the crystals are
well-diffracting and the spots are sharp and well-resolved, indexing
only works with a certain selection of frames, the refinement the goes
totally hairwire. Probalby just a parameter or so set wrong. My input
file in the attachment. The last three lines do not make much of a
difference. Any ideas?
Thanks!
Cheers
Jan
************************
mosflm.in:
detector marccd
directory ../Images
template Image_0###.img
image 001
nullpix 1
separation 0.95 0.95 close
!LIMITS XMIN 0 XMAX 165 YMIN 0 YMAX 165 xscan 2048 yscan 2048
!SIZE 2048 2048
!PIXEL 0.07934
************************
Harry
--
Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills
Road, Cambridge, CB2 2QH
