| 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: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | Florian Feldbauer <florian at ep1.ruhr-uni-bochum.de>, Mark Rivers <rivers at cars.uchicago.edu> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Thu, 29 Apr 2021 15:32:24 +0000 |
|
> from
our pixel sensor we just get a list of pixels that have seen a hit (row and column address).
That's exactly what the SNS beamline detectors report.
They send messages which basically contain a time stamp, some detail about the beam pulse, and then a list of
detector pixels which where hit and when exactly relative to the time stamp.
> We want to accumulate all hits and display them as 2d histogram (x-axis beeing column, y axis row and content of pixel = number of hits since start of the measurement).
Yes, we also need to to several things with that raw data. It's streamed into files for later analysis, that's the basic data acquisition job. It's put into X/Y histograms so you can display in near real time where the detector is hit, verify basic diffraction patterns. It's put into time-of-flight histograms, into histograms that accumulate the energy or 'D-space' or ... of the hits. But all that is done in IOCs, which then update an X/Y histogram image in basic area detector format, or waveforms for most of the rest. The display tool simply displays the image or waveform, it doesn't do any of the computations.
-Kay |