Author: Bertrand, B.
Paper Title Page
MOPV034 Migration of Tango Controls Source Code Repositories 209
 
  • M. Liszcz, M. Celary, P.P. Goryl, K. Kedron
    S2Innovation, Kraków, Poland
  • G. Abeillé
    SOLEIL, Gif-sur-Yvette, France
  • B. Bertrand
    MAX IV Laboratory, Lund University, Lund, Sweden
  • R. Bourtembourg, A. Götz
    ESRF, Grenoble, France
  • T. Braun
    byte physics e.K., Berlin, Germany
  • A.F. Joubert
    SARAO, Cape Town, South Africa
  • A. López Sánchez, C. Pascual-Izarra, S. Rubio-Manrique
    ALBA-CELLS Synchrotron, Cerdanyola del Vallès, Spain
  • L. Pivetta
    Elettra-Sincrotrone Trieste S.C.p.A., Basovizza, Italy
 
  Funding: Tango Community
At the turn of 2020/2021, the Tango community faced the challenge of a massive migration of all Tango software repositories from GitHub to GitLab. The motivation has been a change in the pricing model of the Travis CI provider and the shutdown of the JFrog Bintray service used for artifact hosting. GitLab has been chosen as a FOSS-friendly platform for storing both the code and build artifacts and for providing CI/CD services. The migration process faced several challenges, both technical, like redesign and rewrite of CI pipelines, and non-technical, like coordination of actions impacting multiple interdependent repositories. This paper explains the strategies adopted for migration, the outcomes, and the impact on the Tango Controls collaboration.
 
poster icon Poster MOPV034 [0.181 MB]  
DOI • reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-MOPV034  
About • Received ※ 10 October 2021       Accepted ※ 04 November 2021       Issue date ※ 28 November 2021  
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)  
 
WEAR01 The Tango Controls Collaboration Status in 2021 544
 
  • A. Götz, R. Bourtembourg, D. Lacoste, N. Leclercq
    ESRF, Grenoble, France
  • G. Abeillé
    SOLEIL, Gif-sur-Yvette, France
  • B. Bertrand, V. Hardion
    MAX IV Laboratory, Lund University, Lund, Sweden
  • G. Brandl
    MLZ, Garching, Germany
  • T. Braun
    byte physics e.K., Berlin, Germany
  • P.P. Goryl, M. Liszcz
    S2Innovation, Kraków, Poland
  • A.F. Joubert, A.J. Venter
    SARAO, Cape Town, South Africa
  • C. Pascual-Izarra, S. Rubio-Manrique
    ALBA-CELLS Synchrotron, Cerdanyola del Vallès, Spain
  • L. Pivetta
    Elettra-Sincrotrone Trieste S.C.p.A., Basovizza, Italy
 
  The Tango Controls collaboration has continued to grow since ICALEPCS 2019. Multiple new releases were made of the stable release V9. The new versions include support for new compiler versions, new features and bug fixes. The collaboration has adopted a sustainable approach to kernel development to cope with changes in the community. New projects have adopted Tango Controls while others have completed commissioning of challenging new facilities. This paper will present the status of the Tango-Controls collaboration since 2019 and how it is helping new and old sites to maintain a modern control system.  
slides icon Slides WEAR01 [3.240 MB]  
DOI • reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-WEAR01  
About • Received ※ 10 October 2021       Revised ※ 15 October 2021       Accepted ※ 23 December 2021       Issue date ※ 25 February 2022
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)  
 
THBL01 Control System Management and Deployment at MAX IV 819
 
  • B. Bertrand, Á. Freitas, V. Hardion
    MAX IV Laboratory, Lund University, Lund, Sweden
 
  The control systems of big research facilities like synchrotron are composed of many different hardware and software parts. Deploying and maintaining such systems require proper workflows and tools. MAX IV has been using Ansible to manage and deploy its full control system, both software and infrastructure, for quite some time with great success. All required software (i.e. tango devices, GUIs…) used to be packaged as RPMs (Red Hat Package Manager) making deployment and dependencies management easy. Using RPMs brings many advantages (big community, well tested packages, stability) but also comes with a few drawbacks, mainly the dependency to the release cycle of the Operating System. The Python ecosystem is changing quickly and using recent modules can become challenging with RPMs. We have been investigating conda as an alternative package manager. Conda is a popular open-source package, dependency and environment management system. This paper will describe our workflow and experience working with both package managers.  
slides icon Slides THBL01 [5.899 MB]  
DOI • reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-THBL01  
About • Received ※ 10 October 2021       Accepted ※ 21 November 2021       Issue date ※ 12 February 2022  
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)  
 
THPV011 Notifications with Native Mobile Application 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 icon 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)  
 
FRBR04 Continuous Scans with Position Based Hardware Triggers 1069
 
  • H. Enquist, A. Bartalesi, B. Bertrand, J. Forsberg, Á. Freitas, V. Hardion, M. Lindberg, C. Takahashi
    MAX IV Laboratory, Lund University, Lund, Sweden
 
  At beamline end-stations, data taking that relies on traditional step scanning, in which motors are repeatedly started and stopped, leads to inefficient usage of the x-ray source. This also increases the risk of sample radiation damage. We have developed a system where scans are performed while continuously moving the motors. To ensure stable repeatable measurements, the detector triggers are generated, in hardware, from the motor encoder positions. Before the scan starts, a list of positions is generated and as the scan progresses a trigger is produced as each successive position in the list is reached. The encoder signals from the motors are connected both to the IcePAP motion controller for closed loop operation, and a PandABox which is used as the trigger source. Control is from Tango and Sardana with a TriggerGate controller that calculates the motor positions and configures the PandABox. The scanned motor can be either a single motor, for example a sample positioner, or a combined motion like a monochromator. When combined motions are required, these make use of the parametric trajectory mode of the IcePAP. This enables continuous scans of coupled axes with non-linear paths.  
slides icon Slides FRBR04 [1.685 MB]  
DOI • reference for this paper ※ https://doi.org/10.18429/JACoW-ICALEPCS2021-FRBR04  
About • Received ※ 10 October 2021       Revised ※ 14 October 2021       Accepted ※ 20 November 2021       Issue date ※ 13 December 2021
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)