| 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: | NDStats plugin shows huge numbers for Eiger detector (areaDetector 3.7) |
| From: | "Sobhani, Bayan via Tech-talk" <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Tue, 20 Aug 2019 13:48:54 +0000 |
|
I have an IOC running for an Eiger detector. The pixels are measured from -1.0 to 0.0. I think at least part of areaDetector recognizes this because when I set the Minimum and Maximum under “Display Controls” on the CSS screens, the picture
looks good. However, on the NDStats page, I see the minimum is 0, and the Maximum is 65535. I would expect the minimum to be -1.0, and the maximum to be 0. The Total is also a very large number (16407209312) – it was a much smaller number when I was
running an older version of Areadetector (I think 2.7). I thought the problem might be the Datatype – the DataType in the Stats plugin is UInt16. I attempted to change this to Float32 by writing to the Stats1:DataType PV, but it keeps reverting back to UInt16. Any ideas what could be causing the numbers in the Stats1 plugin to be these huge numbers? Alex |