EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame
From: "Ivashkevych, Oksana 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: Tue, 23 Feb 2021 19:21:35 +0000

Hi Mark,

Thank you very much for configuration suggestion and clarification!

 

All needed stats work for me as PARAM now, as well as 4 ROI sizes and positions.

 

Oksana

 

 

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Tuesday, February 23, 2021 11:45 AM
To: Ivashkevych, Oksana <oksana at bnl.gov>
Cc: tech-talk at aps.anl.gov
Subject: RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame

 

Hi Oksana,

 

You can set up the plugin chain like this:

 

PIL->ROISTAT1->FileHDF1

 

In the detector Attributes.xml file remove all of the entries for the statistics.

 

In the ROISTAT1 you create a new attributes XML file that uses TYPE=PARAM to add the TOTAL and MEAN for each of the 4 ROIs defined in that plugin.  The ROISTAT1 plugin will now add its attributes to those added by the PIL detector driver and they will be written to the HDF5 file.

 

You no longer need to use the ROI1-4 or STATS1-4 plugins.

 

If you use the ROI and STATS plugins then you cannot use PARAM, you need to use EPICS_PV, which can have some latency as you have observed.

 

Mark

 

 

From: Ivashkevych, Oksana <oksana at bnl.gov>
Sent: Tuesday, February 23, 2021 10:33 AM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk at aps.anl.gov
Subject: RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame

 

Hi Mark,

 

They are interested in total counts and max_count from their 4 ROIs. ROI_Start, and ROI_SIZE I can take from “EPICS_PV”.

I understand same things can be archived with ROIStats, which would be fine too.

 

Thank you

Oksana  

 

 

> -----Original Message-----

> From: Mark Rivers <rivers at cars.uchicago.edu>

> Sent: Tuesday, February 23, 2021 11:21 AM

> To: Ivashkevych, Oksana <oksana at bnl.gov>

> Cc: tech-talk at aps.anl.gov

> Subject: Re: Saving hdf5 ADPilatus images along with ROI and stats data from

> the same frame

>

> Hi Oksana,

>

>

> type=PARAM can only be used for parameters generated by that plugin or

> driver, not by other plugins.

>

>

> However, you may be able to do what you want by changing your plugin

> chain.

>

>

> - Can you please diagram you plugin chain?

>

> - Are you using both the NDPluginStats and NDPluginROIStats plugin?  If so, is

> this necessary?

>

> - Is the HDF5 file saving the entire image, or just a specific ROI?

>

> Mark

>

>

> ________________________________

> From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Ivashkevych,

> Oksana via Tech-talk <tech-talk at aps.anl.gov>

> Sent: Tuesday, February 23, 2021 10:05 AM

> To: Tech-talk

> Subject: Saving hdf5 ADPilatus images along with ROI and stats data from the

> same frame

>

>

> Hello,

>

> I am trying to configure hdf5 plugin to save N images with 4 ROI data (start,

> size), and 4 Stats, connected to ROIs ( total , maxValue).

>

>

>

> I have created Attributes.xml file  following example from ADSimDetector.

> type="EPICS_PV" works, however type="PARAM" does not for parameters

> from areaDetector/ADCore/ADApp/pluginSrc/, but does work for params

> from areaDetector/ADCore/ADApp/ADSrc/.

>

>

>

> It looks like with "EPICS_PV" type statistics data come from the previous

> frame.

>

>

>

> I was wondering if there is something I am missing, or there are other ways

> to get the correct statistics into the hdf5 file. I have tried using Stats,

> ROIStats, and ROI plugins.

>

> The green attributes are correctly saved, others show NaN in hdf5 file.

>

>

>

> I have ADCore 3.6.0; ADPilatus 2.6.0

>

> Thank you

>

>

>

> Attributes.xml:

>

>

>

> <?xml version="1.0" standalone="no" ?>

>

> <!-- Attributes -->

>

> <Attributes

>

>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

>

>

> xsi:noNamespaceSchemaLocation="../../../../../ADCore/XML_schema/NDAtt

> ributes.xsd"

>

>     >

>

>     <Attribute name="DriverFileName"  type="PARAM"

> source="FULL_FILE_NAME"                       datatype="STRING"

> description="Driver file name"/>

>

>     <Attribute name="ROI0Size"      type="PARAM"    source="DIM0_SIZE"

> datatype="INT"     description="X size ROI 0"/>

>

>     <Attribute name="ROI0Mean"      type="PARAM"

> source="MEAN_VALUE"              datatype="DOUBLE"     description="Mean

> value ROI 0"/>

>

>     <Attribute name="ROI1Mean"      type="PARAM"

> source="MEAN_VALUE" addr="1"     datatype="DOUBLE"

> description="Mean value ROI 0"/>

>

>     <Attribute name="_ROI0Total"     type="PARAM"

> source="ROISTAT_TOTAL"                   datatype="DOUBLE"     description="Total

> counts ROI 0"/>

>

>     <Attribute name="_ROI1Total"     type="PARAM"

> source="ROISTAT_TOTAL"      addr="1"     datatype="DOUBLE"

> description="Total counts ROI 1"/>

>

>     <Attribute name="MaxSizeX"            type="PARAM"

> source="MAX_SIZE_X"                   datatype="INT"        description="Detector X

> size"/>

>

>     <Attribute name="MaxSizeY"            type="PARAM"

> source="MAX_SIZE_Y"                   datatype="INT"        description="Detector Y

> size"/>

>

>     <Attribute name="CameraModel"         type="PARAM"    source="MODEL"

> datatype="STRING"     description="Camera model"/>

>

>     <Attribute name="AttributesFileParam"  type="PARAM"

> source="ND_ATTRIBUTES_FILE"            datatype="STRING"

> description="Attributes file param"/>

>

>     <Attribute name="CameraManufacturer"  type="PARAM"

> source="MANUFACTURER"                 datatype="STRING"

> description="Camera manufacturer"/>

>

> </Attributes>

>

>

>

 


References:
Saving hdf5 ADPilatus images along with ROI and stats data from the same frame Ivashkevych, Oksana via Tech-talk
Re: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame Mark Rivers via Tech-talk
RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame Ivashkevych, Oksana via Tech-talk
RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame Mark Rivers via Tech-talk

Navigate by Date:
Prev: RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame Mark Rivers via Tech-talk
Next: pfeiffer TPG 366 Maxiguage Epics support Vishnu Patel 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  <20212022  2023  2024 
Navigate by Thread:
Prev: RE: Saving hdf5 ADPilatus images along with ROI and stats data from the same frame Mark Rivers via Tech-talk
Next: pfeiffer TPG 366 Maxiguage Epics support Vishnu Patel 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  <20212022  2023  2024 
ANJ, 24 Feb 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·