Author: Lange, R.
Paper Title Page
TUMBCMO01 Extending the Coverage of Automated Testing in ITER’s Control System Software Distribution 338
 
  • R. Lange, H. Kim, A. Žagar
    ITER Organization, St. Paul lez Durance, France
  • V. Costa, J. Nieto, M. Ruiz
    UPM-I2A2, Madrid, Spain
 
  Funding: Partially funded by PID2019-108377RB-C33/MCIN/AEI (Agencia Estatal de Investigación) /10.13039/501100011033 and PID2022-137680OB-C33/MCIN/AEI /10.13039/501100011033 / FEDER/ and the European Union.
As part of the effort to standardize the control system environment of ITER’s in-kind delivered >170 plant systems, the Controls Division publishes CODAC Core System (CCS), a complete Linux-based control system software distribution. In the past, a large part of the integrated and end-to-end software testing for CCS was executed manually, using many long and complex test plan documents. As the project progress introduces increasing scope and higher quality requirements, that approach was not maintainable in the long term. ITER CODAC and its partners have started a multi-year effort converting manual tests to automated tests, inside the so-called Framework for Integration Testing (FIT), which itself is being developed and gradually extended as part of the effort. This software framework is complemented by a dedicated hardware test stand setup, comprising specimens of the different controllers and I/O hardware supported by CCS. FIT and the test stand will allow to run fully scripted hardware-in-the-loop (HIL) tests and allow functional verification of specific software modules as well as different end-to-end use cases.
 
slides icon Slides TUMBCMO01 [1.306 MB]  
poster icon Poster TUMBCMO01 [10.356 MB]  
DOI • reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-TUMBCMO01  
About • Received ※ 04 October 2023 — Revised ※ 10 October 2023 — Accepted ※ 28 November 2023 — Issued ※ 09 December 2023
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)  
 
TUSDSC08 Phoebus Tools and Services 944
 
  • K. Shroff
    BNL, Upton, New York, USA
  • T. Ashwarya
    FRIB, East Lansing, Michigan, USA
  • T.M. Ford
    LBNL, Berkeley, California, USA
  • K.-U. Kasemir
    ORNL, Oak Ridge, Tennessee, USA
  • R. Lange
    ITER Organization, St. Paul lez Durance, France
  • G. Weiss
    ESS, Lund, Sweden
 
  The Phoebus toolkit consists of a variety of control system applications providing user interfaces to control systems and middle-layer services. Phoebus is the latest incarnation of Control System Studio (CS-Studio), which has been redesigned replacing the underlying Eclipse RCP framework with standard Java alternatives like SPI, preferences, etc. Additionally the GUI toolkit was switched from SWT to JavaFX. This new architecture has not only simplified the development process while preserving the extensible and pluggable aspects of RCP, but also improved the performance and reliability of the entire toolkit. The Phoebus technology stack includes a set of middle-layer services that provide functionality like archiving, creating and restoring system snapshots, consolidating and organizing alarms, user logging, name lookup, etc. Designed around modern and widely used web and storage technologies like Spring Boot, Elastic, MongoDB, Kafka, the Phoebus middle-layer services are thin, scalable, and can be easily incorporated in CI/CD pipelines. The clients in Phoebus leverage the toolkit’s integration features, including common interfaces and utility services like adapter and selection, to provide users with a seamless experience when interacting with multiple services and control systems. This presentation aims to provide an overview of the Phoebus technology stack, highlighting the benefits of integrated tools in Phoebus and the microservices architecture of Phoebus middle-layer services.  
poster icon Poster TUSDSC08 [0.816 MB]  
DOI • reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-TUSDSC08  
About • Received ※ 06 October 2023 — Revised ※ 09 October 2023 — Accepted ※ 23 November 2023 — Issued ※ 30 November 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 icon 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)