Re: [ccp4bb] mosflm and APS BM17

2007-08-22 Thread Harry Powell
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

Re: [ccp4bb] mosflm and APS BM17

2007-08-22 Thread Jan Abendroth
Hi all, thanks a lot for all the responses! As anticipated, the solution is rather simple - the origin of the beam: denzo refines to: x=82.6 y=80.3 mosflm reads from header: x=80.0 y=84.0 - bad indexing etc mosflm works with: x=82.6 y=80.3 No swapping of x and y between denzo and mosflm in this

Re: [ccp4bb] mosflm and APS BM17

2007-08-21 Thread Roger Rowlett
Is it possible that your crystal is not really a single crystal, or has multiple domains? I had a similar problem with an otherwise beautifully diffracting crystal (beyond 2.0 A) whose integration rapidly broke down after a few frames. On close inspection, it was possible to visualize multiple