Abstract

The CMS Tracker was repaired, recalibrated and commissioned successfully for the second run of Large Hadron Collider. In 2015 the Tracker performed well with improved hit efficiency and spatial resolution compared to Run I and operated smoothly at lower temperatures after the successful recommissioning of the cooling system. This year the detector is expected to withstand luminosities that are beyond its design limits and will need a combined effort of both online and offline team to yield the high quality data that is required to reach our physics goals. We present the experience gained during the second run of the LHC and show the latest performance results of the CMS Tracker.

Highlights

  • In this paper is discussed the operational experience with the CMS Tracker gained during the long period of data taking at the Large Hadron Collider (LHC), with a particular focus on the Run II

  • The CMS Tracker is entirely based on silicon sensors, it is composed of a pixel detector, which is closest to the interaction point, and a micro-strip detector

  • The end-cap disks are composed of 24 blades arranged in a turbine-like geometry, each made of two panels placed back to back and containing a total number of 45 read-out chips (ROCs) (Figure 3)

Read more

Summary

Introduction

In this paper is discussed the operational experience with the CMS Tracker gained during the long period of data taking at the Large Hadron Collider (LHC), with a particular focus on the Run II. Most of the developments have been deployed in 2016, permitting to collect over 37 f b−1 of proton-proton collisions in a single year, already exceeding the total collected in Run I and in 2015 (Figure 1), the plan is to achieve 100 fb−1 by the end of 2018 This outstanding improvement of the beam conditions made 2016 a very challenging year for the Figure 1: Evolution of integrated luminosity in Run I and Run II data taking periods. CMS detector that faced a significant increase of occupancy and data rate, of particular impact on the Tracker system, being the closest to the interaction point

The CMS Tracker
Activities during the long shutdown
Pixel detector status and performance in Run II
Strip detector status and performance in Run II
Alignment
Track reconstruction performance
Pilot Blade and the Phase I upgrade
Summary and conclusions

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.