RE: Using Macros in the Alarm Tree

["Lloyd, Tate Wallace via Tech-talk" <tech-talk at aps.anl.gov>]

Thank you for your help, Kay.

 

Best,

Tate

 

From: Kasemir, Kay <kasemirk at ornl.gov>
Sent: Wednesday, June 7, 2023 5:27 AM
To: Lloyd, Tate Wallace <lloyd28 at llnl.gov>; tech-talk at aps.anl.gov
Subject: Re: Using Macros in the Alarm Tree

 

> Is there a way to implement macros in the alarm tree such that a single item with keywords can be added and several different PVs are included in that item?

 

You can export/import the alarm config in an XML format. That allows you to use for example python scripts to generate the alarm config XML from some site-specific database that has information about all your PVs, the channel finder, or whatever you want.

You can also make use of the hierarchical alarm tree structure to define links to overview displays or generic guidance just once on a higher level and have them be presented for all the subtree nodes.

 

Having said that, the goal should not be to rapidly add as many alarms as possible, using scripts and macros to expedite the process.

That way you’re likely to end up with an alarm configuration that is huge and useless.

It’s not a race where you need to add alarms faster than operators can handle them.

Instead, each alarm should be added after discussions between

• A subsystem expert who can describe the purpose of the alarm and provide handling guidance
• An EPICS person who can identify or maybe create a suitable alarm trigger PV, locate or maybe create a display that can be linked from the alarm
• Somebody from operations to check that the alarm description and handling guideline make sense to operators and maybe alert operators of the new alarm

 

In the overall process, a right-click in the alarm tree, “Add Item” to enter the PV name, guidance and display is just a 30 second operation.

For more, see “Alarm Guidelines” on https://controlssoftware.sns.ornl.gov/training/2022_USPAS/

 

-Kay