Re: [EXTERNAL] pv of Phoebus-product

["Kasemir, Kay via Tech-talk" <tech-talk@aps.anl.gov>]

18019393607@163.com wrote:

> ... hundreds of PV names ...


If you have a large list of PV names, you can use vi or python or .. to turn them into a config file for import:

<config name="Accelerator">
  <component name="Whatever">
      <pv name="PV1"/>
      <pv name="PV2"/>
...
      <pv name="PV9999"/>
  </component>
</config>

But if your goal is to quickly add hundreds of PVs, you missed the main point of the alarm system.
It's supposed to help operators do their job.
Each alarm PV should come with a link to a display that shows the affected subsystem in more detail, and guidance on what to do.
Instead of simply adding the first PV that comes to mind, you want to check if the limits are appropriate, whether they need to be operator-adjustable (add to screen and autosave), if you need HYST, if maybe some "raw" PVs need to be combined into a more useful alarm trigger PV (using calc records).
See alarm system guidelines on https://controlssoftware.sns.ornl.gov/training/2022_USPAS/
If you simply add hundreds of PVs, you likely get hundreds of useless alarms, where all that operators can do with them is disable.








From: Tech-talk <tech-talk-bounces@aps.anl.gov> on behalf of White via Tech-talk <tech-talk@aps.anl.gov>
Sent: Monday, April 10, 2023 9:37 PM
To: tech-talk@aps.anl.gov <tech-talk@aps.anl.gov>
Subject: [EXTERNAL] pv of Phoebus-product 
 

      Hi,   
      I have a question when I am using phobus, After setting up Phoebus and the Alarm Configuration and building the product. I found the PV names were only imported through XML files, when there are hundreds of PV names, is there a convenient and quick way to import PV without typing them one by one?
   
  Thanks,
   White