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  <20212022  2023  2024  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Moving to phoebus alarm server
From: "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "Gotz, Malte" <malte.gotz at helmholtz-berlin.de>
Date: Tue, 13 Apr 2021 12:10:19 +0000
> ... I couldn’t find any pre-existing solution to converting alh config files to the phoebs/css xml format.
> ... Do you have scripts that build one xml file from fragments ...

The phoebus alarm server uses the same XML configuration file format as the earlier, Eclipse-based implementation.
The latter's AlarmConfigTool included an option to read the alh file format, see https://github.com/ControlSystemStudio/cs-studio/blob/master/applications/alarm/alarm-plugins/org.csstudio.alarm.beast.configtool/scripts/convert_alh.sh
I didn't have an operational motivation to port it to the phoebus code base, since I've personally never used it at our site.
Reasons:
The conversion from a basic ALH hierarchy of PVs into the XML format is pretty easy, you can do that with a python script in a day (and if you do, please email the result so I can add that to the new code base).
The real issue, however, is usually the conversion of related displays, where you need to for example convert some link that called a script for starting MEDM into the path to a converted display file. This is highly site-specific (and another reason for implementing the conversion tool in python so each site can easily adjust it to local needs).
Finally, the overall idea of the alarm system is not to add many PVs real fast, but instead spend some time on each alarm to come up with a good trigger PV, a useful guidance message, a suitable link to a related display and ideally another link to for example a web page that has more detail. See "Alarm Guidelines" on https://controlssoftware.sns.ornl.gov/training/2019_USPAS/ For us at the SNS that alone was enough reason to not simply import existing ALH config files but instead to start over with a new configuration. But again if you already have a perfect alarm configuration and would like to import, then I'd suggest implementing a python tool that converts the ALH config into the XML format which you can then import. Similarly, I use the export/import option of the alarm server to extract the config as XML for several purposes: Periodic backup, bulk update of for example telephone numbers, ..

Thanks,
Kay

References:
Moving to phoebus alarm server Gotz, Malte via Tech-talk

Navigate by Date:
Prev: Moving to phoebus alarm server Gotz, Malte via Tech-talk
Next: problems with running EPICS Gateway on virtual machines? Ru Igarashi 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  <20212022  2023  2024 
Navigate by Thread:
Prev: Moving to phoebus alarm server Gotz, Malte via Tech-talk
Next: problems with running EPICS Gateway on virtual machines? Ru Igarashi 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  <20212022  2023  2024 
ANJ, 13 Apr 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·