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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Count record that resets by date |
From: | Daniel Cuneo via Tech-talk <[email protected]> |
To: | Matt Newville <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Thu, 14 Mar 2019 11:32:03 -0700 |
Thanks Diego, your solution is similar to Eric's. Being still fairly new to EPICS, I'm getting a lot out of talking myself through these examples.I like the idea of having no other dependencies than base. This IOC runs on a small pizza box computer and I'd like to avoid building anything other than base if possible.The PVs are archived by the Archiver Appliance. I do have access to whatever report I want to generate via the rest API. This works great for me, but fails when I want to share this information with the EPS manager and other stake holders.Cheers,dpcOn Thu, Mar 14, 2019 at 4:32 AM Matt Newville <[email protected]> wrote:Daniel,On Wed, Mar 13, 2019 at 4:02 PM Daniel Cuneo via Tech-talk <[email protected]> wrote:Hi all,I'd like to create a database record that counts based on a forward link. This record would need to reset back to zeroat 12AM every day.Use case, is where a beam line user hits a reset button repeatably (tied to a bo record) as a work around for something that is broken.I'd like to track these resets.Is there a way to do this with base?I'm considering writing a C subroutine for this is it doesn't already exist.Cheers!dpcIf the use-case is to track resets of a bo record, why not use a script that sets up a monitor on the bo record and writes the value and timestamp of each event to a file? Or you could add the bo record to whatever archiver you're using and extract the events from that. Either way, such an event log would let you can slice the event data any way you want (not just "per day") and you haven't erased the information every day at midnight.--Matt Newville