Jim, thanks for the info. At present we use d*TREK mostly only for in-house data (Saturn, Jupiter & R-axis) so the data collection rate is much lower and in any case we would gain nothing by compressing them since the I/O is the same whether it's gzip reading in the images or d*TREK. Our problem is that our people bring back a large no of datasets (> 150) from each synchrotron trip, dump them all on the file server and then try to process them all at the same time!
Cheers -- Ian On Thu, May 6, 2010 at 12:38 PM, Jim Pflugrath <jim.pflugr...@rigaku.com> wrote: > d*TREK will process compressed images with the following extensions: .gz > .bz2 .Z .pck and .cbf > > > -----Original Message----- > From: CCP4 bulletin board [mailto:ccp...@jiscmail.ac.uk] On Behalf Of Ian > Tickle > Sent: Thursday, May 06, 2010 6:25 AM > To: CCP4BB@JISCMAIL.AC.UK > Subject: [ccp4bb] Processing compressed diffraction images? > > All - > > No doubt this topic has come up before on the BB: I'd like to ask about the > current capabilities of the various integration programs (in practice we use > only MOSFLM & XDS) for reading compressed diffraction images from > synchrotrons. A... > > cluster: the disk I/O is the bottleneck. Now you could argue that we should > spread the load over more disks or maybe spend more on faster disk > controllers, but the whole point about disks is they're cheap, we don't need > the extra I/O bandwidth for anything else, and you shouldn't need to spend a > fortune, particularly if there are ways of making the software more > efficient, which after all will benefit everyone. > > Cheers > > -- Ian > >
