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

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

In that case I would say that the plugin should be enhanced to be able to get the status and severity fields. As I wrote, I am not familiar with the plugin so I cannot say how difficult that would be.

The important point is that the severity and status are "atomically" included in the data samples. If you pick them up as separate PVs, then you have to do (non-trivial) data sorting to figure out when the severity & status have changed.

Timo

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


Am Fri, 6 Sep 2024 09:09:18 +0000
schrieb Timo Korhonen <Timo.Korhonen at ess.eu <mailto:Timo.Korhonen at ess.eu>>:


> 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.


Unfortunately we did not find a way (so far) to access alarm status or
alarm serverity fields via the plugin. We can request data from PVs and
work with that (and set up alerts based on the data), but there is no
obvious way to access the other fields (unless they are "archived fields"
like HIHI etc.).


Maybe the plugin doesn't support this? In that case would could probably
fall back on creating an extra channel per device that reflects the error
status. Or would the first idea we had (simply adding PVNAME.STAT
explicitely to the archiver) work as well?




cu
Gerrit