| 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: Receiving duplicate monitor values using CA PV Gateway |
| From: | "Johnson, Andrew N. via Tech-talk" <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Mon, 3 Jun 2019 22:31:53 +0000 |
|
Hi William, On 6/3/19 12:13 PM, Layne (US), William C via Tech-talk wrote:
Thanks; so the first monitor update is getting duplicated when it's coming from the CA gateway, and from Jure Varlec's post it sounds like this behaviour only occurs when running the gateway in its -no-cache mode. This confirms that the problem is internal to the gateway. We don't have a dedicated maintainer for the gateway, and Ralph Lange who is nominally responsible for it doesn't have much if any time to work on it. Nobody is going to have any objections to your looking into the internals of the code and proposing a fix if you feel so inclined. In any case Ralph is busy all this week organizing the EPICS Collaboration Meeting that is going on at ITER in France. If you are developing your own client software it should be relatively straightforward to detect and discard these duplications by comparing the monitor events timestamps, as long as you're using one of the data types which includes that information. - Andrew -- Complexity comes for free, Simplicity you have to work for. |