Tracker Alignment Constants for Run II -- 2017

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: 5

Alignment and Surface Deformation Objects (Data)

2017 Ultra Legacy conditions

  • Conditions: Single IOV tags TrackerAlignment_2017_ultralegacy_v1 + TrackerSurfaceDeformations_2017_ultralegacy_v1 + TrackerAlignmentExtendedErrors_2017_ultralegacy_v2 packaged into multi-IOV tags TrackerAlignment_v25_offline + TrackerSurfaceDeformations_v12_offline + TrackerAlignmentExtendedErrors_v12_offline_IOVs
  • Internal validation + Fine APE validation
  • AlCaDB HN and TK alignment HN + Follow up message
  • Local alignment object is here: /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/MP/MPproduction/um0003/jobData/jobm/um0003.db
  • As the naming suggests, 2017_ultralegacy contain only the 2017 part (from run 297049)
  • AlCaDB HN
  • Internal validation

TrackerAlignment_v25_offline contains
 - the past from TrackerAlignment_v23_offline
 - TrackerAlignment_2017_ultralegacy_v1 from 297049
 - and TrackerAlignment_v24_offline from 313041

TrackerSurfaceDeformations_v12_offline contains
 - the past from TrackerSurfaceDeformations_v11_offline
 - TrackerSurfaceDeformations_2017_ultralegacy_v1 from 297049
 - and TrackerSurfaceDeformations_v11_offline from 313041

TrackerAlignmentExtendedErrors_v12_offline_IOVs contains
 - the past from TrackerAlignmentExtendedErrors_v9_offline_IOVs
 - TrackerAlignmentExtendedErrors_2017_ultralegacy_v2 from 297049
 - and TrackerAlignmentExtendedErrors_v10_offline_IOVs from 313041

  • Conditions: TrackerAlignmentExtendedErrors_2017_ultralegacy_v2
  • History
297049 -  TrackerAPE_merged_mp3029
298653 -  TrackerAPE_merged_um0001
301046 -  TrackerAPE_merged_um0001
301392 -  TrackerAPE_merged_mp3029
303998 -  TrackerAPE_merged_um0001
304447 -  TrackerAPE_merged_mp3029
304663 -  TrackerAPE_merged_um0001
304991 -  TrackerAPE_merged_mp3029
306464 -  TrackerAPE_merged_mp3115

  • Conditions: Multi IOV tags TrackerAlignment_v25_offline + TrackerSurfaceDeformations_v12_offline + TrackerAlignmentExtendedErrors_v11_offline_IOVs
  • AlCaDB HN and TK alignment HN
TrackerAlignment_v25_offline contains
 - the past from TrackerAlignment_v23_offline
 - TrackerAlignment_2017_ultralegacy_v1 from 297049
 - and TrackerAlignment_v24_offline from 313041

TrackerSurfaceDeformations_v12_offline contains
 - the past from TrackerSurfaceDeformations_v11_offline
 - TrackerSurfaceDeformations_2017_ultralegacy_v1 from 297049
 - and TrackerSurfaceDeformations_v11_offline from 313041

TrackerAlignmentExtendedErrors_v11_offline_IOVs_fixed contains
 - the past from TrackerAlignmentExtendedErrors_v9_offline_IOVs
 - TrackerAlignmentExtendedErrors_2017_ultralegacy_v1 from 297049
 - and TrackerAlignmentExtendedErrors_v10_offline_IOVs from 313041

TrackerAlignmentExtendedErrors_v11_offline_IOVs by mistake contained TrackerAlignmentExtendedErrors_2017_ultralegacy_v2 as well

TrackerAlignment_v23_offline

NB: IDENTICAL TO v21

  • CondDB tag contains TrackerAlignment_v21_offline + additional IOV from mp2636/jobm1 (IOV13)
  • Only update of the alignment from 305898.
  • TIF HN and AlCaDB HN

Compiling information from v21 and v23:

IOV since test run int. lumi/fb alignmet+surfaces APE Era
1 294034 296173 0.0 mp2608 v1 Run2017A
2 296641 297057 0.3 mp2608 v1 Run2017A
3 297179 297219 2.0 mp2608 v1 Run2017B
4 297281 297503 2.6 mp2608 v1 Run2017B
5 298653 299061 6.4 hp2300 v2 Run2017B
6 299277 299368 7.3 hp2300 v2 Run2017B
7 299443 300157 8.1 hp2300 v3 Run2017C
8 300389 300560 11.8 mp2608 v3 Run2017C
9 301046 301472 15.9 mp2607 v3 Run2017C
10 302131 302472 20.3 hp2300 v3 Run2017D
11 303790 304292 25.3 hp2300 v3 Run2017E
12 304911 305108 35.3 mp2607 v3 Run2017F
13 305898 305898 37.7 mp2636   Run2017F

TrackerAlignment_v22_offline

DO NOT USE!

TrackerAlignment_v21_offline + TrackerSurfaceDeformations_v11_offline + TrackerAlignmentExtendedErrors_v9_offline_IOVs

Tags at CondDB:

Announcement: TIF hypernews and AlCaDB

IOV since test run int. lumi/fb alignmet+surfaces APE Era
1 294034 296173 0.0 mp2608 v1 Run2017A
2 296641 297057 0.3 mp2608 v1 Run2017A
3 297179 297219 2.0 mp2608 v1 Run2017B
4 297281 297503 2.6 mp2608 v1 Run2017B
5 298653 299061 6.4 hp2300 v2 Run2017B
6 299277 299368 7.3 hp2300 v2 Run2017B
7 299443 300157 8.1 hp2300 v3 Run2017C
8 300389 300560 11.8 mp2608 v3 Run2017C
9 301046 301472 15.9 mp2607 v3 Run2017C
10 302131 302472 20.3 hp2300 v3 Run2017D
11 303790 304292 25.3 hp2300 v3 Run2017E
12 304911 305108 35.3 mp2607 v3 Run2017F
13 305898 305898 37.7 mp2636 v3 Run2017F

Details:

  • summary of performance at DPG meeting November 14, 2017
  • final candidates and validation (incl. also non-selected test objects): TkAl meeting November 1, 2017
  • APE TkAl meeting November 15, 2017
  • For each IOV, hp2300 was run in three steps with 10 iterations each: first, aligning the high level structures in both BPIX and FPIX, then aligning BPIX at module level including the primary vertex constraint, then aligning FPIX (except local w) at module level. The first step used cosmics+collisions in IOVs 5, 7, 10, and 11, where there were enough cosmic tracks for them to provide a reasonable constraint; in IOV 6 there were not enough cosmics, so only collisions were used. The second and third steps used collisions only in all IOVs.
  • Doc for IOV13

TrackerAlignment_forPrompt2017_v1

Post-TS2 pixel ML alignment (on top of updates by PCL), consistent with v6 gain calibration and v10 templates. Internal reference mp2564/jobm1.

Tag at CondDB

Details of the object and validation are discussed in

To summarize, the PV performance got improved especially in dz vs eta, DMR in BPX similar as GT and FPX got improved. The chi2 probability plot is included to show the difference between 0 APE and the current APE in GT.

TrackerAlignment_StartUp17_v11

consistent with the new deployed pixel templates and new HV in strips

Tag at CondDB

Internal ID hp2250 ( validation)

Anouncement on Hypernews

TrackerAlignment_forFall2017ReReco_v0 + TrackerSurfaceDeformations_forFall2017ReReco_v0

Tags at CondDB:

Full strips-detector module level alignment, pixel HL. Surface deformations same as TrackerSurfaceDeformations_StartUp17_v9. Derived against GT 92X_dataRun2_Prompt_v8 from runs 300400 - 301649 with min-bias, iso-mu, Z-mumu, and cosmics. Internal id mp2541/jobm1.

Details at Tracker Alignment Meeting, 2017-08-30 in the presentations

TrackerAlignment_v20_offline + TrackerSurfaceDeformations_v10_offline

Tags at CondDB:

The offline tags created according to the request from AlCa/DB HN which contain multi-IOVs from 2016 Legacy and 2017 selected payloads.

TrackerAlignment_ReReco2017_v0 + surfaces +APE

Tags at CondDB:

Private tags are created to contain only 2017 multi-IOVs and prepare for 2017 Re-Reco as proposed in AlCa/DB Meeting.

TrackerAlignment_StartUp17_v10

consistent with the new deployed pixel templates and the L2 timing

Tags at CondDB:

Pixel ML alignment on 300389. Internal ID sm2251. More information in TkAl HN announcement.

TrackerAlignment_StartUp17_v9 + surfaces

Tags at CondDB:

Pixel ML alignment based on Run 299592-98+299614-617. The update was to accommodate the new pixel template (v7) and the latest timing settings. Internal ID sm2238. Full validation at TkAlStartUp2017/express_299380_v2.pdf, TkAlStartUp2017/express_299592-98_smonly_v2.pdf, TkAlStartUp2017/express_299614-17_smonly_v2.pdf.

TrackerAlignment_StartUp17_v8 + surfaces

Tags at CondDB:

Pixel ML alignment from 2017 collision data 299327 (after magnet trip 17-Jul). Internal ID mp2505. Derived against GT 92X_dataRun2_express_v4. Full validation at TkAlStartUp2017/express_299329.pdf

TrackerAlignment_StartUp17_v7

Tags at CondDB:

Pixel ML alignment from 2017 collision data 298996 (post TS1 with new Vcal calibration). Internal ID hp2042. Derived against GT 92X_dataRun2_express_v4 (includes the templates v6). Full validation at TkAlStartUp2017/express_298996.pdf

TrackerAlignment_StartUp17_v6 + surfaces

Tags at CondDB:

Pixel ML alignment + surfaces from 2017 collision data, runs 298653, 298671, 298678, including cosmics runs 298647/48/51/57/58/61/68. Internal ID hp2225. Derived against GT 92X_dataRun2_express_v2. Full validation at TkAlStartUp2017/hptest_170710_298653_71_78_with9_2_0_withPCL.pdf

TrackerAlignment_from06Jul2017ReReco_v0 + surfaces

Tags at CondDB:

Pixel ML alignment on 06Jul2017ReReco of 297664+297671 (updated VCal calibration, PH, gain calibration), based on conditions in 92X_dataRun2_July6ReReco_PixelCommissioning_v2 + dedicated templates SiPixelTemplateDBObject_phase1_38T_2017_v6. Internal id mp2498/jobm1.

Remarks:

TrackerAlignment_from04Jul2017ReReco_v0

Tags at CondDB:

Pixel ML alignment on 04Jul2017ReReco of 297292 (updated VCal gain calibration), based on conditions in 92X_dataRun2_July4ReReco_PixelCommissioning. Internal id mp2495.

TrackerAlignment_StartUp17_v5 + surfaces

Tags at CondDB:

Pixel ML alignment + surfaces from 2017 collision data, run 297292 mp2494. Derived against GT 92X_dataRun2_express_v2 plus SiPixelTemplateDBObject_phase1_38T_2017_v3_hltvalidation template CPE that is appropriate for bias voltage of 200 V in layer 1, 100 V other layers.

NB: above tags are identical to the tags with same name appended by _forHLTValidation.

TrackerAlignment_StartUp17_v4 + surfaces

Tags at CondDB:

Pixel ML alignment + surfaces from 2017 collision data, run 297211 hp2207. Derived against GT 92X_dataRun2_express_v2 plus SiPixelTemplateDBObject_phase1_38T_2017_v2_hltvalidation template CPE that is appropriate for bias voltage of 100 V (fixing the wrong templates in GT).

Validation presented at tracker-alignment meeting, 2017-06-21.

Note, due to some mistake, tracker alignment contains 3 payloads corresponding to object hp2207, mp2494 and hp2207. The correct object should be hp2207 as the latest payload (hash 04d204f309394e486a187accba60ee107e517824).

TrackerAlignment_StartUp17_v3 + surfaces

Tags at CondDB:

Pixel ML alignment + surfaces from 2017 collision data, run 296786 hp2195. Derived against GT 92X_dataRun2_express_v2 plus SiPixelTemplateDBObject_phase1_38T_2017_v2_hltvalidation template CPE that is appropriate for bias voltage of 100 V (fixing the wrong templates in GT).

TrackerAlignment_StartUp17_v2

Tag at CondDB: TrackerAlignment_StartUp17_v2

Pixel ML alignment from 2017 collision data, run 296786 mp2480. Derived against GT 92X_dataRun2_express_v2 for appropriate runs (see below).

The object has been derived using the collision data of the runs 296786. The template CPE of the GT 92X_dataRun2_express_v2 were used in the track re-fits. It is based on the GT, which was essentially hp2026. The movement compared to the pervious object is below 50 μm, except for few modules in BPX layer1. The object mostly improves the BPX resolution in all layers, as seen from the DMR validation. The run has a more optimized timing setting for BPX.

Full set of validations (mp2480 in dark turquoise).

TrackerAlignment_StartUp17_v1

Tag at CondDB: TrackerAlignment_StartUp17_v1

Pixel ML alignment from 2017 collision data, run 295463 hp2026. Derived against GT 92X_dataRun2_express_v2 for appropriate runs (see below).

The object has been derived using the collision data of the runs 295463. The template CPE of the GT 92X_dataRun2_express_v2 were used in the track re-fits. It is based on the GT, which was essentially mp2438. The movement compared to the pervious object is at maximum ~100 μm, mostly in BPX layer1. The object mostly improves the BPX layer1 resolution, as seen from the DMR validation. The run has a more optimized timing setting for BPX, derived also a better performance in Primary vertex.

Full set of validations (hp2026 in cyan in DMR and in black in PV).

TrackerAlignment_StartUp17_v0

Tag at CondDB: TrackerAlignment_StartUp17_v0

Pixel ML alignment from first 2017 collision data + CRAFT/interfill cosmics. Internal reference mp2438. Derived against GT 92X_dataRun2_express_v2 for appropriate runs (see below).

The object has been derived using the collision data of the runs 295209+295210 as well as CRAFT (private rereco) and interfill cosmics data. The template CPE of the GT 92X_dataRun2_express_v2 were used in the track re-fits. It is the result of several iterations with successively more degrees of freedom aligned as well as a final iteration to test the stability of the solution. We find positions of the pixel high-level structures to be within 50mum of the position in the GT, in agreement to what was earlier observed in PCL. Individual modules can have significantly larger differences. Note that for one FPX module, a position difference of 4mm is found. The local resolution (as measured by the DMRs) improves significantly, in particular in FPX. We also see different performance in the different BPX layers, clearly worst in Layer 1. We also observe that the curvature of the modules, which is assumed to be flat in the current reconstruction, is not well modeled in FPX (BPX hard to tell with given precision). In the current alignments, it is not adjusted, but this is sth. to be improved in a next iteration with mored data. The primary vertex performance is slightly improved over the GT, not much though. We assume also some interplay with the beamspot that is taken from the GT for this validation.

All modules were aligned except

  • 82 modules receiving no hits at all;
  • 29 modules receiving less than a minimum number of hits required for the alignment fit.

Full set of validations (mp2438 in cyan).

TrackerAlignment_CRAFT17_v0

Tag at CondDB: TrackerAlignment_CRAFT17_v0 Identical to mp2398 documented below.

Validations presented at TkAl meeting 2017-05-17.

CRAFT17 PREP Objects

date object description
2017-05-17 TrackerAlignment_mp2399 mp2399/jobm: CRAFT-data alignment: pixel HL, strips HL (started from CRUZET ML alignment TrackerAlignment_mp2397), add. comments 2
2017-05-17 TrackerAlignment_mp2398 mp2398/jobm: CRAFT-data alignment: pixel HL, strips HL (started from CRUZET ML alignment TrackerAlignment_mp2397), add. comments 2
Additional comments 1
  • Depends on surface conditions in GT 90X_dataRun2_Express_v4 for IOV 290550
  • Includes full pixel detector, using private rereco for those runs that include BPX; simultaneous alignment of all detectors
  • APE=0 in fit (fully correct covariance matrix); APE=100mum in pixel for re-fit
  • Generic CPE (as templates not working)
  • Entries cut 15
    • Ladders/blades receiving hits (i.e. non-dead modules) but below N(hits) threshold: 6.0%. For mp2399, those ladders/blades are not aligned
    • Ladders/blades without hits: 1.7% (attributed to dead modules)

TrackerAlignment_CRUZET17_v4

Tag at CondDB: TrackerAlignment_CRUZET17_v4 Same as TrackerAlignment_mp2397 documented below at "CRUZET17 PREP Objects"

TrackerAlignment_CRUZET17_v3

Tags at CondDB:

A few informations from routine aligners: (mp2374)

  • Starting geometry: TrackerAlignment_CRUZET17_v1
  • Type of data used to derive it: CRUZET17 Express data (runs 290550-292358)
  • use case for the payload: ML-FPIX alignment to improve data taking performance

TrackerAlignment_CRUZET17_v1

Tags at CondDB:

Content:

  • Pixel High-Level alignment (excluding BPIX hits): mp2358
  • The first CRUZET Alignment for 2017 included in the production
  • Ignoring pixel hits in the track-refit and alignment. Otherwise identical to mp2355

More details can be found here.

Tags at CondDB:

Content:

  • Pixel High-Level alignment (excluding BPIX hits): mp2355

More details can be found here.

PreCRUZET2017 _v1

Content:

  • pixel is ideal
  • strip from IOV 284038 in TrackerAlignment_EOY16_sm1959 (54f63024c9dff456c4c812a32bc2368a92f4e467) and from IOV 271866 in TrackerSurfaceDeformations_EOY16_mp2269 (92a2c43586e74f3d197a46af56194c6bb9780814)

New tags:

CRUZET17 PREP Objects

date object description
2017-05-12 TrackerAlignment_mp2397 mp2397/jobm: CRUZET-data alignment: pixel ML, strips HL (iteration of mp2396/jobm, entries: 15), add. comments 1
2017-05-12 TrackerAlignment_mp2396-2 mp2396/jobm2: CRUZET-data alignment: pixel ML, strips HL (entries: 15), add. comments 1
2017-05-12 TrackerAlignment_mp2396 mp2396/jobm: CRUZET-data alignment: pixel ML, strips HL (entries: 25), add. comments 1
2017-05-08 TrackerAlignment_mp2387 BPX ML alignment mp2387 description
2017-05-02 TrackerAlignment_mp2374 FPX ML alignment mp2374; same object as # TrackerAlignment_CRUZET17_v3
Additional comments 1
  • Depends on surface conditions in GT 90X_dataRun2_Express_v4 for IOV 290550
  • Includes full pixel detector, using private rereco for those runs that include BPX; simultaneous alignment of all detectors
  • APE=0 in fit (fully correct covariance matrix)
  • Generic CPE (as templates not working)
  • Modules receiving hits (i.e. non-dead modules) that are not aligned because N(hits) below threshold: 1.7% (in case of entries cut 15), 10.8% (in case of entries cut 25)
  • Total amount of pixel modules w/o hits: 4.4% (attributed to dead modules)

APE Objects

APE Objects with Fixed Values

The following APE scenarios were created with fixed APE (given in mum in the tag name) and are valid for the Phase-I detector.

APE PROD Objects:

date object (DB) description
2017-07-21 TrackerAlignmentExtendedErrors_StartUp17_v5 APE BPIX and FPX: 5, except BPX L1 x direction (10) TIB: 5 TOB: 10 TID and TEC; 20 for TrackerAlignment_forPrompt2017_v1.
2017-07-21 TrackerAlignmentExtendedErrors_StartUp17_v4 APE (in mum): L1x: 30, L1yz: 40, L2yz20, rest in pixel: 5; TIB, TOB xyz: 10mum; TID, TEC xyz: 20mum; based on APE measurement on 299327-29 for TrackerAlignment_StartUp17_v8 and TrackerSurfaceDeformations_StartUp17_v8
2017-07-07 TrackerAlignmentExtendedErrors_StartUp17_v3 moderately inflated over v2 pixel APE for after TS1-magnet ramp. 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)
2017-06-22 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)
2017-06-17 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); values based on measuerement presented at TkAl meeting, June 7, 2017
2017-05-18 TrackerAlignmentExtendedErrors_BPIX50_FPIX50_TIB20_TOB20_TID40_TEC40 50mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC
2017-05-18 TrackerAlignmentExtendedErrors_BPIX100_FPIX100_TIB20_TOB20_TID40_TEC40 100mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC
2017-05-18 TrackerAlignmentExtendedErrors_BPIX500_FPIX500_TIB20_TOB20_TID40_TEC40 500mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC

APE PREP Objects

date object (DB) description
2017-06-09 TrackerAlignmentExtendedErrors_BPX-L1-Scenario_v0 BPX Layer 1: 500mum x,y,z; BPX Layer 2: 10mum x,z and 40mum y; BPX Layer 3+4: 10mum x,y,y; FPX,TIB,TOB: 10mum x,y,y; TID,TEC: 20mum x,y,y
2017-05-17 TrackerAlignmentExtendedErrors_BPIX50_FPIX50_TIB20_TOB20_TID40_TEC40 50mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC
2017-05-08 TrackerAlignmentExtendedErrors_BPIX100_FPIX100_TIB20_TOB20_TID40_TEC40 100mum in pixel; 20 mum in TIB,TOB; 40 mum in TID, TEC

Dedicated APE Objects

The following APE objects were measured in data and are valid for the Phase-I detector.

date object (DB) description
2017-05-22 TrackerAlignmentExtendedErrors_Upgrade2017_pseudoAsymptotic_v3 Dedicated APE object for TrackerAlignment_Upgrade2017_pseudoAsymptotic_v3; see comment 1
Comment 1
  • Contains the values listed in Valeria's slide 8 in the column sigma(pseudo-asym17, alignment), where I took the larger value for the z-coordinate.
  • For the strips I took the values from 2016 MC scenario.

Alignment and Surface Deformation Objects (MC)

TrackerAlignment_2017_ultralegacymc_v2

Tag at CondDB : TrackerAlignment_2017_ultralegacymc_v2

Corresponding APEs: TrackerAlignmentExtendedErrors_2017_ultralegacymc_v2

  • /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/data/commonValidation/CMSSW_10_5_0_NumberOfHitsperModule/src/Alignment/MCscenarioUL2017/move_FPIX_realistic_30plus30minus.db
  • SG : Gaussian smearing of design geometry
  • Alignment trying to mimic data UL17 campaign
  • APEs also investigated to match the data
  • Adding a systematic misalignment by hand in the FPIXes to better describe the IP vs eta in data

Internal validation is here.

TrackerAlignment_2017_ultralegacymc_v1

Tag at CondDB : TrackerAlignment_2017_ultralegacymc_v1

Corresponding APEs: TrackerAlignmentExtendedErrors_2017_ultralegacymc_v1

  • mp3149
  • SG : GT 105X_mc2017_realistic_v5

Internal validation is here.

TrackerAlignment_Upgrade2017_realistic_v3

Tags:

Description:

  • use step 1 from 2018 scenario (done with 100X samples) as new scenario for 2017, fixing most WMs
  • internal validation: link
  • object: mp2813 jobm6

TrackerAlignment_Upgrade2017_realistic_v2 and TrackerAlignmentSurfaceDeformations _Upgrade2017_realistic_v0 and TrackerAlignmentExtendedErrors _Upgrade2017_realistic_v2

For MC V2 production campaign after bug fixed and performance optimization in TIB as announced on AlCa/DB HN.

Tags:

TrackerAlignment_Phase1Realistic_v2 and TrackerSurfaceDeformations_Phase1Realistic_v2 and TrackerAlignmentExtendedErrors _Phase1Realistic_v2

Tags:

TrackerAlignment_Phase1Realignment_CRAFT

Starting geometry: corresponding CRUZET payload (see below)

Alignables: pixel only

  1. ML alignment

Tags at CondDB

TrackerAlignment_Phase1Realignment_CRUZET

Starting geometry: TrackerAlignment_Phase1Startup_Misalignment_v0

Alignable: pixel only, in two steps

  1. HLS alignment
  2. HLS+ML alignment

Different statistics are available at CondDB:

TrackerAlignment_Phase1Startup_Misalignment_v0

Tag at CondDB

Realistic startup scenario after installation and before any alignment procedure.

TrackerAlignment_Upgrade2017_pseudoAsymptotic_v0

Tag at CondDB

Random gaussian smearing of the module position in BPIX and FPIX using the RMS of the BPIX and FPIX spread of the modules in the current asymptotic phase-0 scenario.

(Documentation coming soon)

WARNING: based on wrong ideal geometry. Do not use!

TrackerAlignment_Upgrade2017_pseudoAsymptotic_v1

Hybrid scenario of 2016 asymptotic MC scenario for pixel and a-priori set alignment for Phase-I pixel, based on the 2016 MC scenario in the pixel.

This scenarios was created to get a phase-1 scenario with similar performance as the phase-0 asymptotic scenario by applying the RMS values from the phase-0 pixel as gaussian smearing to the phase-1 pixel. The values are documented here The strips alignment is as in the 2016 MC asymptotic scenario for MC 80X, presented at the AlCa/DB meeting, March 7, 2016.

This scenario goes together with the "realistic" surfaces (NB: ideal in pixel, NOT ideal in strips!).

WARNING: based on wrong ideal geometry. Do not use!

MC Production Scenarios

Fixed ideal phase-I geometry TrackerAlignment_Upgrade2017_design_v4

"Ideal" alignment with fixed phase-I geometry

Original payload: /afs/cern.ch/work/g/ghellwig/public/for_alca-db_contacts/tracker_alignment_payloads__pixel_ideal__strips_aligned_to_91X_upgrade2017_design_Candidate_2017_05_10_09_23_53.db

Pseudo-asymptotic scenario TrackerAlignment_Upgrade2017_pseudoAsymptotic_v2

"pseudo asymptotic" alignment: emulating the expected asymptotic performance by applying the residual resolution of the 2016 MC asymptotic scenario (in strips: same as 2016, in pixel: 2016 resolution applied as smearing to the phase-I detector)

This scenarios was created to get a phase-1 scenario with similar performance as the phase-0 asymptotic scenario by applying the RMS values from the phase-0 pixel as gaussian smearing to the phase-1 pixel. The values are documented here The strips alignment is as in the 2016 MC asymptotic scenario for MC 80X, presented at the AlCa/DB meeting, March 7, 2016.

This scenario goes together with the "realistic" surfaces (NB: ideal in pixel, NOT ideal in strips!).

Original payload: /afs/cern.ch/work/g/ghellwig/public/for_alca-db_contacts/geometry_MisalignmentScenario_PhaseI_PseudoAsymptotic__from_tracker_alignment_payloads__pixel_ideal__strips_aligned_to_91X_upgrade2017_realistic_Candidate_2017_05_10_16_13_16.db

Pseudo-asymptotic scenario TrackerAlignment_Upgrade2017_pseudoAsymptotic_v3

"pseudo asymptotic" alignment: emulating the expected asymptotic performance by applying the residual resolution of the 2016 MC asymptotic scenario (in strips: same as 2016, in pixel: started with 2016 resolution applied as smearing to the phase-I detector, and then was scaled down to match the performance observed in EOY16 data). It is the same as TrackerAlignment_Upgrade2017_pseudoAsymptotic_v2, but the pixel smearing factors where reduced by factors of 0.2 in FPX and 0.5 in BPX to match the DMR performance (RMS of alignment curve, RMS of ideal subtracted quadratically) in EOY16 data.

Original payload: /afs/cern.ch/cms/CAF/CMSALCA/ALCA_TRACKERALIGN/PayLoads/2017-05-12_PseudoAsymptoticMCScenario/pseudo-asymptotic_FPX-0p2_BPX-0p5.db

Documentation at Tracker-alignment meeting, 2017-05-22

Technical PREP MC payloads

TrackerAlignment_Upgrade2017_design_v4_strips-EOY16

Technical payload for CRUZET/CRAFT17 validation studies:

Original payload: /afs/cern.ch/work/g/ghellwig/public/for_alca-db_contacts/tracker_alignment_payloads__pixel_ideal__strips_aligned_to_TrackerAlignment_PreCRUZET2017_v1.db

-- ChayanitAsawatangtrakuldee - 2017-03-22

Edit | Attach | Watch | Print version | History: r73 < r72 < r71 < r70 < r69 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r73 - 2019-10-03 - 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback