EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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: Re: ADPilaus + NDFileHDF5
From: John Dobbins via Tech-talk <tech-talk at aps.anl.gov>
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Mon, 8 Feb 2021 20:17:07 +0000
Mark,

Thanks. It works. I hadn't set the PV which points to the detector attributes file.

John

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Monday, February 8, 2021 1:13 PM
To: John Dobbins <john.dobbins at cornell.edu>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: RE: ADPilaus + NDFileHDF5
 

Hi John,

 

Ø  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.

 

There is no need to set AutoIncrement to No.  In you detector attribute XML file if you add this line:

 

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

 

then it should set that attribute to the name of the TIFF file corresponding to that NDArray, and then the HDF5 file plugin will delete the correct file, even if it has an incrementing file number in it.  Did you try that and see some issue?

 

Mark

 

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of John Dobbins via Tech-talk
Sent: Monday, February 8, 2021 10:55 AM
To: tech-talk at aps.anl.gov
Subject: ADPilaus + NDFileHDF5

 

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

 

 

 

 

 

 

 

 

References:
ADPilaus + NDFileHDF5 John Dobbins via Tech-talk
RE: ADPilaus + NDFileHDF5 Mark Rivers via Tech-talk
Navigate by Date:
Prev: Re: Question about databrowser of CSS Kasemir, Kay via Tech-talk
Next: RE: [EXTERNAL] Re: Question about compress records Guyotte, Greg via Tech-talk
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 
Navigate by Thread:
Prev: RE: ADPilaus + NDFileHDF5 Mark Rivers via Tech-talk
Next: caproto ioc alarm value leakage Troup, Euan (CASS, Marsfield) via Tech-talk
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 
ANJ, 08 Feb 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·