IBIC2016 - List of Keywords (luminosity)

Paper	Title	Other Keywords	Page
TUPG20	The CMS Beam Halo Monitor at the LHC: Implementation and First Measurements	detector, background, experiment, vacuum	364
	N. Tosi INFN-Bologna, Bologna, Italy
	A Cherenkov based detector system has been installed at the Large Hadron Collider (LHC), in order to measure the Machine Induced Background (MIB) for the Compact Muon Solenoid (CMS) experiment. The system is composed of forty identical detector units formed by a cylindrical Quartz radiator directly coupled to a Photomultiplier. These units are installed at a radius of 1.8m and a distance of 20.6 m from the CMS interaction point. The fast and direction-sensitive signal allows to measure incoming MIB particles while suppressing the much more abundant collision products and albedo particles, which reach the detector at a different time and from a different direction. The system readout electronics is based on the QIE10 ASIC and a uTCA based back-end, and it allows a continuous online measurement of the background rate separately per each bunch. The detector has been installed in 2015 and is now fully commissioned. Measurements demonstrating the capability of detecting anomalous beam conditions will be presented. on behalf of the CMS collaboration
	Poster TUPG20 [2.609 MB]
DOI •	reference for this paper ※ DOI:10.18429/JACoW-IBIC2016-TUPG20
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

TUPG30	Testing the Untestable: A Realistic Vision of Fearlessly Testing (Almost) Every Single Accelerator Component Without Beam and Continuous Deployment Thereof	hardware, software, operation, simulation	399
	A. Calia, K. Fuchsberger, M. Hostettler CERN, Geneva, Switzerland
	Whenever a bug of some piece of software or hardware stops beam operation, loss of time is rarely negligible and the cost (either in lost luminosity or real financial one) might be significant. Optimization of the accelerator availability is a strong motivation to avoid such kind of issues. Still, even at large accelerator labs like CERN, release cycles of many accelerator components are managed in a "deploy and pray" manner. In this paper we will give a short general overview on testing strategies used commonly in software development projects and illustrate their application on accelerator components, both hardware and software. Finally, several examples of CERN systems will be shown on which these techniques were or will be applied (LHC Beam-Based Feedbacks and LHC Luminosity Server) and describe why it is worth doing so.
DOI •	reference for this paper ※ DOI:10.18429/JACoW-IBIC2016-TUPG30
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

Paper

Title

Other Keywords

Page

TUPG20

The CMS Beam Halo Monitor at the LHC: Implementation and First Measurements

detector, background, experiment, vacuum

364

N. Tosi
INFN-Bologna, Bologna, Italy

A Cherenkov based detector system has been installed at the Large Hadron Collider (LHC), in order to measure the Machine Induced Background (MIB) for the Compact Muon Solenoid (CMS) experiment. The system is composed of forty identical detector units formed by a cylindrical Quartz radiator directly coupled to a Photomultiplier. These units are installed at a radius of 1.8m and a distance of 20.6 m from the CMS interaction point. The fast and direction-sensitive signal allows to measure incoming MIB particles while suppressing the much more abundant collision products and albedo particles, which reach the detector at a different time and from a different direction. The system readout electronics is based on the QIE10 ASIC and a uTCA based back-end, and it allows a continuous online measurement of the background rate separately per each bunch. The detector has been installed in 2015 and is now fully commissioned. Measurements demonstrating the capability of detecting anomalous beam conditions will be presented.
on behalf of the CMS collaboration

Poster TUPG20 [2.609 MB]

DOI •

reference for this paper ※ DOI:10.18429/JACoW-IBIC2016-TUPG20

Export •

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

TUPG30

Testing the Untestable: A Realistic Vision of Fearlessly Testing (Almost) Every Single Accelerator Component Without Beam and Continuous Deployment Thereof

hardware, software, operation, simulation

399

A. Calia, K. Fuchsberger, M. Hostettler
CERN, Geneva, Switzerland

Whenever a bug of some piece of software or hardware stops beam operation, loss of time is rarely negligible and the cost (either in lost luminosity or real financial one) might be significant. Optimization of the accelerator availability is a strong motivation to avoid such kind of issues. Still, even at large accelerator labs like CERN, release cycles of many accelerator components are managed in a "deploy and pray" manner. In this paper we will give a short general overview on testing strategies used commonly in software development projects and illustrate their application on accelerator components, both hardware and software. Finally, several examples of CERN systems will be shown on which these techniques were or will be applied (LHC Beam-Based Feedbacks and LHC Luminosity Server) and describe why it is worth doing so.

DOI •

reference for this paper ※ DOI:10.18429/JACoW-IBIC2016-TUPG30

Export •

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