ICALEPCS2023 - List of Authors (Rose, S.C.F.)

Paper	Title	Page
MO4BCO05	Apples to Oranges: A Comparison of EPICS Build and Deployment Systems	205
	S.C.F. Rose, D.H.C. Araujo, L.A. Mello Magalhães, A.L. Olsson ESS, Lund, Sweden
	ESS currently uses two different systems for managing the build and deployment of EPICS modules. Both of these use modules that are packaged and prepared to be dynamically loaded into soft IOCs, based on the require module developed at PSI. The difference is the deployment: For the accelerator, we use a custom utility to define and build an EPICS environment which is then distributed on a global shared filesystem to the production and lab networks. For the neutron instrumentation side, in contrast, we use conda to build individual EPICS environments for each IOC, where the underlying packages are stored on a shared artifactory server. In each case, the goal is to provide a repeatable and controllable mechanism to produce a consistent EPICS environment for IOCs in use at ESS. The difference (other than the tools and storage) is in some sense philosophical: should a software environment be defined at build-time or at run-time? In this presentation we will provide an overview of some of the challenges, contrasts, and lessons learned from these two different but related approaches to EPICS module deployment.
	Slides MO4BCO05 [0.819 MB]
DOI •	reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-MO4BCO05
About •	Received ※ 06 October 2023 — Accepted ※ 13 October 2023 — Issued ※ 24 October 2023
Cite •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

TH1BCO01	Five years of EPICS 7 - Status Update and Roadmap	1087
	R. Lange ITER Organization, St. Paul lez Durance, France L.R. Dalesio, M.A. Davidsaver, G.S. McIntyre Osprey DCS LLC, Ocean City, USA S.M. Hartman, K.-U. Kasemir ORNL, Oak Ridge, Tennessee, USA A.N. Johnson, S. Veseli ANL, Lemont, Illinois, USA H. Junkes FHI, Berlin, Germany T. Korhonen, S.C.F. Rose ESS, Lund, Sweden M.R. Kraimer Self Employment, Private address, USA K. Shroff BNL, Upton, New York, USA G.R. White SLAC, Menlo Park, California, USA
	Funding: Work supported in part by the U.S. Department of Energy under contracts DE-AC02-76SF00515 and DE-AC05-00OR22725. After its first release in 2017, EPICS version 7 has been introduced into production at several sites. The central feature of EPICS 7, the support of structured data through the new pvAccess network protocol, has been proven to work in large production systems. EPICS 7 facilitates the implementation of new functionality, including developing AI/ML applications in controls, managing large data volumes, interfacing to middle-layer services, and more. Other features like support for the IPv6 protocol and enhancements to access control have been implemented. Future work includes integrating a refactored API into the core distribution, adding modern network security features, as well as developing new and enhancing existing services that take advantage of these new capabilities. The talk will give an overview of the status of deployments, new additions to the EPICS Core, and an overview of its planned future development.
	Slides TH1BCO01 [0.562 MB]
DOI •	reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-TH1BCO01
About •	Received ※ 04 October 2023 — Revised ※ 12 October 2023 — Accepted ※ 19 November 2023 — Issued ※ 24 November 2023
Cite •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

THMBCMO11	Full Stack PLC to EPICS Integration at ESS	1216
	A. Rizzo, E.E. Foy, D. Hasselgren, A.Z. Horváth, A. Petrushenko, J.A. Quintanilla, S.C.F. Rose, A. Simelio ESS, Lund, Sweden
	The European Spallation Source is one of the largest science and technology infrastructure projects being built today. The Control System at ESS is then essential for the synchronisation and day-to-day running of all the equipment responsible for the production of neutrons for the experimental programs. The standardised PLC platform for ESS to handle slower signal comes from Siemens, while for faster data interchange with deterministic timing and higher processing power, from Beckoff/EtherCAT. All the Control Systems based on the above technologies are integrated using EPICS framework*. We will present how the full stack integration from PLC to EPICS is done at ESS using our standard Configuration Management Ecosystem. https://www.siemens.com/global/en/products/automation/systems/industrial/plc.html https://www.beckhoff.com/en-en/products/i-o/ethercat/ * https://epics-controls.org/
	Slides THMBCMO11 [0.178 MB]
	Poster THMBCMO11 [0.613 MB]
DOI •	reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-THMBCMO11
About •	Received ※ 05 October 2023 — Revised ※ 25 October 2023 — Accepted ※ 08 December 2023 — Issued ※ 18 December 2023
Cite •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

Paper

Title

Page

Apples to Oranges: A Comparison of EPICS Build and Deployment Systems

205

S.C.F. Rose, D.H.C. Araujo, L.A. Mello Magalhães, A.L. Olsson
ESS, Lund, Sweden

ESS currently uses two different systems for managing the build and deployment of EPICS modules. Both of these use modules that are packaged and prepared to be dynamically loaded into soft IOCs, based on the require module developed at PSI. The difference is the deployment: For the accelerator, we use a custom utility to define and build an EPICS environment which is then distributed on a global shared filesystem to the production and lab networks. For the neutron instrumentation side, in contrast, we use conda to build individual EPICS environments for each IOC, where the underlying packages are stored on a shared artifactory server. In each case, the goal is to provide a repeatable and controllable mechanism to produce a consistent EPICS environment for IOCs in use at ESS. The difference (other than the tools and storage) is in some sense philosophical: should a software environment be defined at build-time or at run-time? In this presentation we will provide an overview of some of the challenges, contrasts, and lessons learned from these two different but related approaches to EPICS module deployment.

Slides MO4BCO05 [0.819 MB]

DOI •

reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-MO4BCO05

About •

Received ※ 06 October 2023 — Accepted ※ 13 October 2023 — Issued ※ 24 October 2023

Cite •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

TH1BCO01

Five years of EPICS 7 - Status Update and Roadmap

1087

R. Lange
ITER Organization, St. Paul lez Durance, France
L.R. Dalesio, M.A. Davidsaver, G.S. McIntyre
Osprey DCS LLC, Ocean City, USA
S.M. Hartman, K.-U. Kasemir
ORNL, Oak Ridge, Tennessee, USA
A.N. Johnson, S. Veseli
ANL, Lemont, Illinois, USA
H. Junkes
FHI, Berlin, Germany
T. Korhonen, S.C.F. Rose
ESS, Lund, Sweden
M.R. Kraimer
Self Employment, Private address, USA
K. Shroff
BNL, Upton, New York, USA
G.R. White
SLAC, Menlo Park, California, USA

Funding: Work supported in part by the U.S. Department of Energy under contracts DE-AC02-76SF00515 and DE-AC05-00OR22725.
After its first release in 2017, EPICS version 7 has been introduced into production at several sites. The central feature of EPICS 7, the support of structured data through the new pvAccess network protocol, has been proven to work in large production systems. EPICS 7 facilitates the implementation of new functionality, including developing AI/ML applications in controls, managing large data volumes, interfacing to middle-layer services, and more. Other features like support for the IPv6 protocol and enhancements to access control have been implemented. Future work includes integrating a refactored API into the core distribution, adding modern network security features, as well as developing new and enhancing existing services that take advantage of these new capabilities. The talk will give an overview of the status of deployments, new additions to the EPICS Core, and an overview of its planned future development.

Slides TH1BCO01 [0.562 MB]

DOI •

reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-TH1BCO01

About •

Received ※ 04 October 2023 — Revised ※ 12 October 2023 — Accepted ※ 19 November 2023 — Issued ※ 24 November 2023

Cite •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

THMBCMO11

Full Stack PLC to EPICS Integration at ESS

1216

A. Rizzo, E.E. Foy, D. Hasselgren, A.Z. Horváth, A. Petrushenko, J.A. Quintanilla, S.C.F. Rose, A. Simelio
ESS, Lund, Sweden

The European Spallation Source is one of the largest science and technology infrastructure projects being built today. The Control System at ESS is then essential for the synchronisation and day-to-day running of all the equipment responsible for the production of neutrons for the experimental programs. The standardised PLC platform for ESS to handle slower signal comes from Siemens*, while for faster data interchange with deterministic timing and higher processing power, from Beckoff/EtherCAT**. All the Control Systems based on the above technologies are integrated using EPICS framework***. We will present how the full stack integration from PLC to EPICS is done at ESS using our standard Configuration Management Ecosystem.
* https://www.siemens.com/global/en/products/automation/systems/industrial/plc.html
** https://www.beckhoff.com/en-en/products/i-o/ethercat/
*** https://epics-controls.org/

Slides THMBCMO11 [0.178 MB]

Poster THMBCMO11 [0.613 MB]

DOI •

reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-THMBCMO11

About •

Received ※ 05 October 2023 — Revised ※ 25 October 2023 — Accepted ※ 08 December 2023 — Issued ※ 18 December 2023

Cite •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)