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  <20142015  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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: areaDetector acquirePeriod and acquireTime
From: "Pearson, Matthew R." <[email protected]>
To: Emma Shepherd <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Fri, 6 Jun 2014 13:55:13 +0000
Hi Emma,

How about having an additional frame rate parameter, or a maximum frame rate defined by a minimum acquire period? The Andor 3 drivers have a nice feature (provided by the manufacture API), which gives us the maximum frame rate when we change the image size and/or acquire times. 

In most cases the scientists want to keep dead time to a minimum anyway, so having the option to fix acquire period to the minimum possible would be useful. I've only seen acquire period set higher than it needs to be when there's issue with detector saturation. There may be complications with image size. If you read out a reduced image size the readout time might change, depending on the detector. Some detectors might have other options that change the readout time (eg. ADC sampling frequency).

Cheers,
Matt

On Jun 6, 2014, at 1:58 AM, Emma Shepherd <[email protected]> wrote:

> Hi Mark, all,
> 
> I've been thinking a bit about the relationship between the acquireTime and acquirePeriod parameters in areaDetector.
> 
> In some circumstances, scientists don't want any delay between frames, i.e. they want the acquirePeriod to be equal (or as close as possible) to the acquireTime.  They set this up for a given desired acquireTime, but are then sometimes caught out when they decrease the acquireTime but forget to decrease the acquirePeriod as well, so the overall frame rate is not what they expect.
> 
> I was wondering if people have a general way of dealing with this?  One possible solution would be to have an additional parameter to effectively disable the acquirePeriod, by forcing it to always be the minimum allowable value depending on the requirements of the particular detector and the current acquisition settings.  It would be nice to have a common solution across drivers/detectors if possible.
> 
> Cheers,
> Emma
> 
> 
> 



Replies:
RE: areaDetector acquirePeriod and acquireTime Mark Rivers
References:
areaDetector acquirePeriod and acquireTime Emma Shepherd

Navigate by Date:
Prev: areaDetector acquirePeriod and acquireTime Emma Shepherd
Next: wrong SADR field declaration in genSub haquin
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: areaDetector acquirePeriod and acquireTime Emma Shepherd
Next: RE: areaDetector acquirePeriod and acquireTime Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·