ICALEPCS2021 - List of Keywords (ion-source)

Paper	Title	Other Keywords	Page
WEBR03	The Fast Protection System for CSNS Accelerator	hardware, operation, power-supply, linac	593
	Y.L. Zhang, D.P. Jin, P. Zhu IHEP, Beijing, People’s Republic of China
	The fast protection system for CSNS accelerator is a FPGA based protection system. The VME bus and SFP was adopted by the FPS. The FPS includes one central station and several sub-stations, and connnections between the central and the sub-stations are in star style. Two kinds of beam stopping modes are designed and implemented by FPS, one is the transient beam stopping and auto recovery mode, the other is the permanent beam stopping mode. The measured response time for the FPS is less than 1.5 micro-seconds.
	Slides WEBR03 [2.773 MB]
DOI •	reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-WEBR03
About •	Received ※ 19 October 2021 Revised ※ 25 January 2022 Accepted ※ 06 February 2022 Issue date ※ 11 February 2022
Cite •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPV018	The Linac4 Source Autopilot	controls, framework, linac, status	665
	M. Peryt, M. Hrabia, D. Noll, R. Scrivens CERN, Geneva, Switzerland
	The Linac4 source is a 2MHz, RF driven, H⁻ ion source, using caesium injection to enhance H⁻ production and lower the electron to H⁻ ratio. The source operates with 800µs long pulses at 1.2 second intervals. The stability of the beam intensity from the source requires adjustment of parameters like RF power used for plasma heating. The Linac4 Source Autopilot improves the stability and uptime of the source, by using high-level automation to monitor and control Device parameters of the source, in a time range of minutes to days. This paper describes the Autopilot framework, which incorporates standard CERN accelerator Controls infrastructure, and enables users to add domain specific code for their needs. User code typically runs continuously, adapting Device settings based on acquisitions. Typical use cases are slow feedback systems and procedure automation (e.g. resetting equipment). The novelty of the Autopilot is the successful integration of the Controls software based predominantly on Java technologies, with domain specific user code written in Python. This allows users to leverage a robust Controls infrastructure, with minimal effort, using the agility of the Python ecosystem.
	Poster WEPV018 [4.371 MB]
DOI •	reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-WEPV018
About •	Received ※ 10 October 2021 Revised ※ 19 October 2021 Accepted ※ 22 December 2021 Issue date ※ 31 December 2021
Cite •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

THPV011	Notifications with Native Mobile Application	site, controls, EPICS, software	883
	B. Bertrand, J. Forsberg MAX IV Laboratory, Lund University, Lund, Sweden E. Laface, G. Weiss ESS, Lund, Sweden
	Notifications are an essential part of any control system. Many people want to be notified of specific events. There are several ways to send notifications: SMS, e-mails or messaging applications like Slack and Telegram are some common ones. Those solutions frequently require some central configuration to record who will receive messages, which is difficult to maintain. ESS developed a native mobile application, both for iOS and Android, to manage notifications. The application allows the users to subscribe to the topics they are interested in, removing the need for a central configuration. A web server is used as gateway to send all notifications following Apple and Google protocols. This server exposes a REST API that is used both by clients to send messages and mobile applications to retrieve and manage those messages. This paper will detail the technical implementation as well as the lessons learnt from this approach.
	Poster THPV011 [6.079 MB]
DOI •	reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-THPV011
About •	Received ※ 09 October 2021 Accepted ※ 21 November 2021 Issue date ※ 05 January 2022
Cite •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

Paper

Title

Other Keywords

Page

WEBR03

The Fast Protection System for CSNS Accelerator

hardware, operation, power-supply, linac

593

Y.L. Zhang, D.P. Jin, P. Zhu
IHEP, Beijing, People’s Republic of China

The fast protection system for CSNS accelerator is a FPGA based protection system. The VME bus and SFP was adopted by the FPS. The FPS includes one central station and several sub-stations, and connnections between the central and the sub-stations are in star style. Two kinds of beam stopping modes are designed and implemented by FPS, one is the transient beam stopping and auto recovery mode, the other is the permanent beam stopping mode. The measured response time for the FPS is less than 1.5 micro-seconds.

Slides WEBR03 [2.773 MB]

DOI •

reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-WEBR03

About •

Received ※ 19 October 2021 Revised ※ 25 January 2022 Accepted ※ 06 February 2022 Issue date ※ 11 February 2022

Cite •

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

WEPV018

The Linac4 Source Autopilot

controls, framework, linac, status

665

M. Peryt, M. Hrabia, D. Noll, R. Scrivens
CERN, Geneva, Switzerland

The Linac4 source is a 2MHz, RF driven, H⁻ ion source, using caesium injection to enhance H⁻ production and lower the electron to H⁻ ratio. The source operates with 800µs long pulses at 1.2 second intervals. The stability of the beam intensity from the source requires adjustment of parameters like RF power used for plasma heating. The Linac4 Source Autopilot improves the stability and uptime of the source, by using high-level automation to monitor and control Device parameters of the source, in a time range of minutes to days. This paper describes the Autopilot framework, which incorporates standard CERN accelerator Controls infrastructure, and enables users to add domain specific code for their needs. User code typically runs continuously, adapting Device settings based on acquisitions. Typical use cases are slow feedback systems and procedure automation (e.g. resetting equipment). The novelty of the Autopilot is the successful integration of the Controls software based predominantly on Java technologies, with domain specific user code written in Python. This allows users to leverage a robust Controls infrastructure, with minimal effort, using the agility of the Python ecosystem.

Poster WEPV018 [4.371 MB]

DOI •

reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-WEPV018

About •

Received ※ 10 October 2021 Revised ※ 19 October 2021 Accepted ※ 22 December 2021 Issue date ※ 31 December 2021

Cite •

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

THPV011

Notifications with Native Mobile Application

site, controls, EPICS, software

883

B. Bertrand, J. Forsberg
MAX IV Laboratory, Lund University, Lund, Sweden
E. Laface, G. Weiss
ESS, Lund, Sweden

Notifications are an essential part of any control system. Many people want to be notified of specific events. There are several ways to send notifications: SMS, e-mails or messaging applications like Slack and Telegram are some common ones. Those solutions frequently require some central configuration to record who will receive messages, which is difficult to maintain. ESS developed a native mobile application, both for iOS and Android, to manage notifications. The application allows the users to subscribe to the topics they are interested in, removing the need for a central configuration. A web server is used as gateway to send all notifications following Apple and Google protocols. This server exposes a REST API that is used both by clients to send messages and mobile applications to retrieve and manage those messages. This paper will detail the technical implementation as well as the lessons learnt from this approach.

Poster THPV011 [6.079 MB]

DOI •

reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-THPV011

About •

Received ※ 09 October 2021 Accepted ※ 21 November 2021 Issue date ※ 05 January 2022

Cite •

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