Approval: Plots and Captions Tracker Alignment Run 2

Figure Caption
mean_dxy_phi_vs_lumi.png The mean of the average impact parameter in the transverse plane $d_{xy}$ as a function of processed luminosity. Only tracks with transverse momentum $p_{T}$ > 3 GeV are considered. The vertical black lines indicate the first processed run for 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate a change in the pixel tracker calibration. The blue points correspond to the results with the alignment constants used during data-taking, the red points to the 2016, 2017 and 2018 End-Of-Year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), and the green points to the results obtained in the Run-2 Legacy alignment procedure. During the LHC shutdown in winter 2016/17, the inner component (pixel detector) of the CMS tracking detector was replaced. The first few inverse picobarns of the 2017 pp collision run have been devoted to the commissioning of the new detector, resulting in sub-optimal tracking performance. This is visible in degraded impact parameter bias around the 36 fb${}^{\text{-1}}$ mark. Apart from this short period, aligning the tracker improves the mean of this distribution. Short IOVs with suboptimal configuration of the pixel local reconstruction (e.g. different high-voltage settings, inconsistent local reconstruction with alignment) can give rise to isolated peaks in the trends, especially during data taking. The suboptimal performance of the alignment during data taking at the beginning of 2018 is caused by the fact that the alignment was not updated by the prompt calibration loop (PCL).
mean_dz_phi_vs_lumi.png The mean of the average impact parameter in the longitudinal plane $d_{z}$ as a function of processed luminosity. Only tracks with transverse momentum $p_{T}$ > 3 GeV are considered. The vertical black lines indicate the first processed run for 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate a change in the pixel tracker calibration. The blue points correspond to the results with the alignment constants used during data-taking, the red points to the 2016, 2017 and 2018 End-Of-Year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), and the green points to the results obtained in the Run-2 Legacy alignment procedure. During the LHC shutdown in winter 2016/17, the inner component (pixel detector) of the CMS tracking detector was replaced. The first few inverse picobarns of the 2017 pp collision run have been devoted to the commissioning of the new detector, resulting in sub-optimal tracking performance. This is visible in degraded impact parameter bias around the 36 fb${}^{\text{-1}}$ mark. Apart from this short period, aligning the tracker improves the mean of this distribution. Short IOVs with suboptimal configuration of the pixel local reconstruction (e.g. different high-voltage settings, inconsistent local reconstruction with alignment) can give rise to isolated peaks in the trends, especially during data taking. The suboptimal performance for the alignment during data taking at the beginning of 2016 is due to relative misalignment of the two half-barrels of the pixel detector along the z-direction. This was not corrected by the alignment in the prompt calibration loop (PCL), which was not active in that period.
RMS_dxy_phi_vs_lumi.png The RMS of the average impact parameter in the transverse plane $d_{xy}$ in bins of the track azimuth $\phi$, as a function of processed luminosity. Only tracks with transverse momentum $p_{T}$ > 3 GeV are considered. The vertical black lines indicate the first processed run for 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate a change in the pixel tracker calibration. The blue points correspond to the results with the alignment constants used during data-taking, the red points to the 2016, 2017 and 2018 End-Of-Year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), and the green points to the results obtained in the Run-2 Legacy alignment procedure. During the LHC shutdown in winter 2016/17, the inner component (pixel detector) of the CMS tracking detector was replaced. The first few inverse picobarns of the 2017 pp collision run have been devoted to the commissioning of the new detector, resulting in sub-optimal tracking performance. This is visible in degraded impact parameter bias around the 36 fb${}^{\text{-1}}$ mark. Apart from this short period, aligning the tracker improves the mean of this distribution. Short IOVs with suboptimal configuration of the pixel local reconstruction (e.g. different high-voltage settings, inconsistent local reconstruction with alignment) can give rise to isolated peaks in the trends, especially during data taking. The suboptimal performance of the alignment during data taking at the beginning of 2018 is caused by the fact that the alignment was not updated by the prompt calibration loop (PCL). The slopes for the alignment during data taking visible between two pixel calibration updates are due to radiation effects, causing rapid changes of the Lorentz drift. This effect can only be corrected by aligning with a finer granularity than the automated alignment (PCL) implements.
RMS_dz_phi_vs_lumi.png The RMS of the average impact parameter in the longitudinal plane $d_{z}$ in bins of the track azimuth $\phi$, as a function of processed luminosity. Only tracks with transverse momentum $p_{T}$ > 3 GeV are considered. The vertical black lines indicate the first processed run for 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate a change in the pixel tracker calibration. The blue points correspond to the results with the alignment constants used during data-taking, the red points to the 2016, 2017 and 2018 End-Of-Year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), and the green points to the results obtained in the Run-2 Legacy alignment procedure. During the LHC shutdown in winter 2016/17, the inner component (pixel detector) of the CMS tracking detector was replaced. The first few inverse picobarns of the 2017 pp collision run have been devoted to the commissioning of the new detector, resulting in sub-optimal tracking performance. This is visible in degraded impact parameter bias around the 36 fb${}^{\text{-1}}$ mark. Apart from this short period, aligning the tracker improves the mean of this distribution. Short IOVs with suboptimal configuration of the pixel local reconstruction (e.g. different high-voltage settings, inconsistent local reconstruction with alignment) can give rise to isolated peaks in the trends, especially during data taking.
RMS_dxy_eta_vs_lumi.png The RMS of the average impact parameter in the transverse plane $d_{xy}$ in bins of the track pseudorapidity $\eta$, as a function of processed luminosity. Only tracks with transverse momentum $p_{T}$ > 3 GeV are considered. The vertical black lines indicate the first processed run of the 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate a change in the pixel tracker calibration. The blue points correspond to the results with the alignment constants used during data-taking, the red points to the 2016, 2017 and 2018 End-Of-Year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), and the green points to the results obtained in the Run-2 Legacy alignment procedure. During the LHC shutdown in winter 2016/17, the inner component (pixel detector) of the CMS tracking detector was replaced. The first few inverse picobarns of the 2017 pp collision run have been devoted to the commissioning of the new detector, resulting in sub-optimal tracking performance. This is visible in degraded impact parameter bias around the 36 fb${}^{\text{-1}}$ mark. Apart from this short period, aligning the tracker improves the mean of this distribution. Short IOVs with suboptimal configuration of the pixel local reconstruction (e.g. different high-voltage settings, inconsistent local reconstruction with alignment) can give rise to isolated peaks in the trends, especially during data taking.
RMS_dz_eta_vs_lumi.png The RMS of the average impact parameter in the longitudinal plane $d_{z}$ in bins of the track pseudorapidity $\eta$, as a function of processed luminosity. Only tracks with transverse momentum $p_{T}$ > 3 GeV are considered. The vertical black lines indicate the first processed run of the 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate a change in the pixel tracker calibration. The blue points correspond to the results with the alignment constants used during data-taking, the red points to the 2016, 2017 and 2018 End-Of-Year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), and the green points to the results obtained in the Run-2 Legacy alignment procedure. During the LHC shutdown in winter 2016/17, the inner component (pixel detector) of the CMS tracking detector was replaced. The first few inverse picobarns of the 2017 pp collision run have been devoted to the commissioning of the new detector, resulting in sub-optimal tracking performance. This is visible in degraded impact parameter bias around the 36 fb${}^{\text{-1}}$ mark. Apart from this short period, aligning the tracker improves the mean of this distribution. Short IOVs with suboptimal configuration of the pixel local reconstruction (e.g. different high-voltage settings, inconsistent local reconstruction with alignment) can give rise to isolated peaks in the trends, especially during data taking.
baryCentre_x_BPIX_2016+2017+2018_IntegratedLumi.png Barycentre position of the barrel pixel detector as a function of the integrated luminosity, determined as the centre-of-gravity of barrel pixel modules only. The vertical black solid lines indicate the first processed run of the 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate changes in the pixel calibration. The blue line corresponds to the results with the alignment constants used during data taking, the red line corresponds to the results with alignment constants during the 2016, 2017 and 2018 End-of-year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), the green line corresponds to the results with alignment constants as obtained in the Run-2 Legacy alignment procedures. Large position differences at the beginning of 2017 and 2018 data taking periods are caused by the fact that the pixel detector was extracted during the shutdowns and then re-installed, in occasion of the Phase-1 upgrade in 2017, and for module replacements in 2018.
baryCentre_y_BPIX_2016+2017+2018_IntegratedLumi.png Barycentre position of the barrel pixel detector as a function of the integrated luminosity, determined as the centre-of-gravity of barrel pixel modules only. The vertical black solid lines indicate the first processed run of the 2016, 2017 and 2018 data-taking period, respectively. The vertical dotted lines indicate changes in the pixel calibration. The blue line corresponds to the results with the alignment constants used during data taking, the red line corresponds to the results with alignment constants during the 2016, 2017 and 2018 End-of-year (EOY) re-reconstruction (notice there is no EOY re-reconstruction for the last 33 fb${}^{\text{-1}}$ of data-taking in 2018), the green line corresponds to the results with alignment constants as obtained in the Run-2 Legacy alignment procedures. Large position differences at the beginning of 2017 and 2018 data taking periods are caused by the fact that the pixel detector was extracted during the shutdowns and then re-installed, in occasion of the Phase-1 upgrade in 2017, and for module replacements in 2018.
Cosmic_rate_final.png

Average rates of cosmic ray data (in Hz) recorded by the CMS tracker during the years 2016, 2017 and 2018, calculated including all commissioning and interfill runs. Events are required to have at least one track with a minimum of 7 hits, and at least two hits measured in either pixel detector or stereo strip modules (2D measurement). For the event rate (first bin), tracks are reconstructed by at least one out of three reconstruction algorithms ( CMS Collaboration, Alignment of the CMS Silicon Tracker during Commissioning with Cosmic Rays.(2010) J. Inst. 5 T03009). For the track rate calculation instead (all other bins), tracks reconstructed by one of the three reconstruction algorithms are considered as the input for the tracker alignment procedure. Track rates per partition are obtained by requiring tracks to have at least one valid hit in each partition. The statistical uncertainty on the measured rates is negligible and hence not shown in the plot.
vsLumi_Xpos_BPIXx-.png Observed movements in x direction of the two barrel pixel half cylinders as a function of processed luminosity from the prompt calibration loop. Error bars represent the statistical uncertainties of the measurement. The vertical black solid lines indicate the first processed run for 2016, 2017 and 2018 data-taking period, respectively. Vertical dashed lines illustrate updates of the pixel calibration. The two horizontal lines show the threshold for a new alignment to be triggered. The grey bands at the beginning of each year indicate runs, where the automated updates of the alignment were not active. Missing points, especially at the beginning of 2018, correspond to periods where the automated alignment was not fully functional.
hist_Xpos_BPIXx-.pnghist_Xpos_BPIXx+.png Observed movements in x direction of the two barrel pixel half cylinders from the prompt calibration loop. The two vertical lines show the threshold for a new alignment to be triggered. The filled entries~(Updates inactive) correspond to runs in early 2016, 2017 and 2018, where the automated updates of the alignment were not active. For both half cylinders the fraction of runs, where a new alignment was triggered by the movement in x direction, is displayed. In this fraction the filled entries are not taken into account.
DmedianR_BPIX_plain.pngDmedianR_FPIX_plain.png Distribution of median residuals in the local-x(x') coordinate for different components of the tracker system. The derived MC object (MC) is compared to three representative Data IOVs (18 July, 18 August, 05 October) to assess its validity as final geometry. The study corresponds to the MC scenario derived for 2017. The larger width of the MC distribution in the forward pixel is driven by the systematic misalignment of 30 $\mu$m in the global z-direction that was applied to the forward pixel to achieve a better description of the data (see $ \left<d_z\right> $ vs. $ \eta $ plot).
DmedianR_TIB_plain.pngDmedianR_TEC_plain.png Distribution of median residuals in the local-x(x') coordinate for different components of the tracker system. The derived MC object (MC) is compared to three representative Data IOVs (18 July, 18 August, 05 October) to assess its validity as final geometry. The study corresponds to the MC scenario derived for 2017.
PV_Validation_2017.png Distribution of mean impact parameter in the transverse plane $d_{xy}$ and in the longitudinal plane $d_{z}$ as a function of two angular variables $\phi$ and $\eta$. The derived MC object (MC) is compared to three representative Data IOVs (18 July, 18 August, 05 October) to assess its validity as final geometry. The study corresponds to the MC scenario derived for 2017. In the attempt of mimicking the observed behaviour in data in the $ \left<d_z\right> $ vs. $ \eta $ plot, a systematic misalignment of 30 $ \mu $m in the global z-direction was applied to the forward pixel endcaps.
hist_Delta_dxy.pnghist_Delta_dz.png Difference in impact parameter in the longitudinal and transverse plane between two halves of cosmic tracks. The derived MC object (MC) is compared to three representative Data IOVs (18 July, 18 August, 05 October) to assess its validity as final geometry. The study corresponds to the MC scenario derived for 2017.
-- PaulAsmuss - 2020-07-13
Attachments Attachments
Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf Cosmic_rate_final.pdf r1 manage 14.4 K 2020-07-13 - 14:40 PaulAsmuss  
PNGpng Cosmic_rate_final.png r1 manage 77.4 K 2020-07-13 - 15:53 PaulAsmuss  
PDFpdf DmedianR_BPIX_plain.pdf r1 manage 22.6 K 2020-07-16 - 11:11 PaulAsmuss  
PNGpng DmedianR_BPIX_plain.png r1 manage 101.7 K 2020-07-16 - 11:11 PaulAsmuss  
PDFpdf DmedianR_FPIX_plain.pdf r1 manage 21.7 K 2020-07-16 - 11:11 PaulAsmuss  
PNGpng DmedianR_FPIX_plain.png r1 manage 95.7 K 2020-07-16 - 11:11 PaulAsmuss  
PDFpdf DmedianR_TEC_plain.pdf r1 manage 22.9 K 2020-07-16 - 11:19 PaulAsmuss  
PNGpng DmedianR_TEC_plain.png r1 manage 96.2 K 2020-07-16 - 11:19 PaulAsmuss  
PDFpdf DmedianR_TIB_plain.pdf r1 manage 57.5 K 2020-07-16 - 11:11 PaulAsmuss  
PNGpng DmedianR_TIB_plain.png r1 manage 100.4 K 2020-07-16 - 11:11 PaulAsmuss  
PDFpdf PV_Validation_2017.pdf r1 manage 124.2 K 2020-07-13 - 14:41 PaulAsmuss  
PNGpng PV_Validation_2017.png r1 manage 153.4 K 2020-07-13 - 15:53 PaulAsmuss  
PNGpng RMS_dxy_eta_vs_lumi.png r1 manage 124.0 K 2020-07-13 - 14:39 PaulAsmuss  
PNGpng RMS_dxy_phi_vs_lumi.png r1 manage 109.2 K 2020-07-13 - 14:39 PaulAsmuss  
PNGpng RMS_dz_eta_vs_lumi.png r1 manage 143.3 K 2020-07-13 - 14:39 PaulAsmuss  
PNGpng RMS_dz_phi_vs_lumi.png r1 manage 127.0 K 2020-07-13 - 14:39 PaulAsmuss  
PDFpdf baryCentre_x_BPIX_2016+2017+2018_IntegratedLumi.pdf r1 manage 69.1 K 2020-07-13 - 14:40 PaulAsmuss  
PNGpng baryCentre_x_BPIX_2016+2017+2018_IntegratedLumi.png r1 manage 54.0 K 2020-07-13 - 15:53 PaulAsmuss  
PDFpdf baryCentre_y_BPIX_2016+2017+2018_IntegratedLumi.pdf r1 manage 71.3 K 2020-07-13 - 14:40 PaulAsmuss  
PNGpng baryCentre_y_BPIX_2016+2017+2018_IntegratedLumi.png r1 manage 56.9 K 2020-07-13 - 15:53 PaulAsmuss  
PDFpdf hist_Delta_dxy.pdf r1 manage 22.0 K 2020-07-14 - 12:22 PaulAsmuss  
PNGpng hist_Delta_dxy.png r1 manage 116.4 K 2020-07-14 - 12:22 PaulAsmuss  
PDFpdf hist_Delta_dz.pdf r1 manage 20.9 K 2020-07-14 - 12:22 PaulAsmuss  
PNGpng hist_Delta_dz.png r1 manage 117.3 K 2020-07-14 - 12:22 PaulAsmuss  
PDFpdf hist_Xpos_BPIXx+.pdf r1 manage 14.8 K 2020-07-20 - 10:39 PaulAsmuss  
PNGpng hist_Xpos_BPIXx+.png r1 manage 47.5 K 2020-07-20 - 10:39 PaulAsmuss  
PDFpdf hist_Xpos_BPIXx-.pdf r1 manage 14.8 K 2020-07-20 - 10:39 PaulAsmuss  
PNGpng hist_Xpos_BPIXx-.png r1 manage 47.3 K 2020-07-20 - 10:39 PaulAsmuss  
PNGpng mean_dxy_phi_vs_lumi.png r1 manage 109.3 K 2020-07-13 - 14:39 PaulAsmuss  
PNGpng mean_dz_phi_vs_lumi.png r1 manage 102.0 K 2020-07-13 - 14:39 PaulAsmuss  
PDFpdf vsLumi_Xpos_BPIXx-.pdf r1 manage 281.4 K 2020-07-20 - 10:39 PaulAsmuss  
PNGpng vsLumi_Xpos_BPIXx-.png r1 manage 65.9 K 2020-07-20 - 10:39 PaulAsmuss  
Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2020-07-20 - PaulAsmuss
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback