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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Is there a maximum threshold plugin for areaDetector? |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "Marco A. Barra Montevechi Filho" <marco.filho at lnls.br>, Wang Xiaoqiang <xiaoqiang.wang at psi.ch>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 15 Aug 2023 19:29:21 +0000 |
Folks, I have made the following changes to NDPluginProcess. Note that these break backwards compatibility, because I think it would otherwise add confusion and complexity.
I have attached these screenshots:
The new version is in the enhance_clip branch of ADCore on Github. https://github.com/areaDetector/ADCore/tree/enhance_clip Please let me know if this seems OK. Mark From: Marco A. Barra Montevechi Filho <marco.filho at lnls.br>
Specifically for Sirius applications, it would be useful to set all values above upper threshold to zero. If i understand the current plugin, it only replaces the
values above upper threshold with the upper threshold value itself, right? From: Mark Rivers <rivers at cars.uchicago.edu> I agree that the clipping should be made more flexible. I think it would be good to make this more general that replacing with 0 or the clip value. Users might want to replace the clip values with non-zero user-specified values, for example
-1, -2, etc. |
Attachment:
NDProcess.png
Description: NDProcess.png
Attachment:
WithoutClipping.jpg
Description: WithoutClipping.jpg
Attachment:
WithClipping.jpg
Description: WithClipping.jpg