ADPilaus + NDFileHDF5

[John Dobbins via Tech-talk <tech-talk at aps.anl.gov>]

All,

I am trying the Pilatus with the NDFileHDF5 plug-in.  From an acquisition I end up with both TIFF (x NumImages) files and one hdf5 file and am wondering about the proper way to end up with just the hdf5.

I see in the documentation for the NDPluginFile

-----------------------------------------------------------

The base class will delete the “original” file that the driver created for that array if the following are all true:

The DeleteDriverFile record is “Yes”.

The file plugin has successfully written a new file.

The array contains an attribute called “DriverFileName” that contains the full file name of the original file. The driver attributes XML file should contain a line like the following:

<Attribute name="DriverFileName" type="PARAM" source="FULL_FILE_NAME" datatype="STRING" description="Driver file name"/>

-------------------------------------------------------------

In the NDFileHDF5 plug-in I have "Delete Driver File" = Yes

And the plug-in successfully writes the .h5 file

Regarding the third point (Attribute DriverFileName): 

In the ADPilatus plug-in, should I set "Auto Increment" to No?  Which will give me a fixed "FULL_FILE_NAME".  Of course, then this file keeps getting over-written and deleting it is less relevant.

What is the best way to handle this?

Thanks,

John Dobbins

Research Support Specialist

Cornell High Energy Synchrotron Source

Cornell University

www.chess.cornell.edu