1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | ADPilaus + NDFileHDF5 |
From: | John Dobbins via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Mon, 8 Feb 2021 16:54:46 +0000 |
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:
-------------------------------------------------------------
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
|