Tracker Alignment Constants for Run II -- 2016

Description: Timeline of these tags is ordered from bottom to the top which means the tag on the top is always the latest one.

Complete:

Alignment and Surface Deformation Objects (Data)

Ultra-Legacy campaign for 2016

Candidate 1, based on the object from /afs/cern.ch/work/j/jschulz/public/merged_dbFiles/merged_mp3218.db and /afs/cern.ch/work/j/jschulz/public/merged_dbFiles/merged_mp3218.db

• Alignment: TrackerAlignment_2016_ultralegacy_v1
• APE: TrackerAlignmentExtendedErrors_2016_ultralegacy_v1
• AlCaDB talk: https://indico.cern.ch/event/848325/#3-ul-2016-sign-off-tracker-ali
• HN message: https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/4228.html

Candidate 2, based on the object from /afs/cern.ch/work/j/jschulz/public/merged_dbFiles/merged_mp3297.db and /afs/cern.ch/work/j/jschulz/public/merged_dbFiles/merged_mp3297.db

• Alignment: TrackerAlignment_2016_ultralegacy_v2
• APE: TrackerAlignmentExtendedErrors_2016_ultralegacy_v2
• Alignment talk: https://indico.cern.ch/event/841666/#b-345177-tracker-alignment
• HN message: https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/4228.html

Candidate 2 has been packaged into multi-IOV tags TrackerAlignment_v27_offline + TrackerAlignmentExtendedErrors_v14_offline_IOVs with the following history:

TrackerAlignment_v27_offline
0      - 271865: Content of TrackerAlignment_v26_offline in that run range
271866 - 290542: TrackerAlignment_2016_ultralegacy_v2
290543 - inf: : Content of TrackerAlignment_v26_offline in that run range


TrackerAlignmentExtendedErrors_v14_offline_IOVs
0      - 271865: Content of TrackerAlignmentExtendedErrors_v13_offline_IOVs in that run range
271866 - 290542: TrackerAlignmentExtendedErrors_2016_ultralegacy_v2
290543 - inf: : Content of TrackerAlignmentExtendedErrors_v13_offline_IOVs in that run range

TrackerSurfaceDeformations _v9_offline and TrackerAlignment _v19_offline

Tags at TrackerAlignment_v19_offline and TrackerSurfaceDeformations_v9_offline

• dedicated offline multi-IOV tags for surfaces and for alignment
• respective copies of TrackerSurfaceDeformations _v7_offline and TrackerAlignment _v17_offline up to run2016A
• then including legacy campaign (EOY16)

TrackerAlignment _EOY16_sm1959 and TrackerSurfaceDeformations _EOY16_mp2269

Final object

• Presentation at AlCaDB meeting and announcement on AlCa/DB HN, presentation of APE at AlCa/DB meeting January 9, 2017
  • TrackerAlignmentRcd
  • SurfaceDeformationsRcd
  • TrackerAlignmentExtendedErrorsRcd (35 IOVs: the first IOV correspond to two IOVs in the corresponding alignment record)
• More detailed validations at the TkAl meeting, Dec 7, 2016.

Dedicated TWiki to the EOY campaign (for technical details only!) More information can be found here. For APEs, see dedicated section below.

Starting conditions (v2) after new IOVs definition

• GTs to use: 80X_dataRun2_Prompt_v15_forTkAlNovCamp_singleIOV_v1 (single-IOV), 80X_dataRun2_Prompt_v15_forTkAlNovCamp_multiIOV_v1 (multi-IOV)

For single-IOV : 80X_dataRun2_Prompt_v15_forTkAlNovCamp_singleIOV_v1 is created with following conditions changed

• TrackerAlignmentRcd extracted from TrackerAlignment_MP_Run2016B_v2 which is the alignment from May camp
• TrackerSurfaceDeformationRcd is corresponding surface deformation to above alignment ( TrackerSurfaceDeformations_2015-EOY_v1_RunD)
• SiPixelTemplateDBObjectRcd includes the latest pixel templates for this year ( SiPixelTemplateDBObject_38T_v10_offline)

For multi-IOV : 80X_dataRun2_Prompt_v15_forTkAlNovCamp_multiIOV_v1 is created with following conditions changed

• TrackerAlignmentRcd contains the multi-IOVs of 2016 Sept ReReco + all subsequent PCL updates with new IOV definition ( TrackerAlignment_ReReco2016BtoG_plusPCLafter279479_v2)
• TrackerSurfaceDeformationRcd is corresponding surface deformation to above alignments ( TrackerAlignmentSurfaceDeformation_ReReco2016BtoG_v1)
• SiPixelTemplateDBObjectRcd includes the latest pixel templates for this year ( SiPixelTemplateDBObject_38T_v10_offline)

More details at:

• (EOY16) IOV definition on HN
• Announcement on TkAl HN

Zmumu studies

• TrackerAlignment_misalignment_singleIOV_SG_EOY16
• TrackerAlignment_misalignment_multiIOV_SG_EOY16

These tags are misalignment of the aforementionned geometries with:

Starting conditions (v1)

• GTs to use: 80X_dataRun2_Prompt_v15_forMPTkAlNovCamp_v1 (single-IOV), 80X_dataRun2_Prompt_v15_forHipPyTkAlNovCamp_v1 (multi-IOV)

For single-IOV : 80X_dataRun2_Prompt_v15_forMPTkAlNovCamp_v1 is created with following conditions changed

• TrackerAlignmentRcd extracted from TrackerAlignment_MP_Run2016B_v2 which is the alignment from May camp
• TrackerSurfaceDeformationRcd is corresponding surface deformation to above alignment ( TrackerSurfaceDeformations_2015-EOY_v1_RunD)
• SiPixelTemplateDBObjectRcd includes the latest pixel templates for this year ( SiPixelTemplateDBObject_38T_v8_candidate)

For multi-IOV : 80X_dataRun2_Prompt_v15_forHipPyTkAlNovCamp_v1 is created with following conditions changed

• TrackerAlignmentRcd contains the first 20 IOVs of 2016 Sept ReReco + all subsequent PCL updates ( TrackerAlignment_ReReco2016BtoG_plusPCLafter279479)
• TrackerSurfaceDeformationRcd is corresponding surface deformation to above alignments ( TrackerAlignmentSurfaceDeformation_ReReco2016BtoG_v1)
• SiPixelTemplateDBObjectRcd includes the latest pixel templates for this year ( SiPixelTemplateDBObject_38T_v8_candidate)

More details at:

• Starting geometry annoncement on HN

TrackerSurfaceDeformations _v8_offline and TrackerAlignment _v18_offline

Tags at _v18_offline and CondDB (surface deformations)

• dedicated offline multi-IOV tags for surfaces and for alignment
• respective copies of TrackerSurfaceDeformations _v7_offline and TrackerAlignment _v17_offline up to run2016B
• then including rereco campaign (TrackerAlignmentSurfaceDeformation _ReReco2016BtoG)

Note: this corresponds to (corrected version of) the September 2016 ReReco campaign (EOY16 Legacy alignment will be performed in November 2016)

Announcement on 10 September and on 14 October

TrackerAlignment _ReReco2016BtoG and TrackerAlignmentSurfaceDeformation _ReReco2016BtoG_v1

Note: mind the v1 for surface deformations

Tags at CondDB (alignment) and at CondDB (surfaces)

• ReReco campaign before HIP mitigation
• pixel only at ML
• multi-IOV, ladder as HLS
• includes new fit of surface shape deformations
• starting from TrackerAlignment _Run2016B
• internal reference mp2226/jobData/jobm3
  • original object (wrong surface payload!) was mp2226/jobData/jobm2
  • mp2226/jobData/jobm3 has the surfaces fixed

Note: the wrong surface deformations were in express and HLT conditions for some time (see announcement on 14 October)

Full report on indico page of the TkAl meeting of 7 September (note: documentation not up-to-date!! still correspond to the wrong surface deformations!!)

Annoucement on the hypernews

These conditions have been input in express and HLT as well (see main page the TWiki).

TrackerAlignment _v17_offline

Tag at CondDB

• This is a copy of TrackerAlignment _v16_offline up to run 275417
• also including later PCL updates

TrackerAlignment _v16_offline

Multi-IOV tag containing:

• Pseudo-PCL alignment run with 13TeV data at 0T for run eras Run2015B, Run2015C, and Run2015D
• CRUZET 2016 (barrel HLS alignment)
• Run2016A (Pseudo-PCL)
• Run2016B (MayCamp2016 + Pseudo-PCL)

Test tag TrackerAlignment_v14_0T_offline at PREP2 DB.

More details at:

• Presentation at AlCa/DB meeting for Run2015BCD
• PCLLikeAlignmentResults2016 for Run2016AB

TrackerAlignment _Run2016B_PseudoPCL_276363

Tags at CondDB

This new alignment has been derived by the online PCL workflow that aligns pixel high-level structures, using the data of run 276363 which corrects for small but significant movements induced by the magnet cycle.

TrackerAlignment _Run2016B_PseudoPCL_275376

Tags at CondDB

This new alignment has been derived by the online PCL workflow that aligns pixel high-level structures, using the data of run 275375. More details are discussed here.

TrackerAlignment _Run2016B

Tags at CondDB:

• TrackerAlignment_MP_Run2016B_v2
• TrackerAlignment_HP_Run2016B_v2

Tracker alignment [May Camp] started from GT 80X_dataRun2_Prompt_v8 and overwrote the following records :

• TrackerAlignmentRcd: "TrackerAlignment_Run2016A_PseudoPCL_v1"
• SiPixelTemplateDBObjectRcd: "SiPixelTemplateDBObject_38T_2016_v1_hltvalidation"

with new created self-GT 80X_dataRun2_Prompt_Candidate_2016_05_12_11_59_51.

Note : The "SiPixelTemplateDBObject_38T_2016_v1_hltvalidation" tag was actually mistaken to be uploaded to SiPixelTemplateDBObject0TRcd instead of SiPixelTemplateDBObjectRcd in this self-GT candidate and the alignments were uploaded for both aligners under tags TrackerAlignment_MP_Run2016B and TrackerAlignment_HP_Run2016B.

More details at:

• Tracker alignment meeting May 18, 2016
• AlCaDB meeting May 23, 2016

TrackerAlignment _Run2016B_PseudoPCL_v1

Tag at CondDB

Tracker alignment derived from the Pseudo-PCL workflow on run 272775 and conditions in GT 80X_dataRun2_Express_v6.

TrackerAlignment _Run2016A_PseudoPCL_v1

Tag at CondDB

Tracker alignment derived from the Pseudo-PCL workflow on run 272011 and conditions in GT 80X_dataRun2_Express_v6 (CRUZET alignment).

More details at:

• tif HN announcement
• PCLLikeAlignmentResults2016 TWiki
• validation shown at TkAl meeting 2016-05-04

TrackerAlignment _HP_CRUZET2016

Tag at CondDB

Tracker alignment constants starting from IOV 260335 of 2015-EOY_v1_RunD with new created self-GT 80X_dataRun2_Prompt_Candidate_2016_04_18_10_23_57. This alignment was selected as CRUZET2016 alignment.

Use with TrackerSurfaceDeformations_2015-EOY_v1_RunD

More details at:

• Tracker alignment meeting April 20, 2016
• Announcement on AlCa/DB HN April 21, 2016

TrackerAlignment _MP_CRUZET2016

Tag at CondDB

Use with TrackerSurfaceDeformations_2015-EOY_v1_RunD

Tracker alignment constants starting from IOV 260335 of 2015-EOY_v1_RunD with new created self-GT 80X_dataRun2_Prompt_Candidate_2016_04_18_10_23_57.

More details at:

• Tracker alignment meeting April 20, 2016
• Announcement on AlCa/DB HN April 21, 2016

APE Objects (Data)

TrackerAlignmentExtendedErrors _EOY16_sm1959 and TrackerAlignmentExtendedErrors _EOY16_SingleIOV_sm1959

• presentation of APE at AlCa/DB meeting January 9, 2017
  • Multi-IOV: TrackerAlignmentExtendedErrors_EOY16_sm1959 (35 IOVs: the first IOV correspond to two IOVs in the corresponding alignment record), used in EOY16 reprocessing
  • Single-IOV: TrackerAlignmentExtendedErrors_EOY16_SingleIOV_sm1959 (Full dataset is used as a single IOV, time dependent effects are averaged out)

TrackerAlignmentExtendedErrors _ReReco2016BtoG

Tag at CondDB

• based on TrackerAlignment_ReReco2016BtoG

TrackerAlignmentExtendedErrors _Run2016B_*

Tags at CondDB:

• TrackerAlignmentExtendedErrors_MP_Run2016B by MP
• TrackerAlignmentExtendedErrors_HP_Run2016B by HP

APEs for Run2016B correspond to each validation. Presented at TkAl meeting, 2016-05-24.

TrackerAlignmentExtendedErrors _Run2016B

Update of the following tags:

• Prompt/Express: TrackerAlignmentExtendedErr_2009_v2_express_IOVs from run 272788
• HLT: TrackerAlignmentExtendedErr_2009_v2_hlt_IOVs from run 272788

detector	APE(x,y,z)
BPIX, TIB, TOB	10μm
FPIX, TID, TEC	20μm

Note: This update reduces the previously employed conservative APEs of 100μm in the pixel detector, which were put in place to take into account the remaining uncertainties of the CRUZET-data derived pixel start-up alignment (see below). This update is based on the conclusions from recent validation with the Run2015A collision data and CRAFT as well as the very latest online DQM results, which clearly indicate that the APE are overestimated and that smaller APE would describe better the data.

TrackerAlignmentExtendedErrors _CRUZET2016

Tag at CondDB.

APE for 2016 collision start-up. Conservative estimate from 2015 operation experience of 20μm in the barrel and 40μm in the endcap detectors, plus inflated APE (100μm) in the pixel to account for the foreseen magnet ramp:

detector	APE(x,y,z)
BPIX, FPIX	100μm
TIB, TOB	20μm
TID, TEC	40μm

Alignment and Surface Deformation Objects (MC)

TrackerAlignment _Asymptotic_Run2016_v1_mc

Tag at TrackerAlignment_Asymptotic_Run2016_v1_mc at CondDB.

Tracker alignment constants simulating the asymptotic conditions at 2016 data taking after ~3/fb. Derived starting from the start-up scenario TrackerAlignment_Startup_Run2016_v1_mc, re-aligned at high-level with cosmics and collision data tracks at 3.8T. Depends on conditions in GT 76X_mcRun2_design_v14. Internal reference /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/mp1982.

This alignment contains no scenario of the surface deformation.

More details at:

• Tracker alignment meeting April 29, 2016 (validation)
• AlCa/DB meeting, March 7, 2016 (study of z-movements)

TrackerAlignment _Asymptotic_Run2016_v0_mc

NOTE Has been derived relative to design local-reco conditions, therefore not usable with realistic conditions! Fix available in #TrackerAlignment_Startup_Run2016_v1_mc

Tag at TrackerAlignment_Asymptotic_Run2016_v0_mc at CondDB.

Tracker alignment constants simulating the asymptotic conditions at 2016 data taking after ~3/fb. Derived starting from the start-up scenario TrackerAlignment_Startup_Run2016_v0_mc, re-aligned at high-level with cosmics and collision data tracks at 3.8T. Depends on conditions in GT 76X_mcRun2_design_v14. Internal reference /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/mp1961.

The alignment scenario can be used together with the existing surface deformation scenario . TrackerSurfaceDeformations _2011Realistic_v2_mc

More details at:

• Tracker alignment meeting March 9, 2016
• AlCa/DB meeting, March 7, 2016
• AlCa/DB meeting, February 29, 2016
• Tracker alignment meeting February 24, 2016

TrackerAlignment _Startup_Run2016_v1_mc

Tag at TrackerAlignment_Startup_Run2016_v1_mc CondDB

Tracker alignment constants simulating the post-CRUZET 2016 start-up conditions. Derived starting from a pre-CRUZET mis-alignment scenario, re-aligned at high-level with 0T cosmics tracks (CRUZET). Depends on conditions in GT 76X_mcRun2cosmics_startup_peak_v0. Internal reference /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/mp1971.

The alignment scenario can be used together with the existing surface deformation scenario .

This is a fix of #TrackerAlignment_Startup_Run2016_v0_mc

More details at:

• AlCa/DB meeting, March 14, 2016

TrackerAlignment _Startup_Run2016_v0_mc

NOTE Has been derived relative to design local-reco conditions, therefore not usable with realistic conditions! Fix available in #TrackerAlignment_Startup_Run2016_v1_mc

Tag at TrackerAlignment_Startup_Run2016_v0_mc CondDB

Tracker alignment constants simulating the post-CRUZET 2016 start-up conditions. Derived starting from a pre-CRUZET mis-alignment scenario, re-aligned at high-level with 0T cosmics tracks (CRUZET). Depends on conditions in GT 76X_mcRun2_design_v14. Internal reference /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/mp1957.

The alignment scenario can be used together with the existing surface deformation scenario .

More details at:

• Tracker alignment meeting March 9, 2016
• AlCa/DB meeting, March 7, 2016
• AlCa/DB meeting, February 29, 2016
• Tracker alignment meeting February 24, 2016

-- ChayanitAsawatangtrakuldee - 2016-08-23