Dear Laurent, On Thu, May 31, 2018 at 02:58:52PM +0200, maveyrau wrote: > we recently collected many datasets on dectris detectors producing > hd5 files. I would like to use some auto processing tools to process > them (xdsapp, xdsme…). As far as I can say, xdsapp or xdsme cannot > process hd5 natively. I tried to convert them to cbf format > (eiger2cbf, hdf2mini-cbf,...), but then it seams that the header of > the caf files are lacking some required informations…
Since you already mention "hdf2mini-cbf" from autoPROC, why not use autoPROC itself for doing the actual processing: process -h5 /where/ever/your_master.h5 ... See also [1] and [2] for more information. > Any idea how to convert hd5 files to complete cdf files? hdf2mini-cbf [3] should create CBF files that are as compatible with original Pilatus mini-CBF files as possible: at least we tried very hard to achieve this in it's original design. If this doesn't work in your particular case we would be very interested to have access to some example files from the beamline(s) you collected on - maybe there are changes in the HDF5 file(s) we aren't aware of (yet). Keeping up with changes to detectors or beamlines is always tricky, unless developers are being made aware of this ;-) Cheers Clemens [1] www.globalphasing.com/autoproc/wiki/index.cgi?DataProcessingHdf5 [2] http://www.globalphasing.com/autoproc/manual/autoproc_reference_card.pdf [3] www.globalphasing.com/autoproc/wiki/index.cgi?DataProcessingHdf5#hdf5converter To unsubscribe from the CCP4BB list, click the following link: https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=CCP4BB&A=1
