Re: Adding additional fields to be archived in "policies.py"

[Timo Korhonen via Tech-talk <tech-talk at aps.anl.gov>]

Correction:

I should have written alarm _severity_ below (NO_ALARM, MINOR, MAJOR and INVALID).
Alarm status is the other field that gives you more detailed information.

Sorry for the spam.

Timo

On 2024-09-06, 11:09, "Tech-talk on behalf of Timo Korhonen via Tech-talk" <tech-talk-bounces at aps.anl.gov <mailto:tech-talk-bounces at aps.anl.gov> on behalf of tech-talk at aps.anl.gov <mailto:tech-talk at aps.anl.gov>> wrote:


The data validity is included in the alarm concept by having the alarm status INVALID. See here for more details: 
https://urldefense.us/v3/__https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html <https://urldefense.us/v3/__https://docs.epics-controls.org/en/latest/process-database/EPICS_Process_Database_Concepts.html>*alarm-specification__;Iw!!G_uCfscf7eWS!ZdkeLEEiCbQ2_BdTJHku1FLAjrRImHdLJ45jYo9zmRX9sxEibTm6fEj-iZbEd3A4mWCxl79-PDc4fIg1yyFxFgRvWJfL$ 


Invalid is the "highest" alarm status which tells that the data is not to be trusted, typically if there is a problem in communicating with the device.


This does not rely on HIGH, HIHI, etc., but is shown in the severity field in the archived data.


I think that should do what you need - as far as I understand correctly. I am not familiar with the archiver datasource plugin though.


Timo


On 2024-09-06, 10:47, "Gerrit Kühn" <gerrit.kuehn at aei.mpg.de <mailto:gerrit.kuehn at aei.mpg.de> <mailto:gerrit.kuehn at aei.mpg.de <mailto:gerrit.kuehn at aei.mpg.de>>> wrote:




Am Fri, 6 Sep 2024 07:47:19 +0000
schrieb Timo Korhonen <Timo.Korhonen at ess.eu <mailto:Timo.Korhonen at ess.eu> <mailto:Timo.Korhonen at ess.eu <mailto: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://urldefense.us/v3/__https://github.com/sasaki77/archiverappliance-datasource/__;!!G_uCfscf7eWS!ZdkeLEEiCbQ2_BdTJHku1FLAjrRImHdLJ45jYo9zmRX9sxEibTm6fEj-iZbEd3A4mWCxl79-PDc4fIg1yyFxFoSoZLBY$ <https://urldefense.us/v3/__https://github.com/sasaki77/archiverappliance-datasource/__;!!G_uCfscf7eWS!ZdkeLEEiCbQ2_BdTJHku1FLAjrRImHdLJ45jYo9zmRX9sxEibTm6fEj-iZbEd3A4mWCxl79-PDc4fIg1yyFxFoSoZLBY$> <https://urldefense.us/v3/__https://github.com/sasaki77/archiverappliance-datasource/__;!!G_uCfscf7eWS!ZdkeLEEiCbQ2_BdTJHku1FLAjrRImHdLJ45jYo9zmRX9sxEibTm6fEj-iZbEd3A4mWCxl79-PDc4fIg1yyFxFoSoZLBY$ <https://urldefense.us/v3/__https://github.com/sasaki77/archiverappliance-datasource/__;!!G_uCfscf7eWS!ZdkeLEEiCbQ2_BdTJHku1FLAjrRImHdLJ45jYo9zmRX9sxEibTm6fEj-iZbEd3A4mWCxl79-PDc4fIg1yyFxFoSoZLBY$> >) 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