| 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] Re: How to archive PVs regularly even if they are not updating |
| From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | EPICS Tech Talk <tech-talk at aps.anl.gov>, Ralph Lange <ralph.lange at gmx.de> |
| Date: | Mon, 26 Sep 2022 15:13:06 +0000 |
|
On Mon, 26 Sept 2022 at 15:02, Shankar, Murali via Tech-talk <tech-talk at aps.anl.gov> wrote:
> If that's the case (noticeable change of behavior compared to the older archivers) - what is the difference between the two options?
I don't think it's a change from the Channel Archiver nor the RDB-based archive engine.
MONITOR: Channel uses monitor (for ADEL threshold) and tries to save every received value.
SCAN: Channel uses monitor (for ADEL threshold) and then saves the most recently received value every SCAN period.
SCAN does not perform a get or get-callback every SCAN period, and it also doesn't save the time of when it was scanned.
Instead, it would for example scan once every 5 minutes, and then write whatever the most recently received sample was .. if it changed.
-Kay
|