[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: [Imgcif-l] CBF file templates
- To: The Crystallographic Binary File and its imgCIF application to image data <imgcif-l@iucr.org>
- Subject: Re: [Imgcif-l] CBF file templates
- From: Harry Powell <harry@mrc-lmb.cam.ac.uk>
- Date: Tue, 29 Sep 2009 10:51:54 +0100
- In-Reply-To: <4854F2500EA8C4478A508D2D92973E52047BE33A@EXCHANGE25.fed.cclrc.ac.uk>
- References: <4854F2500EA8C4478A508D2D92973E52047BE339@EXCHANGE25.fed.cclrc.ac.uk><F19F5DE9-6164-4A13-9EC6-1D4375803719@mrc-lmb.cam.ac.uk><4854F2500EA8C4478A508D2D92973E52047BE33A@EXCHANGE25.fed.cclrc.ac.uk>
hi > The aim is to define a superset of the format that the ADSC produces, This would be good, and what I've been asking for for several years. Consistency is a wonderful thing. It's not just Mosflm though. > Hi Harry, > > Since we have more ADSC detectors than any other this is something at > the front of my mind! However, something we're looking for is being > able > to put more information in the image header than is currently > contained > therein (= omelette) > so some change may be necessary (= broken eggs) > > The aim is to define a superset of the format that the ADSC produces, > which should mean that Mosflm continues to be happy. > > Cheers, > > Graeme > > -----Original Message----- > From: imgcif-l-bounces@iucr.org [mailto:imgcif-l-bounces@iucr.org] On > Behalf Of Harry Powell > Sent: 29 September 2009 10:32 > To: The Crystallographic Binary File and its imgCIF application to > image > data > Subject: Re: [Imgcif-l] CBF file templates > > Hi > > Use something that doesn't break the CBFs that the ADSC detectors > write. > They are, without a doubt, the best model to use, mainly because they > have been writing CBFs for more years than I care to remember and > Chris > has been more responsive than anyone else in making them useful. > > On 29 Sep 2009, at 09:58, Winter, Graeme (DLSLtd,RAL,DIA) wrote: > >> Dear CBF'ers, >> >> I'm working on trying to establish a "Diamond standard" template for >> our CBF files across a number of detectors, and I was wondering how >> this is best specified. What would be ideal would be to set up a >> template which contains those things that the beamline "knows" but >> the > >> detector does not, then have the detector software populate the other >> fields (e.g. >> exposure time, integration time, maximum trusted pixel, oscillation >> start / end) to give a full description. >> >> Now, has anyone done something like this? If so, how do you specify >> the fields which are to be replaced? If not, does anyone have an >> opinion on how this should be done? >> >> Thanks, >> >> Graeme >> >> Graeme Winter >> Software and MX Support Scientist >> Diamond Light Source >> >> +44 1235 778091 (work) >> +44 7786 662784 (work mobile) >> >> >> >> This e-mail and any attachments may contain confidential, copyright >> and or privileged material, and are for the use of the intended >> addressee only. If you are not the intended addressee or an >> authorised > >> recipient of the addressee please notify us of receipt by returning >> the e-mail and do not use, copy, retain, distribute or disclose the >> information in or attached to the e-mail. >> >> Any opinions expressed within this e-mail are those of the individual >> and not necessarily of Diamond Light Source Ltd. >> >> Diamond Light Source Ltd. cannot guarantee that this e-mail or any >> attachments are free from viruses and we cannot accept liability for >> any damage which you may sustain as a result of software viruses >> which > >> may be transmitted in or with the message. >> >> Diamond Light Source Limited (company no. 4375679). Registered in >> England and Wales with its registered office at Diamond House, >> Harwell > >> Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United >> Kingdom >> >> >> >> _______________________________________________ >> imgcif-l mailing list >> imgcif-l@iucr.org >> http://scripts.iucr.org/mailman/listinfo/imgcif-l > > Harry > -- > Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, > Hills > Road, Cambridge, CB2 0QH > > > > _______________________________________________ > imgcif-l mailing list > imgcif-l@iucr.org > http://scripts.iucr.org/mailman/listinfo/imgcif-l > This e-mail and any attachments may contain confidential, copyright > and or privileged material, and are for the use of the intended > addressee only. If you are not the intended addressee or an > authorised recipient of the addressee please notify us of receipt by > returning the e-mail and do not use, copy, retain, distribute or > disclose the information in or attached to the e-mail. > Any opinions expressed within this e-mail are those of the > individual and not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any > attachments are free from viruses and we cannot accept liability for > any damage which you may sustain as a result of software viruses > which may be transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in > England and Wales with its registered office at Diamond House, > Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 > 0DE, United Kingdom > > _______________________________________________ > imgcif-l mailing list > imgcif-l@iucr.org > http://scripts.iucr.org/mailman/listinfo/imgcif-l Harry -- Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills Road, Cambridge, CB2 0QH _______________________________________________ imgcif-l mailing list imgcif-l@iucr.org http://scripts.iucr.org/mailman/listinfo/imgcif-l
Reply to: [list | sender only]
- References:
- [Imgcif-l] CBF file templates (Winter, Graeme (DLSLtd,RAL,DIA))
- Re: [Imgcif-l] CBF file templates (Harry Powell)
- Re: [Imgcif-l] CBF file templates (Winter, Graeme (DLSLtd,RAL,DIA))
- Prev by Date: Re: [Imgcif-l] CBF file templates
- Next by Date: Re: [Imgcif-l] CBF file templates
- Prev by thread: Re: [Imgcif-l] CBF file templates
- Next by thread: Re: [Imgcif-l] CBF file templates
- Index(es):