[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW
- To: <imgcif-l@iucr.org>
- Subject: Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW
- From: <Graeme.Winter@Diamond.ac.uk>
- Date: Wed, 14 Jul 2010 15:08:58 +0100
- In-Reply-To: <AANLkTimhafA9Q7NYaBOSzkrpKHang_WjmHw-OyuWWvgm@mail.gmail.com>
- References: <4854F2500EA8C4478A508D2D92973E5206D6B69C@EXCHANGE25.fed.cclrc.ac.uk><AANLkTimhafA9Q7NYaBOSzkrpKHang_WjmHw-OyuWWvgm@mail.gmail.com>
Hi James, I would think graefully ignoring all non-cif file contents would work wonderfully... I look forward to a fix! Best wishes, Graeme -----Original Message----- From: imgcif-l-bounces@iucr.org [mailto:imgcif-l-bounces@iucr.org] On Behalf Of James Hester Sent: 14 July 2010 14:10 To: The Crystallographic Binary File and its imgCIF application to image data Subject: Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW I'm glad you like PyCifRW...but at the moment it won't play well with cbf, as it is expecting pure ASCII for all tokens. I'll look into graceful handling of syntax errors, so you at least get back anything that has been successfully parsed. I once thought it might be nice if PyCIFRW could deal with imgCIF and CBF files, but quickly realised that I would need to be using a C library for speed and would thus have issues distributing it in a uniform cross-platform manner. On Wed, Jul 14, 2010 at 5:49 PM, <Graeme.Winter@diamond.ac.uk> wrote: > Hi Folks, > > Has anyone tried reading cbf files with PyCifRW? It appears to cope > fine with the "real" cif at the top but then chokes when it hits the > binary data. I'd like to be able to just read the cif describing the > experiment, so in theory there should be a way to do this. If I copy > out just the cif into another file it works fine. > > Thing is, I don't want to copy the cif out to read it when I want to > parse every header in a data set :o) - has anyone a workaround for this? > > > I like PyCifRW as it's included in cctbx and works just fine. The > pycbf isn't built by default :o( > > Thanks, > > Graeme > > > > Dr. 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 > -- T +61 (02) 9717 9907 F +61 (02) 9717 3145 M +61 (04) 0249 4148 _______________________________________________ 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
Reply to: [list | sender only]
- Follow-Ups:
- References:
- [Imgcif-l] Reading CBF file headers from Python with PyCifRW (Graeme.Winter)
- Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW (James Hester)
- Prev by Date: Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW
- Next by Date: Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW
- Prev by thread: Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW
- Next by thread: Re: [Imgcif-l] Reading CBF file headers from Python with PyCifRW
- Index(es):