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: [EXTERNAL] Question about image widget in Phoebus |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "'Kasemir, Kay'" <kasemirk at ornl.gov>, Florian Feldbauer <florian at ep1.ruhr-uni-bochum.de> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Thu, 29 Apr 2021 14:27:07 +0000 |
Florian, If have you have an image from a pixel array detector displayed in Phoebus or another OPI that
IS a 2-D histogram. Most OPI displays render that as a black and white intensity or false color scale, where the intensity or color is proportional to the number of counts in each pixel. Is what you are asking for it to render instead as a 2-D bar graph, i.e. with rectangular prisms at each pixel whose height is proportional to the number of counts? Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Kasemir, Kay via Tech-talk Hi: Check the example displays. "Image Widget" demonstrates the Cursor Info PVs. Having said that, the basic idea is that the display simply displays PVs. It doesn't "do" anything, it won't compute a histogram. The cursor info PVs can used to send the location of a "click" inside the image to PVs on an IOC, and that IOC then computes something related to that location. If you want to compute a histogram for the horizontal or vertical line through the cursor, I think the area detector has the basic functionality. So image display -> cursor PVs
-> maybe some calc records to transform location -> area detector histogram plugin -> waveform for XYPlot. Other ways we use the cursor PVs on beamlines: One IOC reads the cursor location and updates a string PV with detector pixel information (which detector module, which 'tube', ...). Another more elaborate 'python IOC' turns the click on an image into motor commands to move the clicked location of the sample into the beam. But again the display doesn't "do" anything here beyond just writing the X/Y location of the click to PVs. -Kay From: Tech-talk <tech-talk-bounces at aps.anl.gov>
on behalf of Florian Feldbauer via Tech-talk <tech-talk at aps.anl.gov> Hey all, |