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: | areaDetector: ADBinX/Y and ADSizeX/Y interactions |
From: | Phil Atkin <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Thu, 14 Jan 2016 15:39:37 +0000 |
As I understand it, the ADSize parameters are intended to determine
the dimensions of the _physical_ region of the sensor that is read
out. That's why the constraint imposed is ADMin + ADSize <= ADMaxSize This means that the output array from an areaDetector driver should have dimensions given approximately by ADSize/ADBin for each dimension. Is this correct? Thanks, Phil Atkin --
Pixel Analytics is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP |