TWiki> CMSPublic Web>SWGuide>SWGuideCalAli>SWGuideTrackAlignment>SWGuideAlignmentConstants (revision 241)EditAttachPDF

CMS Tracker Alignment DB Object Tags for Run-2

Description: History and description of alignment/surface deformation/APE tags in Run-2. Run-1 alignment constants are documented here.

Contacts

Current multi-IOV data tags

Starting from 80X_dataRun2_Express_v9 and 80X_dataRun2_Prompt_v9, it has been introduced new Tracker Alignment tag (copy of the existing one) for the purpose of switching on the SiPixelAli PCL for both Express and Prompt.

Summary table

stream TrackerAlignmentRcdSorted ascending TrackerSurfaceDeformationRcd TrackerAlignmentErrorExtendedRcd
HLT TrackerAlignment_PCL_byRun_v0_hl TrackerSurafceDeformations_v1_hlt TrackerAlignmentExtendedErr_2009_v2_hlt_IOVs
Express TrackerAlignment_PCL_byRun_v2_express TrackerSurafceDeformations_v1_express TrackerAlignmentExtendedErr_2009_v2_express_IOVs
Prompt TrackerAlignment_PCL_byRun_v2_express TrackerSurafceDeformations_v1_express TrackerAlignmentExtendedErr_2009_v2_express_IOVs
Offline TrackerAlignment_v28_offline TrackerSurfaceDeformations_v13_offline TrackerAlignmentExtendedErrors_v15_offline_IOVs

TrackerAlignment_PCL_byRun_v0_hlt

Detailed information at CondDB.

since run object comment
246978 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
248618 TrackerAlignment_v2_hltvalidation Wrong upload to production, no data taken, reverted back to TrackerAlignment_v1_hltvalidation till validation
248642 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
251100 TrackerAlignment_v2_hltvalidation Module-level alignment of pixel detector only with 0T data of Run2015A AlCa/DB HN announcement
251607 TrackerAlignment_Run2015B_PseudoPCL_v2 pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256715 TrackerAlignment_for_Run2015D_v0 inconsistent conditions derived from Run2015C data, uploaded by mistake (affected data corrected in prompt reconstruction)
256746 TrackerAlignment_for_Run2015D_v1 conditions derived from Run2015B data
256766 TrackerAlignment_for_Run2015D_v0 inconsistent conditions derived from Run2015C data but centrally validated, therefore till further validation used in HLT. Express used the TrackerAlignment_for_Run2015D_v1 conditions. Difference to express
270856 TrackerAlignment_CRUZET2016 CRUZET alignment for 2016 the alignment constants starting from IOV 260335 of 2015-EOY_v1_RunD
272497 TrackerAlignment_Run2016A_PseudoPCL_v1 Tracker alignment derived from the Pseudo-PCL workflow on run 272011 and conditions in GT 80X_dataRun2_Express_v6 (CRUZET alignment)
276251 no corresponding Tag created updated module level tracker alignment and APE from 2016B AlCa/DB HN announcement
276517 TrackerAlignment_Run2016B_PseudoPCL_276363 pseudo-PCL alignment at 3.8T after magnet cycle on 02.07.2016 AlCa/DB HN announcement
281466 TrackerAlignment_ReReco2016BtoG Tracker alignment updated from September ReReco campaign Alca/DB HN announcement
285456   Update tracker alignment with conditions derived after last magnet ramp after 2016 end of pp-data taking (run 285090) for p-Pb run
290550 TrackerAlignment_PreCRUZET2017_v1 Conditions changed consistently to phase-I pixel detector and last IOV of EOY16 alignment for strips AlCa/DB HN announcement
292615 TrackerAlignment_CRUZET17_v1 First HL alignment with CRUZET17 data (still w/o BPX) Alca/DB HN announcement
294604 TrackerAlignment_CRAFT17_v0 New tracker alignment derived from CRUZET and CRAFT 2017 data AlCa/DB HN announcement
295502 TrackerAlignment_StartUp17_v0 Updates the pixel module-level alignment (positions and rotations), leading to an improved local resolution and using the collision data of the runs 295209+295210 as well as CRAFT (private rereco) AlCa/DB HN announcement
296819 TrackerAlignment_StartUp17_v1 Updates the pixel module-level alignment (positions and rotations), leading to an improved local resolution in BPX layer1 AlCa/DB HN announcement
297618 TrackerAlignment_StartUp17_v5 Updates the pixel module-level alignment (positions, rotations, surfaces), consistent with templates v3 for new bias voltage in layer 1 AlCa/DB HN announcement
298902 TrackerAlignment_StartUp17_v6 synchronisation with express/prompt
299924 TrackerAlignment_StartUp17_v9 syncrhonisation with express/prompt HN announcement
300703 TrackerAlignment_StartUp17_v10 The new conditions are necessary for full consistency with updates in the pixel local-reco conditions and BPX layer 2 timing settings, leading to improved performance AlCa/DB HN announcement
302581 TrackerAlignment_StartUp17_v11 Consistent with new templates and new HV HN announcement
303856   To be consistent with the PCL-produced payload post-TS2 on express/prompt HN announcement.
304653 TrackerAlignment_forPrompt2017_v1 Update of Tracker alignment and APEs corresponding to V6 pixel gain and other local reco conditions HN announcement.
306532 TrackerAlignment_lastIOV_v2ReReco2017 Full track validation of Tracker alignment and surface HN announcement.
314163 TrackerAlignment_StartUp2018_v2 New tracker alignment and APE (start-up 2018) HN announcement.
316006 TrackerAlignment_PCL_byRun_v1_express_315648 PCL alignment HN announcement.
317393 TrackerAlignment_FirstCollisions2018_v3 New tracker alignment and APE from first collisions 2018 HN announcement.
320399 TrackerAlignment_PreMD2_v1 New tracker alignment during MD2 (machine developing) HN announcement.
320924 TrackerAlignment_PostMD2_v2 New tracker alignment the post-annealing payload HN announcement.
321048 TrackerAlignment_PCL_byRun_v2_express_off Manually upload TkAl from PCL Run 321007 also significantly improved for HLT HN announcement.
321496 TrackerAlignment_PostMD2_v3 New tracker alignment the post-annealing payload to improve further on top of TrackerAlignment_PostMD2_v2 HN announcement.
321496 TrackerAlignment_PostMD2_v3 New tracker alignment the post-annealing payload to improve further on top of TrackerAlignment_PostMD2_v2 HN announcement.
323230 TrackerAlignment_PreMD3_450V_v1 New tracker alignment for PreMD3 with 450V condition HN announcement.
326083 TrackerAlignment_PreMD4_v1 New tracker alignment PreMD4 for HI data taking HN announcement.
326457 TrackerAlignment_PCL_byRun_v0_hlt Manually upload TkAl from PCL Run 326381 for HI data taking HN announcement.
326978 TrackerAlignment_HI2018_v1 New tracker alignment for HI data taking HN announcement.

TrackerAlignment_PCL_byRun_v2_express

Detailed information at CondDB.

Note This is a copied and updated version of tag TrackerAlignment_PCL_byRun_v0_express.

since run object comment
275635 TrackerAlignment_Run2016B_PseudoPCL_275376 Tracker alignment updated with the latest pixel high-level alignment AlCa/DB HN announcement
276319   Tracker alignment updated with the latest pixel high-level alignment which corrects for small but significant movements induced by the magnet cycle AlCa/DB HN announcement
281466 TrackerAlignment_ReReco2016BtoG Tracker alignment updated from September ReReco campaign Alca/DB HN announcement
290550 TrackerAlignment_PreCRUZET2017_v1 Conditions changed consistently to phase-I pixel detector and last IOV of EOY16 alignment for strips AlCa/DB HN announcement
292200 TrackerAlignment_CRUZET17_v1 First HL strips + FPX alignment with CRUZET17 data (no BPX yet, stays at IDEAL). Cures in particular 3mm mis-alignment of FPX -z cylinder. AlCa/DB HN announcement
294604 TrackerAlignment_CRAFT17_v0 New tracker alignment derived from CRUZET and CRAFT 2017 data AlCa/DB HN announcement
295380 TrackerAlignment_StartUp17_v0 Updates the pixel module-level alignment (positions and rotations), leading to an improved local resolution and using the collision data of the runs 295209+295210 as well as CRAFT (private rereco) AlCa/DB HN announcement
295702 TrackerAlignment_StartUp17_v1 Updates the pixel module-level alignment on Run 295463 (positions and rotations), leading to an improved local resolution in BPX layer1 AlCa/DB HN announcement
297104 TrackerAlignment_StartUp17_v2 Updates the pixel module-level alignment on Run 296786 (positions and rotations), leading to an improved local resolution in BPX layer1 AlCa/DB HN announcement
297417 TrackerAlignment_StartUp17_v5 Updates the pixel module-level alignment on Run 297292 (positions, rotations, surfaces), consistent with templates v3 for new bias voltage in layer 1 AlCa/DB HN announcement
298757 TrackerAlignment_StartUp17_v6 Pixel ML alignment + surfaces from 2017 collision data, runs 298653, 298671, 298678, including cosmics runs 298647/48/51/57/58/61/68. AlCa/DB HN announcement
298809 TrackerAlignment_from06Jul2017ReReco_v0 Pixel ML alignment on 06Jul2017ReReco of 297664+297671 (updated VCal calibration, PH, gain calibration) AlCa/DB HN announcement
299228 TrackerAlignment_StartUp17_v7 Pixel ML alignment from 2017 collision data 298996 (post TS1 with new Vcal calibration). Derived against GT 92X_dataRun2_express_v4. AlCa/DB HN announcement
299685 TrackerAlignment_StartUp17_v9 Pixel ML alignment based on Run 299592-97+299614-617. AlCa/DB HN announcement
300662 TrackerAlignment_StartUp17_v10 The new conditions are necessary for full consistency with updates in the pixel local-reco conditions and BPX layer 2 timing settings, leading to improved performance AlCa/DB HN announcement
302539 TrackerAlignment_StartUp17_v11 Consistent with new templates and new HV HN announcement
303796   started automatic PCL-produced payload post-TS2 writing to production tags HN announcement
304653 TrackerAlignment_forPrompt2017_v1 Update of Tracker alignment and APEs corresponding to V6 pixel gain and other local reco conditions HN announcement.
306532 TrackerAlignment_lastIOV_v2ReReco2017 Full track validation of Tracker alignment and surface HN announcement.
314163 TrackerAlignment_StartUp2018_v2 New tracker alignment and APE (start-up 2018) HN announcement.
316006 TrackerAlignment_PCL_byRun_v1_express_315648 PCL alignment HN announcement.
317393 TrackerAlignment_PCL_byRun_v1_express_315648 New tracker alignment and APE from first collisions 2018 HN announcement.
317393 TrackerAlignment_FirstCollisions2018_v3 New tracker alignment and APE from first collisions 2018 HN announcement.
320399 TrackerAlignment_PreMD2_v1 New tracker alignment during MD2 (machine developing) HN announcement.
320812 TrackerAlignment_PCL_byRun_v2_express_off Manually upload TkAl from PCL Run 320757 before green light of TrackerAlignment_PostMD2_v2 object arrived HN announcement.
320924,320997 TrackerAlignment_PostMD2_v2 New tracker alignment the post-annealing payload HN announcement. (uploaded twice due to some mistake by AlCa)
321013 TrackerAlignment_PCL_byRun_v2_express_off Manually upload TkAl from PCL Run 321007 due to mistake by AlCa forgotten to switch on PCL HN announcement.
321496 TrackerAlignment_PostMD2_v3 New tracker alignment the post-annealing payload to improve further on top of TrackerAlignment_PostMD2_v2 HN announcement.
323230 TrackerAlignment_PreMD3_450V_v1 New tracker alignment for PreMD3 with 450V condition HN announcement.
323462   Manually upload TkAl from PCL Run 323419 due to rotations are larger than the tolerances for automatic deployment. HN announcement.
323643 TrackerAlignment_PostMD3_v1 New tracker alignment for PostMD3 consistent with v11 pixel templates HN announcement.
326083 TrackerAlignment_PreMD4_v1 New tracker alignment PreMD4 for HI data taking HN announcement.
326457 TrackerAlignment_PCL_byRun_v2_express Manually upload TkAl from PCL Run 326381 for HI data taking HN announcement.
326978 TrackerAlignment_HI2018_v1 New tracker alignment for HI data taking HN announcement.

Note: automatic uploading mode is now activated and can be monitored from here and here. The table above only presented IOVs from manual uploads (automatic PCL uploads are skipped).

TrackerAlignment_v28_offline

TrackerSurafceDeformations_v1_hlt

Detailed information at CondDB.

since run object comment
184572   Run-I conditions
246993 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
270856 TrackerSurfaceDeformations_2015-EOY_v1_RunD CRUZET2016 AlCa/DB HN announcement
281466 TrackerAlignmentSurfaceDeformation_ReReco2016BtoG September ReReco2016 Annoucement
284121 TrackerAlignmentSurfaceDeformation_ReReco2016BtoG_v1 Corrected payload of September campaign (update after pp-runs but before pA-runs) HN announcement
290550 TrackerSurfaceDeformations_PreCRUZET2017_v1 Conditions changed consistently to phase-I pixel detector and last IOV of EOY16 alignment for strips AlCa/DB HN announcement
297618 TrackerAlignment_StartUp17_v5 Updates the pixel module-level alignment (positions, rotations, surfaces), consistent with templates v3 for new bias voltage in layer 1 AlCa/DB HN announcement
298901 TrackerAlignment_StartUp17_v6 synchronisation with express/prompt
299924 TrackerAlignment_StartUp17_v9 synchronisation with express/prompt HN announcement

TrackerSurafceDeformations_v1_express

Detailed information at CondDB.

since run object comment
184572   Run-I conditions
237545    
246993 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
270856 TrackerSurfaceDeformations_2015-EOY_v1_RunD CRUZET2016 AlCa/DB HN announcement
281466 TrackerAlignmentSurfaceDeformation_ReReco2016BtoG September ReReco2016 Annoucement -> BAD PAYLOAD
283024 TrackerAlignmentSurfaceDeformation_ReReco2016BtoG_v1 Corrected payload of September campaign HN announcement
290550 TrackerSurfaceDeformations_PreCRUZET2017_v1 Conditions changed consistently to phase-I pixel detector and last IOV of EOY16 alignment for strips AlCa/DB HN announcement
297417 TrackerAlignment_StartUp17_v5 Updates the pixel module-level alignment (positions, rotations, surfaces), consistent with templates v3 for new bias voltage in layer 1 AlCa/DB HN announcement
298757 TrackerAlignment_StartUp17_v6 Pixel ML alignment + surfaces from 2017 collision data, runs 298653, 298671, 298678, including cosmics runs 298647/48/51/57/58/61/68. AlCa/DB HN announcement
299685 TrackerAlignment_StartUp17_v9 Pixel ML alignment based on Run 299592-97+299614-617. AlCa/DB HN announcement

TrackerSurafceDeformations_v1_prompt

Detailed information at CondDB.

Note we have currently (24.07.2017) different tags in prompt and express to allow faster reaction to changing conditions during the commissioning period. This is a simply copied version of tag TrackerSurafceDeformations_v1_express until Run 298757.

since run object comment
299443 TrackerAlignment_StartUp17_v9 Pixel ML alignment based on Run 299592-97+299614-617. AlCa/DB HN announcement

TrackerSurfaceDeformations_v13_offline

TrackerAlignmentExtendedErr_2009_v2_hlt_IOVs

Detailed information at CondDB.

(first runs missing)

since run object comment
246994 ape_DESRUN2_74_V4_barrel20-disks40 AlCa/DB HN announcement
253953 ape_DESRUN2_74_V4_barrel10-disks20 reduced APE for 3.8T operation AlCa/DB HN announcement
254588 ape_DESRUN2_74_V4_barrel20-disks40 enlarged APE for 0T operation. Kept also for last 3.8T runs of 2015C since pixel has moved due to magnet cycles during era. AlCa/DB HN announcement
256715 ape_DESRUN2_74_V4_barrel10-disks20 reduced APE for 3.8T operation AlCa/DB HN announcement
270856 TrackerAlignmentExtendedErrors_CRUZET2016 enlarged APE: 100mum for BPIX and FPIX, 20mum for TIB and TOB, 40mum for TID and TEC AlCa/DB HN announcement
272788 TrackerAlignmentExtendedErrors_Run2016B reduced APE "10/20" AlCa/DB HN announcement
276251 TrackerAlignmentExtendedErrors_MP_Run2016B APE of the May16 alignment, employed after ICHEP dataset closing HN announcement
281466 TrackerAlignmentExtendedErrors_ReReco2016BtoG rereco 2016 campaign Annoucement; APEs presented at AlCa/DB meeting, Jan 09, 2017, values reported slides 59ff (curve labelled "sm1959 (APE per IOV)")
289671 TrackerAlignmentExtendedErrors_CRUZET2016 enlarged APE for CRUZET17 data taking with only strips detector: 100mum for BPIX and FPIX, 20mum for TIB and TOB, 40mum for TID and TEC. Note that pixel is still the phase0 format. It will be updated to phase1 once interdependency tests are done with the first, strips-only CRUZET17 data. AlCa/DB HN announcement
290550 TrackerAlignmentExtendedErrors_BPIX500_FPIX500_TIB20_TOB20_TID40_TEC40 APE for CRUZET data taking 500 mum for BPIX and FPIX, 20 mum for TIB and TOB, 40mum for TID and TEC. Conditions changed consistently to phase-I pixel detector AlCa/DB HN announcement
294611 TrackerAlignmentExtendedErrors_BPIX100_FPIX100_TIB20_TOB20_TID40_TEC40 APE for CRAFT data taking 100 mum for BPIX and FPIX, 20 mum for TIB and TOB, 40mum for TID and TEC. AlCa/DB HN announcement
297618 TrackerAlignmentExtendedErrors_StartUp17_v2 APE (in mum) payload based on the last measuerement with 296786: L1x: 30, L1yz: 70, L2y40, rest in pixel: 5; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before) AlCa/DB HN announcement
298647 TrackerAlignmentExtendedErrors_StartUp17_v3 Moderately increased pixel APE to accomodate possible displacement by B-field ramp during TS1. APE (in mum): L1x: 30, L1yz: 70, L2y40, rest in BPX 20, FPX 40; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before). AlCa/DB HN announcement
298901 TrackerAlignmentExtendedErrors_StartUp17_v2 back to previous conditions
304653 TrackerAlignmentExtendedErrors_StartUp17_v5 Update of Tracker alignment and APEs corresponding to V6 pixel gain and other local reco conditions HN announcement.
310617 TrackerAlignmentExtendedErrors_BPIX500_FPIX500_TIB20_TOB20_TID40_TEC40 APEs for CRUZET2018 which is the same as the one for 2016 as presented in AlCa/DB meeting and AlCa/DB HN announcement
314163 TrackerAlignmentExtendedErrors_StartUp2018_v2 New tracker alignment and APE (start-up 2018) HN announcement.
317393 TrackerAlignmentExtendedErrors_FirstCollisions2018_v1 New tracker alignment and APE from first collisions 2018 HN announcement.

TrackerAlignmentExtendedErr_2009_v2_express_IOVs

Detailed information at CondDB.

(first runs missing)

since run object comment
236373    
246994 ape_DESRUN2_74_V4_barrel20-disks40 AlCa/DB HN announcement
253953 ape_DESRUN2_74_V4_barrel10-disks20 reduced APE for 3.8T operation AlCa/DB HN announcement
254588 ape_DESRUN2_74_V4_barrel20-disks40 enlarged APE for 0T operation. Kept also for last 3.8T runs of 2015C since pixel has moved due to magnet cycles during era. AlCa/DB HN announcement
256715 ape_DESRUN2_74_V4_barrel10-disks20 reduced APE for 3.8T operation AlCa/DB HN announcement
270856 TrackerAlignmentExtendedErrors_CRUZET2016 enlarged APE: 100mum for BPIX and FPIX, 20mum for TIB and TOB, 40mum for TID and TEC AlCa/DB HN announcement
272788 TrackerAlignmentExtendedErrors_Run2016B reduced APE "10/20" AlCa/DB HN announcement
276812 TrackerAlignmentExtendedErrors_MP_Run2016B APE of the May16 alignment, employed after ICHEP dataset closing HN announcement
281466 TrackerAlignmentExtendedErrors_ReReco2016BtoG rereco 2016 campaign Annoucement; APEs presented at AlCa/DB meeting, Jan 09, 2017, values reported slides 59ff (curve labelled "sm1959 (APE per IOV)")
289671 TrackerAlignmentExtendedErrors_CRUZET2016 enlarged APE for CRUZET17 data taking with only strips detector: 100mum for BPIX and FPIX, 20mum for TIB and TOB, 40mum for TID and TEC. Note that pixel is still the phase0 format. It will be updated to phase1 once interdependency tests are done with the first, strips-only CRUZET17 data. AlCa/DB HN announcement
290550 TrackerAlignmentExtendedErrors_BPIX500_FPIX500_TIB20_TOB20_TID40_TEC40 APE for CRUZET data taking 500 mum for BPIX and FPIX, 20 mum for TIB and TOB, 40mum for TID and TEC. Conditions changed consistently to phase-I pixel detector AlCa/DB HN announcement
294611 TrackerAlignmentExtendedErrors_BPIX100_FPIX100_TIB20_TOB20_TID40_TEC40 APE for CRAFT data taking 100 mum for BPIX and FPIX, 20 mum for TIB and TOB, 40mum for TID and TEC. AlCa/DB HN announcement
297104 TrackerAlignmentExtendedErrors_StartUp17_v1 APE payload based on the last measuerement with 296463, keeping 100mum in L1: L1 xyz: 100mum (as before); L2 y: 40mum; L2 xz; L3-L4 xyz FPX xyz: 10mum; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before) AlCa/DB HN announcement
297417 TrackerAlignmentExtendedErrors_StartUp17_v2 APE (in mum) payload based on the last measuerement with 296786: L1x: 30, L1yz: 70, L2y40, rest in pixel: 5; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before) AlCa/DB HN announcement
298450 TrackerAlignmentExtendedErrors_StartUp17_v3 Moderately increased pixel APE to accomodate possible displacement by B-field ramp during TS1. APE (in mum): L1x: 30, L1yz: 70, L2y40, rest in BPX 20, FPX 40; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before). AlCa/DB HN announcement
298759 TrackerAlignmentExtendedErrors_StartUp17_v2 APE (in mum) payload based on the last measuerement with 296786: L1x: 30, L1yz: 70, L2y40, rest in pixel: 5; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before) AlCa/DB HN announcement
304653 TrackerAlignmentExtendedErrors_StartUp17_v5 Update of Tracker alignment and APEs corresponding to V6 pixel gain and other local reco conditions HN announcement.
310617 TrackerAlignmentExtendedErrors_BPIX500_FPIX500_TIB20_TOB20_TID40_TEC40 APEs for CRUZET2018 which is the same as the one for 2016 as presented in AlCa/DB meeting and AlCa/DB HN announcement
314163 TrackerAlignmentExtendedErrors_StartUp2018_v2 New tracker alignment and APE (start-up 2018) HN announcement.
317393 TrackerAlignmentExtendedErrors_FirstCollisions2018_v1 New tracker alignment and APE from first collisions 2018 HN announcement.

TrackerAlignmentExtendedErr_2009_v2_prompt_IOVs

Detailed information at CondDB.

Note we have currently (24.07.2017) different tags in prompt and express to allow faster reaction to changing conditions during the commissioning period. This is a simply copied version of tag TrackerAlignmentExtendedErr_2009_v2_express_IOVs until Run 298759.

TrackerAlignmentExtendedErrors_v15_offline_IOVs

Pseudo-PCL Tags

Since run 272011, the PCL alignment is running in test mode at T0. Results are written to the following tags at the preparation DB:

Past tags

Past multi-IOV data tags

stream TrackerAlignmentRcd TrackerSurfaceDeformationRcd TrackerAlignmentErrorExtendedRcd
HLT TrackerAlignment_2009_v1_hlt TrackerSurafceDeformations_v1_hlt TrackerAlignmentExtendedErr_2009_v2_hlt_IOVs
Express TrackerAlignment_2009_v1_express TrackerSurafceDeformations_v1_express TrackerAlignmentExtendedErr_2009_v2_express_IOVs
Prompt1) TrackerAlignment_prompt TrackerSurafceDeformations_v1_express TrackerAlignmentExtendedErr_2009_v2_express_IOVs
Remarks:
  1. This was split from the express tag, see TrackerAlignment_prompt for details

Tags for data reprocessing

Ultra-Legacy (all years)

2017 Re-Reco

2016 Legacy

2016 ReReco campaign (after correction of surface deformations)

2016 pre-ICHEP

2015 End-of-Year (EOY) reprocessing

Reprocessing of 3.8T pp data of 2015. Objects detailed below in 2015-EOY_v1. They are appended to the following offline tags:

Pixel-large-structure fits on all 0T data for run eras Run2015B, Run2015C, and Run2015D:

2015 first data reprocessing

Reprocessing of CRAFT and Run2015A to Run2015D (reprocessing starts before end of era?) data. Discussed in the AlCa/DB meeting, 2015-09-28.

TrackerAlignment_v13_offline (listing only relevant IOVs)

era IOV alignment
CRAFT15 238341 TrackerAlignment_v1_hltvalidation
Run2015A 246866 TrackerAlignment_v2_hltvalidation
Run2015B 250933 TrackerAlignment_for_Run2015D_v1
Run2015C 253620 TrackerAlignment_Run2015C_offline_v0
Run2015D 255621 TrackerAlignment_Run2015D_PseudoPCL_v0

TrackerSurfaceDeformations_v6_offline (listing only relevant IOVs)

era IOV alignment
CRAFT15 - Run2015D 238341 TrackerAlignment_v1_hltvalidation

TrackerAlignmentExtendedErrors_v4_offline_IOVs (listing only relevant IOVs)

era IOV alignment
CRAFT15 + Run2015A 238341 ape_DESRUN2_74_V4_barrel20-disks40
Run2015B - Run2015D 250933 ape_DESRUN2_74_V4_barrel10-disks20

Payload Information

TrackerAlignment_PCL_byRun_v1_express

Diverts the alignment objects produced by the pixelAli at PCL to the this tag, which is not consumed by prompt; as agreed with tracker DPG for the early phases of 2017 running.

Detail information at AlCa/DB HN announcement

TrackerAlignment_PCL_byRun_v2_prompt

Detailed information at CondDB.

Note we have currently (24.07.2017) different tags in prompt and express to allow faster reaction to changing conditions during the commissioning period. This is a simply copied version of tag TrackerAlignment_PCL_byRun_v2_express until Run 299228.

since run object comment
298809 TrackerAlignment_from06Jul2017ReReco_v0 Pixel ML alignment on 06Jul2017ReReco of 297664+297671 (updated VCal calibration, PH, gain calibration) AlCa/DB HN announcement
299228 TrackerAlignment_StartUp17_v7 Pixel ML alignment from 2017 collision data 298996 (post TS1 with new Vcal calibration). Derived against GT 92X_dataRun2_express_v4. AlCa/DB HN announcement
299443 TrackerAlignment_StartUp17_v9 Pixel ML alignment based on Run 299592-97+299614-617. AlCa/DB HN announcement
300558 TrackerAlignment_StartUp17_v10 The new conditions are necessary for full consistency with updates in the pixel local-reco conditions and BPX layer 2 timing settings, leading to improved performance AlCa/DB HN announcement
302539 TrackerAlignment_StartUp17_v11 Consistent with new templates and new HV HN announcement
Show history Hide history

TrackerAlignment_2009_v1_hlt (superseded)

Detailed information at CondDB.

Typically synchronized with TrackerAlignment_2009_v1_express.

since run object comment
246978 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
248618 TrackerAlignment_v2_hltvalidation Wrong upload to production, no data taken, reverted back to TrackerAlignment_v1_hltvalidation till validation
248642 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
251100 TrackerAlignment_v2_hltvalidation Module-level alignment of pixel detector only with 0T data of Run2015A AlCa/DB HN announcement
251607 TrackerAlignment_Run2015B_PseudoPCL_v2 pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256715 TrackerAlignment_for_Run2015D_v0 inconsistent conditions derived from Run2015C data, uploaded by mistake (affected data corrected in prompt reconstruction)
256746 TrackerAlignment_for_Run2015D_v1 conditions derived from Run2015B data
256766 TrackerAlignment_for_Run2015D_v0 inconsistent conditions derived from Run2015C data but centrally validated, therefore till further validation used in HLT. Express used the TrackerAlignment_for_Run2015D_v1 conditions. Difference to express
270856 TrackerAlignment_CRUZET2016 CRUZET alignment for 2016 the alignment constants starting from IOV 260335 of 2015-EOY_v1_RunD
272497 TrackerAlignment_Run2016A_PseudoPCL_v1 Tracker alignment derived from the Pseudo-PCL workflow on run 272011 and conditions in GT 80X_dataRun2_Express_v6 (CRUZET alignment)
276251   updated module level tracker alignment and APE from 2016B AlCa/DB HN announcement
276517 TrackerAlignment_Run2016B_PseudoPCL_276363 pseudo-PCL alignment at 3.8T after magnet cycle on 02.07.2016 AlCa/DB HN announcement
281466 TrackerAlignment_ReReco2016BtoG Tracker alignment updated from September ReReco campaign Alca/DB HN announcement
271866 TrackerAlignment_EOY16_sm1959 Tracker alignment containing 35 IOVs from EOY16 campaign (after new IOVs redefinition) Alca/DB HN announcement

TrackerAlignment_2009_v1_express (superseded)

Detailed information at CondDB.

since run object comment
     
     
246978 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
248618 TrackerAlignment_v2_hltvalidation Wrong upload to production, no data taken, reverted back to TrackerAlignment_v1_hltvalidation till validation
248642 TrackerAlignment_v1_hltvalidation CRUZET+CRAFT alignment AlCa/DB HN announcement
251100 TrackerAlignment_v2_hltvalidation Module-level alignment of pixel detector only with 0T data of Run2015A
251607 [SWGuideAlignmentConstantsRun2015[#TrackerAlignment_Run2015B_Pseudo][TrackerAlignment_Run2015B_PseudoPCL_v2]] pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256715 TrackerAlignment_for_Run2015D_v0 inconsistent conditions derived from Run2015C data, uploaded by mistake (affected data corrected in prompt reconstruction)
256746 TrackerAlignment_for_Run2015D_v1 conditions derived from Run2015B data
257826 TrackerAlignment_Run2015D_PseudoPCL_v0 pseudo-PCL alignment at 3.8T with early Run2015D data AlCa/DB HN announcement
262922 TrackerAlignment_ppRef2015_hltvalidation pseudo-PCL alignment at 3.8T with early Run2015E data AlCa/DB HN announcement
270856 TrackerAlignment_CRUZET2016 CRUZET 2016 alignment AlCa/DB HN announcement
272497 TrackerAlignment_Run2016A_PseudoPCL_v1 Tracker alignment derived from the Pseudo-PCL AlCa/DB HN announcement

TrackerAlignment_prompt (superseded)

Detailed information at CondDB.

This is a new tag that was created by merging the content of the old TrackerAlignment_2009_v1_prompt, which was in use (apparently) up to run 197571, and then inserting all the IOVs from TrackerAlignment_2009_v1_express that were included recently in all the express and prompt GTs.

It is included in the GT for Prompt as of 74X_dataRun2_Prompt_v2.

since run object comment
251607 TrackerAlignment_Run2015B_Pseudo pseudo-PCL alignment at 3.8T AlCa/DB HN announcement
256709 TrackerAlignment_for_Run2015D_v1 conditions derived from Run2015B data (the payload with the younger time stamp)
257826 TrackerAlignment_Run2015D_PseudoPCL_v0 pseudo-PCL alignment at 3.8T with early Run2015D data AlCa/DB HN announcement
262922 TrackerAlignment_ppRef2015_hltvalidation pseudo-PCL alignment at 3.8T with early Run2015E data AlCa/DB HN announcement
270385 TrackerAlignment_CRUZET2016 CRUZET 2016 alignment AlCa/DB HN announcement
272214 TrackerAlignment_Run2016A_PseudoPCL_v1 Tracker alignment derived from the Pseudo-PCL AlCa/DB HN announcement

TrackerAlignmentExtendedErrors_v10_offline_IOVs

Detailed information at CondDB.

TrackerAlignmentExtendedErrors_v9_offline_IOVs

Detailed information at CondDB.

since run object content
1 -- A copy of 43 IOVs from TrackerAlignmentExtendedErrors_v6_offline_IOVs
290101 TrackerAlignmentExtendedErrors_BPIX50_FPIX50_TIB20_TOB20_TID40_TEC40 50mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC
294034 TrackerAlignmentExtendedErrors_ReReco2017_v2 TIB/TOB: 5, TID/TEC: 10, corresponding to alignment IOV 1-4: L1x:10, L1y: 15, L2y: 10, others: 5
298653 TrackerAlignmentExtendedErrors_ReReco2017_v2 TIB/TOB: 5, TID/TEC: 10, corresponding to alignment IOV 5-6: L1x: 10, L1y: 30, L2y: 20, others:5
299443 TrackerAlignmentExtendedErrors_ReReco2017_v2 TIB/TOB: 5, TID/TEC: 10, corresponding to alignment IOV 7-12: L1x: 5, L1y: 10, L2y: 10, others: 5
Note private tag contains only 2017 payload is also created under TrackerAlignmentExtendedErrors_ReReco2017_v2.

TrackerAlignmentExtendedErrors_v8_offline_IOVs

Remake of offline tag created for 2017 Re-reco according to AlCa/DB Announcement. This tag is the updated version of TrackerAlignmentExtendedErrors_v7_offline_IOVs which contains one more payload.

Detailed information at CondDB.

since run object content
1 -- A copy of 43 IOVs from TrackerAlignmentExtendedErrors_v6_offline_IOVs
290101 TrackerAlignmentExtendedErrors_BPIX50_FPIX50_TIB20_TOB20_TID40_TEC40 50mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC
297020 TrackerAlignmentExtendedErrors_StartUp17_v2 APE (in mum) payload based on the last measuerement with 296786: L1x: 30, L1yz: 70, L2y40, rest in pixel: 5; TIB, TOB xyz: 20mum (as before); TID, TEC xyz: 40mum (as before)
299337 TrackerAlignmentExtendedErrors_StartUp17_v4 APE (in mum): L1x: 30, L1yz: 40, L2yz20, rest in pixel: 5; TIB, TOB xyz: 10mum; TID, TEC xyz: 20mum
Note private tag contains only 2017 payload is also created under TrackerAlignmentExtendedErrors_ReReco2017_v1.

TrackerAlignmentExtendedErrors_v7_offline_IOVs

Offline tag created for 2017 Re-reco according to AlCa/DB Announcement.

Detailed information at CondDB.

since run object content
1 -- A copy of 43 IOVs from TrackerAlignmentExtendedErrors_v6_offline_IOVs
290101 TrackerAlignmentExtendedErrors_BPIX50_FPIX50_TIB20_TOB20_TID40_TEC40 50mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC
297020 TrackerAlignmentExtendedErrors_StartUp17_v4 APE (in mum): L1x: 30, L1yz: 40, L2yz20, rest in pixel: 5; TIB, TOB xyz: 10mum; TID, TEC xyz: 20mum
Note private tag contains only 2017 payload is also created under TrackerAlignmentExtendedErrors_ReReco2017_v0.

TrackerAlignmentExtendedErrors_v6_offline_IOVs

Detailed information at CondDB.

since run object content
1 -- Run-I
157865 -- Run-I
238341 TrackerAlignmentExtendedErrors_barrel20_endcap40 CRAFT15
250933 TrackerAlignmentErrorExtended_Run2Startup_v0_mc Start of 2015 data taking? This would correspond to 20/40
250985 TrackerAlignmentExtendedErr_2015-EOY_v1 Run2015B with APEs on mp1896 object
253986 TrackerAlignmentExtendedErr_2015-EOY_v1 Run2015C with APEs on hp1527 object
256547 TrackerAlignmentExtendedErr_2015-EOY_v1 Run2015D with APEs on mp1885 object
266150 TrackerAlignmentExtendedErrors_CRUZET2016 CRAFT16, 100/20/40 APEs
271866 TrackerAlignmentExtendedErrors_EOY16_sm1959 APE for 35 IOVs (final IOV is 284038) from EOY16

Details of Alignment, APE and Surface Deformation

Run 2015

Run 2016

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

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

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

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

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

More details at:

Zmumu studies

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

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

More details at:

TrackerSurfaceDeformations_v8_offline and TrackerAlignment_v18_offline

Tags at _v18_offline and CondDB (surface deformations)

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:

Test tag TrackerAlignment_v14_0T_offline at PREP2 DB.

More details at:

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:

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

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:

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:

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:

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:

APE Objects (Data)

TrackerAlignmentExtendedErrors_EOY16_sm1959 and TrackerAlignmentExtendedErrors_EOY16_SingleIOV_sm1959

TrackerAlignmentExtendedErrors_ReReco2016BtoG

Tag at CondDB

TrackerAlignmentExtendedErrors_Run2016B_*

Tags at CondDB:

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

TrackerAlignmentExtendedErrors_Run2016B

Update of the following tags:

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:

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:

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:

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:

Run 2017

Run 2018

General Information

How to upload new Tracker Alignments to the production GTs

Show description Hide description

First of all, one needs to create new tags to the CondDB browser for global usage (ECAL and Muon people). More information about how to create new tags can be found in hands-on session here.

Then, we should announce these new tags to AlCaDB conveners (cms-PPD-conveners-AlCaDB@cernNOSPAMPLEASE.ch) so they can check and give the green-light to upload them to existing GTs of HLT, Express and Prompt workflows.

After conveners signed-off, what needs to be done is to update, appending a new IOV, the 3 payloads for TrackerAlignment, TrackerSurfaceDeformations and APE, to the existing tags that are already included in the production Global Tags. You can check what are the latest existing production Global Tag for each workflow here. For example, the current Global Tag of HLT is 80X_dataRun2_HLT_v12, Express is 80X_dataRun2_Express_v5 and Prompt is 80X_dataRun2_Prompt_v6.

And in order to check inside each of these Global Tags which are the relevant tags for Tracker Alignment you can use the conddb command within a CMSSW release. 

 conddb list <name_of_the_GT> | grep <name_of_your_record>

(The name_of_your_record relevant for Tracker Alignment are TrackerAlignmentRcd, TrackerSurfaceDeformationRcd and TrackerAlignmentErrorExtendedRcd)

This exercised on the 3 Global Tags above will yield you the table and therefore you can see there is a total of 7 tags to be updated.

All these 6 tags need to be updated. Let's retrive the sqlite files again from the new tags you just created. 

 
conddb_import -c sqlite_file:TrackerSurfaceDeformations_2015-EOY_v1_RunD.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerSurfaceDeformations_2015-EOY_v1_RunD -t TrackerSurfaceDeformations_2015-EOY_v1_RunD

conddb_import -c sqlite_file:TrackerAlignmentExtendedErrors_CRUZET2016.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerAlignmentExtendedErrors_CRUZET2016 -t TrackerAlignmentExtendedErrors_CRUZET2016 

conddb_import -c sqlite_file:TrackerAlignment_HP_CRUZET2016.db -f frontier://FrontierProd/CMS_CONDITIONS -i TrackerAlignment_HP_CRUZET2016 -t TrackerAlignment_HP_CRUZET2016

Then you should do 3 uploads (1 for each of your sqlite files) using the similar metadata files below for each record. 

 uploadConditions.py <name_of_file.db>

The txt files should be in the same folder as the sqlite files in which you upload and since these tags have already the correct synchronization, you don't need to specify the since (the service will automatically synchronize to the correct version).

The examples of metadata files for each record 

 
{
    "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS",
    "destinationTags": {
        "TrackerAlignmentExtendedErr_2009_v2_express_IOVs": {},
        "TrackerAlignmentExtendedErr_2009_v2_hlt_IOVs": {}
    },
    "inputTag": "TrackerAlignmentExtendedErrors_CRUZET2016",
    "since": null,
    "userText": "APE for 2016 startup: 100um for BPix and FPix, 20um for TIB and TOB, 40um for TID and TEC"
}

 
{
    "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS",
    "destinationTags": {
        "TrackerAlignment_PCL_byRun_v2_express": {},
        "TrackerAlignment_PCL_byRun_v0_hlt": {}
    },
    "inputTag": "TrackerAlignment_HP_CRUZET2016",
    "since": null,
    "userText": "Tracker alignment from CRUZET16 data, correcting positions and rotations of the barrel high level structures, starting from IOV 9 of EOY2015"
}

 
{
    "destinationDatabase": "oracle://cms_orcon_prod/CMS_CONDITIONS",
    "destinationTags": {
        "TrackerSurafceDeformations_v1_express": {},
        "TrackerSurafceDeformations_v1_hlt": {}
    },
    "inputTag": "TrackerSurfaceDeformations_2015-EOY_v1_RunD",
    "since": null,
    "userText": "Tracker Surface deformation from IOV9 of EOY 2015 alignment"
}

Example of how to import a payload from the DB into a local sqlite file, e.g. to prepare a tag with results of the pseudo-PCL workflow for central validation. The following will retrieve the payload of the IOV starting with 275375, put it into the local sqlite file SiPixelAli_PCL_v0_prompt_r275375.db and set the IOV range from 1 to infinity: 

 
conddb_import -c sqlite_file:SiPixelAli_PCL_v0_prompt_r275375.db -f frontier://FrontierPrep/CMS_CONDITIONS -i SiPixelAli_PCL_v0_prompt -t SiPixelAli_PCL_v0_prompt_r275375 -b 275375

echo 'update IOV set SINCE=1 where SINCE=275375;' | sqlite3 SiPixelAli_PCL_v0_prompt_r275375.db

How to monitor PCL alignment workflows

Show description Hide description

  • Our SiPixelAli_PCL can be monitored here as well as the others PCL. You can see there is a plot for SiPixelAli_pcl.
  • If you click on the legend at the top right of pclMon page, it will explain the meaning of each color. Basically when it's white, it means no payload was uploaded but when it's green, something has been uploaded (there is also some potential delay which sometimes you might see it's purple, don't panic, it will turn green sometime later but report to AlCa /DB if it's not the case)
  • Once you know if the payload has been uploaded or not, you can check the parameters on the offline DQM GUI, for example here DQM link, there is a series of plots for each run (click on Run #). You can see numbers of run from current data taking corresponding to run numbers on pclMon page and you can check DQM for those runs which have new payload uploaded.
  • You can also check PV performance for example this link or on-time monitoring from this link.
  • You can even double-check new payload uploaded via conddb command line, for example, 
 conddb list TrackerAlignment_PCL_byRun_v2_express | grep 2016-08-20
  • or from condDB browser, link.

Note 1 see monitoring illustration from Chayanit's slides reported in TkAl meeting on 24 Aug 2016.

Note 2 small tip for circulating the DQM links: click on the small anchor sign on the top right part of the screen with the "link me" text, copying the URL won't work because each user session is accessible only under his/her own GRID certificate.

Responsible: TamasAlmosVami

Attachments Attachments
Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt create_scenarios.py.txt r2 r1 manage 10.2 K 2008-06-16 - 17:04 MartinWeber Tool for creation, validation and database insertion of tracker database objects, e.g. misalignment scenarios.
Textini scenarios.ini r1 manage 0.7 K 2008-06-16 - 17:05 MartinWeber File containing description of scenarios, used by create_scenarios.py
Edit | Attach | Watch | Print version | History: r252 | r243 < r242 < r241 < r240 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r241 - 2020-03-05 - TamasAlmosVami
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2021 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