EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20242025  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  <20242025 
<== Date ==> <== Thread ==>

Subject: Re: Adding additional fields to be archived in "policies.py"
From: Gerrit Kühn via Tech-talk <tech-talk at aps.anl.gov>
To: Timo Korhonen <Timo.Korhonen at ess.eu>
Cc: Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>
Date: Fri, 6 Sep 2024 10:47:09 +0200
Am Fri, 6 Sep 2024 07:47:19 +0000
schrieb Timo Korhonen <Timo.Korhonen at ess.eu>:

Hello Timo,

[...]

> You see the "severity" and "status" values, which in this case were both
> 0. 
> 
> You then of course need the additional metadata (HIHI,HIGH,LOW,LOLO) to
> tell what the alarm actually means. But this metadata is not saved with
> each sample.
> 
> I hope this helps.

Partly. :)
We have a different scenario here: We use grafana with the archiver
datasource plugin
(https://github.com/sasaki77/archiverappliance-datasource/) to build
dashboards from archiver data. We would like to display some kind of
additional information to show if the data is actually valid. So the first
idea was to use .STAT for this (which is not available by default). Is
there any other way to access this information via the plugin?

The IOC gets its data via network using streamdevice, so the reason for an
error would rather be a timeout or communication error which would
probably not show up in available fields like HIHI,HIGH,LOW,LOLO.


cu
  Gerrit

Attachment: smime.p7s
Description: S/MIME cryptographic signature


Replies:
Re: Adding additional fields to be archived in "policies.py" Timo Korhonen via Tech-talk
References:
Adding additional fields to be archived in "policies.py" Windsor Tanner via Tech-talk
Re: Adding additional fields to be archived in "policies.py" Michael Davidsaver
Re: Adding additional fields to be archived in "policies.py" Gerrit Kühn
Re: Adding additional fields to be archived in "policies.py" Timo Korhonen via Tech-talk

Navigate by Date:
Prev: Re: Adding additional fields to be archived in "policies.py" Timo Korhonen via Tech-talk
Next: Re: Adding additional fields to be archived in "policies.py" Timo Korhonen via Tech-talk
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  <20242025 
Navigate by Thread:
Prev: Re: Adding additional fields to be archived in "policies.py" Timo Korhonen via Tech-talk
Next: Re: Adding additional fields to be archived in "policies.py" Timo Korhonen via Tech-talk
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  <20242025 
ANJ, 11 Sep 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions ·
· Download · Search · IRMIS · Talk · Documents · Links · Licensing ·