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 | 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] CA gateway chaining |
From: | "Pearson, Matthew R. via Core-talk" <core-talk at aps.anl.gov> |
To: | Timo Korhonen <Timo.Korhonen at ess.eu>, Ralph Lange <ralph.lange at gmx.de> |
Cc: | "core-talk at aps.anl.gov" <core-talk at aps.anl.gov> |
Date: | Mon, 1 Nov 2021 17:19:07 +0000 |
Hi, We have seen similar issues and one way we dealt with it was to provide a heavily re-binned array for use via gateways. Inside the beamline network we provide both a full un-binned array, hidden behind ‘detailed’ buttons, as well as the
re-binned array screens that users will first encounter on higher level screens. We also limited the array size that the gateway will transmit, so some of the larger arrays don’t work which forces people to view the re-binned arrays.
Also, depending on the original data type and software, you can ‘compress’ the array data from 16 or 32-bit down to 8-bit data by re-scaling it to 0-255, like a JPEG image. Then the waveform data type can be set to UCHAR.
The above only works if the waveforms are simply for visualization. Cheers, Matt From: Core-talk <core-talk-bounces at aps.anl.gov>
On Behalf Of Timo Korhonen via Core-talk Right, this is the way we are going for now. It is not exactly trivial to manage but should be doable.
Thanks, TImo From:
Core-talk <core-talk-bounces at aps.anl.gov>
on behalf of EPICS Core Talk <core-talk at aps.anl.gov> On Wed, 27 Oct 2021 at 10:49, Timo Korhonen via Core-talk <core-talk at aps.anl.gov> wrote:
One way to mitigate this - I think this approach was implemented at some point at the SLS - is to route the large array channels through a dedicated separate gateway instance. (Ease of configuration depends on your naming convention.) Cheers, |