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: | RE: NDStats plugin shows huge numbers for Eiger detector (areaDetector 3.7) |
From: | Mark Rivers via Tech-talk <[email protected]> |
To: | 'Bruno Martins' <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Tue, 20 Aug 2019 15:44:32 +0000 |
Ø
One possible workaround is to calculate stats on ROIs corresponding to the Eiger modules and have calc records to combine them. I just tested another workaround. Send the image through an ROI plugin, and set the DataTypeOut to Int32 rather than Automatic. Set the STATS plugin to get its data from the ROI plugin. Now it will get Int32 data, and all the pixels
that were 2^15-1 or 2^31-1 will be -1 and the statistics will be much more reasonable. Feeding this signed image into the display plugins (NDPluginStdArrays or NDPluginPva) will also help a lot in making autoscaled display intensities look good. Mark From: Bruno Martins <[email protected]>
Hi Alex, The SIMPLON API reference [1] states: "pixels that have a corresponding bit set in the pixel_mask are flagged with (2^bit_depth_image)-1". I agree with Mark's assessment that "we are stuck having the gaps and bad pixels be the largest positive
number". One possible workaround is to calculate stats on ROIs corresponding to the Eiger modules and have calc records to combine them. On Tue, Aug 20, 2019 at 10:29 AM Mark Rivers via Tech-talk <[email protected]> wrote:
|