From: Yuri Pompeu
Date: 11 April 2012 16:08
Hello everyone,
I am trying to process ###.cbf raw images (BNL X25) using the iMOSFLM utility and I get the following error message:
"Distance has refined to an unreasonable value"
This causes the program to freeze and not open the rest of the frames.
Also it is not picking up the X and Y beam positions.
It looks to me like its just simply not reading the image file HEADER properly.
Anyone has encountered this before and has any ideas on how to get around/fix this?
Thanks a lot!
Yuri
----------
From: Harry
Hi Yuri
If you can put some of the images on our ftp site (instructions sent separately) we'll have a look. There was a problem a while ago when some Pilatus detectors changed from writing the distance in metres to writing it in millimetres, but no-one told us until iMosflm started having problems. Harry
--
Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills Road, Cambridge, CB2 0QH
----------
From: Harry Powell
----------
From: Kip Guja
Thank you Harry for letting us know about this!
Could you please send an update to the list when the new
version is out? (I would also like to process images from
BNL x25 (Pilatus 6M), and I'm sure there are others in the
same boat).
Best wishes,
Kip
Date: 11 April 2012 16:08
Hello everyone,
I am trying to process ###.cbf raw images (BNL X25) using the iMOSFLM utility and I get the following error message:
"Distance has refined to an unreasonable value"
This causes the program to freeze and not open the rest of the frames.
Also it is not picking up the X and Y beam positions.
It looks to me like its just simply not reading the image file HEADER properly.
Anyone has encountered this before and has any ideas on how to get around/fix this?
Thanks a lot!
Yuri
----------
From: Harry
Hi Yuri
If you can put some of the images on our ftp site (instructions sent separately) we'll have a look. There was a problem a while ago when some Pilatus detectors changed from writing the distance in metres to writing it in millimetres, but no-one told us until iMosflm started having problems.
--
Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills Road, Cambridge, CB2 0QH
----------
From: Harry Powell
Dear all
The problem was indeed the distance being written in mm rather than m, so some of our internal maths gave surprising results. This will be fixed in the next versions of iMosflm and Mosflm - barring finding any killer bugs I hope this will be released next week.
----------
From: Kip Guja
Thank you Harry for letting us know about this!
Could you please send an update to the list when the new
version is out? (I would also like to process images from
BNL x25 (Pilatus 6M), and I'm sure there are others in the
same boat).
Best wishes,
Kip
hey
ReplyDelete