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 Pearson, Matthew R.
- Navigate by Date:
- Prev:
Re: DC Power supplies with EPICS support Bruce Hill
- Next:
Re: areaDetector acquirePeriod and acquireTime Pearson, Matthew R.
- 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:
Newport 8742 Picomotor Controller D'Ewart, J. Mitch
- Next:
Re: areaDetector acquirePeriod and acquireTime Pearson, Matthew R.
- 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
|