Hi folks
With respect to George, I don't think this is the easiest way. If learning to use a different program was the easiest way forward for any task, people would have dropped MS-Windows like a hot potato after the release of Vista and started using some other operating system that was "better". I'm sure that many people here will have their own examples of other instances where they would prefer to carry on using a program they know well rather than learn something new, even if the new program offers advantages.
I'd have to say, in general the easiest thing to do when confronted with Mosflm issues is to get in touch with the authors and ask them. We are all very friendly, approachable people who will do our best to help!
On 9 Nov 2010, at 08:42, George M. Sheldrick wrote:
> By far the easiest way would be to use the programs (SAINT and SADABS)
> provided by Bruker. We get excellent data, e.g. for in-house S-SAD
> phasing, using these programs (either offline or as part of the Bruker
> GUI) for data collected on our SMART6000. For a detailed S-SAD example
> see Berhard's book page 424. Unlike MOSFLM, SAINT can integrate
> non-merohedral twins handling the reflection overlap properly and can
> process phi scans for which the oscillation axis is not perpendicular
> to the incident beam.
>
> George
>
> Prof. George M. Sheldrick FRS
> Dept. Structural Chemistry,
> University of Goettingen,
> Tammannstr. 4,
> D37077 Goettingen, Germany
> Tel. +49-551-39-3021 or -3068
> Fax. +49-551-39-22582
>
>
> On Mon, 8 Nov 2010, Ed Pozharski wrote:
>
>> I am trying to read Bruker's Smart 6000 images with mosflm and it fails.
>> Based on some limited googlearch I feel that "NPIXELB:1" is a relevant
>> information and when these files were processed in HKL (not by me), the
>> relevant detector line says "format ccd bruker smart6000 binned". I see
>> from mosflm website that I might be in trouble here although it says
>> that in recent version handling of bruker smart has been improved. In
>> the mosflm crash file I get this
>>
>> From information in the image file, the detector has been
>> recognized as: Bruker SMART
>> If this is incorrect you must supply a DETECTOR keyword
>>
>> So my question is how do I figure out if this particular format is
>> supported or not?
>>
>> Cheers,
>>
>> Ed.
>>
>> --
>> "I'd jump in myself, if I weren't so good at whistling."
>> Julian, King of Lemurs
>>
>>
Harry
--
Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills Road, Cambridge, CB2 0QH
|