cms track trigger: tower definition and optimization · • assign one tower to each region!! •...

46
Olmo Cerri – September 22 th 2016 Supervisor: Luciano Ristori CMS Track Trigger: Tower definition and optimization

Upload: others

Post on 27-May-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Olmo Cerri – September 22th 2016!!

Supervisor: Luciano Ristori!!

CMS Track Trigger:!Tower definition and

optimization!

Page 2: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

The Compact Muon Solenoid!

2!

Strength:!•  Hermeticity!•  Precise measurement

of charged tracks momenta!

•  Particle ID!General purpose experiment:!•  Standard Model (Higgs, top…)!•  New physics searches: (BSM, dark matter…)!

Collaboration:!•  3500 scientist!•  43 countries!

Location:!•  Worldwide

construction!•  Now at LHC – IP8!

Page 3: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

CMS Tracker!

3!

Silicon strip:!!•  200 m2 active area, 9.6 M channel!•  10x10 cm2 modules!•  Strip dimensions: 90μm x 5cm!•  2 strip sensors on top of each

other : crude PT threshold!

Page 4: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

The challnge: HL-LHC!

4!

Machine:!•  Same tunnel as LHC!•  Installation in 2023!•  Physics run in 2026!•  from 300 to 3000 fb-1!•  25 nm bunch crossing!•  Lpeak ≥ 5 x 1034 cm-2s-1!

Each event:!•  14 TeV energy!•  Up to 200 average simultaneous

interactions!•  1000 Tb/s from silicon tracker!

Page 5: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Trigger!

5!

All data can not be stored at that rate!

Trigger: real-time event selection!

Phase II upgrade goal:!Implement tracks reconstruction in few μs for L1 trigger use!

Extremely challenging goal:!•  40 MHz crossing frequency (one each 25 ns)!•  ~ 20,000 hits/crossing!•  ~ 100 tracks to be identified above 2GeV/c PT!•  Track parameters to be extracted with quasi-offline precision!

Page 6: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

AM + FPGA approach!

6!

•  Associative Memory + FPGA approach successfully used in CDF (2002-2011)!

!•  Currently being implemented in Atlas

(FTK project)!!•  Both at trigger Level 2 with looser

time constraints!

Page 7: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Simulated example!

7!

Balancing the workload:!AM Pattern Bank size VS FPGA resources/latency!

Page 8: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Divide and conquer!

8!

•  Detector can be sliced into independent regions (Trigger Towers)!

•  Each one need its own electronics (ATCA crate)!-  Data collection from front-end modules!-  AM pattern recognition!-  FPGA for track fitting!

•  8 region in ϕ and 6 in η!•  = 48 towers!

Page 9: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

TT definition procedure!

•  Divide parameter space into 48 non-overlapping regions!!•  Assign one tower to each region!!•  Define 48 “training samples”, one per tower!

–  Use single muon sample !•  2π in φ and η = [-2.4, +2.4]!•  PT ≥ 2 GeV and σz = 5 cm!•  Select tracks from one of the 48 regions!!

•  Assign modules to a tower!–  Go through the tracks in the corresponding training sample!–  Add all modules hit by at least one track!! 9!

Page 10: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

TT definition problem!

10!

•  Track parameter space is 4-dim (q/PT, ϕ, η, vz)!•  4-dim region can be conveniently defined by the intersection of two weakly

correlated projections: (q/PT, ϕ) and (η, vz)!•  Disjoint phase-space regions correspond to overlapping physical regions!•  Overlap due to track curvature (ϕ) and to finite vz dimension (η)!

One of the goals is to minimize overlap regions !without compromizing acceptance!

Page 11: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Minimizing the Overlap!

11!

Regions are better defined in terms of ϕ(R*) instead of ϕ(0)!•  Minimize the number of detector

modules to be shared among trigger towers!

!!

Shift positive wrt negative tracks: !

Less overlap needed!!

Page 12: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Parameter space regions!

12!

R⇤� = R⇤

⌘ = 58.89 cm

•  Defined in terms of R*:!-  η* = η(R*)!-  Φ* = Φ(R*)!

•  8 equal division in Φ* !•  6 equal division in η*! Might be further optimized!

Page 13: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Naïve vs New definition!

13!

Each tower needs to see 400-500 front-end modules!

Page 14: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Intermediate example – TT[5,2]!

14!

Training sample!Acceptance!

Page 15: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

R* optimization!

15!

[cm]φR*0 20 40 60 80 100 120

Tota

l num

ber o

f con

nect

ion

5000550060006500700075008000850090009500

10000barrelintermediateendcapActual value = 58.89ηR*

- 3.0M sampleφ

Connection required for different R*

[cm]ηR*0 20 40 60 80 100 120

Tota

l num

ber o

f con

nect

ion

5000

6000

7000

8000

9000

10000

11000

12000barrelintermediateendcapActual value

= 58.89φR*

- 3M sampleη

Connection required for different R*

•  Optimization parameter: total number of connection between TT and modules!

•  Barrel, intermediate and forward regions treated separately!•  Scan R* in one view for a given R* on the other!

R*η is already in a minimum plateau!R*ϕ can be optimized up to 5%!

Page 16: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

A different R* optimization!

16!

§  Number of modules R* optimization:!-  Goal: Minimize the number modules connected!-  High R*phi are favored because of module dimensions!

!§  First study does not take in account that same modules produce a

significant larger number of stubs wtr to other ones!-  E.g. inner or forward modules are more likely to be overcrowded

by pileup events!

!§  New different study has been done to take in account this effect!

-  Each module has to be weighted using the amount of stubs that produce on average!ª  PU only events can be used to establish weights!

-  Minimize the sum of the weights!-  Inner and forward modules are disfavored!

Page 17: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

R* weighted results!

17!

[cm]ηR*0 20 40 60 80 100 120

Tota

l num

ber o

f con

nect

ion

wei

ghte

d

8000

10000

12000

14000

16000

18000barrelintermediateendcapActual value

= 90.00φR*

- 5.0M sampleη

Weighted Connection required for different R*

[cm]φR*0 20 40 60 80 100 120

Tota

l num

ber o

f con

nect

ion

wei

ghte

d

7000

8000

9000

10000

11000

12000

13000

14000barrelintermediateendcapActual value

= 60.00ηR*

- 5.0M sampleφ

Weighted Connection required for different R*

•  To be compared with slide 15!•  Different approach different results!•  Minima seems slightly deeper and displaced to lower R*!•  To be understand what will be the real bottleneck and which

optimization is more useful!

Actual values corresponds also to previous study minimum!

Page 18: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Modules per tower - acceptance trade-off!

18!

Target:!•  Minimize the number of modules included in each tower:!

-  Remove modules less involved!-  Compromise between acceptance and simplicity!

Strategy:!•  Inclusive simulation: 4π muons shooting!•  For each TT: counters of stubs detected in each module!

-  Inside layer: modules sorting by the number of stubs detected!§  For each layer: include modules in TT list following the

order and stop when the sum reaches a given threshold !•  Compute efficiency:!

-  Denominator: all tracks whose parameters fall inside the appropriate phase-space region!

-  Numerator: tracks that have at least 5(6) stubs in modules belonging to the TT in 5(6) different layers!

Page 19: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency: Barrel!

19!

Total number of modules260 280 300 320 340 360 380 400

Effic

ienc

y

0.7

0.75

0.8

0.85

0.9

0.95

1

1.05 > 3 GeV

T| < 10 cm, PzTT [4,2] - |V

Requiring 5 stubs

Requiring 6 stubs

> 3 GeVT

| < 10 cm, PzTT [4,2] - |V Example of inefficiencies: !

Thr values = {1., 0.99, 0.97, 0.95, 0.93}!

•  With 17% less modules, efficiency drop by few percent!

Page 20: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Connection per module – Threshold tradeoff!

20!

Number of TT connected0 1 2 3 4 5 6 7 8

Num

ber o

f mod

ules

1−10

1

10

210

310

410

> 3 GeVT

| < 15 cm , Pz

Distribution of TT connection for a module - |v

Thr = 1.00Thr = 0.99Thr = 0.97Thr = 0.95

> 3 GeVT

| < 15 cm , Pz

Distribution of TT connection for a module - |v

Number of TT connected0 1 2 3 4 5 6 7 8

Num

ber o

f mod

ules

1−10

1

10

210

310

410

> 3 GeVT

| < 10 cm , Pz

Distribution of TT connection for a module - |v

Thr = 1.00Thr = 0.99Thr = 0.97Thr = 0.95

> 3 GeVT

| < 10 cm , Pz

Distribution of TT connection for a module - |v

vz = [-15 cm, +15 cm]! vz = [-10 cm, +10 cm]!

•  The distribution remains essentially the same!•  Multiple connection can be avoided paying some acceptance!

Page 21: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

From Parameters to CSV file!

21!

•  PT threshold!•  vz acceptance!•  R*phi!•  R*eta!•  Single Muon sample!

INPUT! FULL!SIMULATION!

•  TT modules list!•  TT physical

boundaries on each layer!

•  Whole detector!•  Format: “.csv” file!

OUTPUT!

Current setup:!•  PT > 3 GeV!

•  vz = [-15 cm, +15 cm]!•  R*phi = 90 cm!•  R*eta = 60 cm!

•  20M Single Muon event (4π generation)!

Page 22: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Tracking trigger simulation!

•  Only for TT25: [4,2] (Old TT27)!•  Using current L1TT simulation code +

modification (https://github.com/ocerri/SLHCL1TrackTriggerSimulations)!•  Pattern bank generation!– Raw sample of 1G single muon!–  Stub cleaning and sample shrinking!– Pattern bank generation!

•  Performance check!– New vs Old bank size comparison!– Average number of roads in TTbar + PU140 events!– Efficiency and resolution!

22!

Page 23: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Training sample generation!

23!

Raw sample:!•  800M single muon events!•  Wider for future studies!

Stub Cleaner!&!

Shrinking!

StubCleaner.cc!

PB training sample:!•  About 134M muons!•  Strict TT25 definition!

Page 24: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Pattern bank generation!

24!

•  Pattern bank training sample effective size: 134M+66M = 200M events!•  Super-strips defined using full simulation boundaries!•  Generated for 6 different configurations:!

-  L5x2 or L5x2_L10x2!-  nz: 4, 6, 8!

Popularity!•  nz4: Very Good (about 15)!•  nz6: Good(more than 5)!•  nz8: Fine (more than 3)!

NEW OLDEv.Type PU SSConfig Banksize95% Meanroads road95% Banksize95% Diff Meanroads Diff road95% Diff SSConfig Banksize95% Popularity Banksize95% DiffTTbar 140 sf1_nz4_L5x2 1.40E+06 28.00 108.1 1.31E+06 6.8% sf1_nz4_L5x2 1.40E+06 13 1.31E+06 6.8%TTbar 140 sf1_nz6_L5x2 3.02E+06 22.85 89.08 2.85E+06 5.9% 22 3.9% 90.8 -1.9% sf1_nz6_L5x2 3.02E+06 6 2.85E+06 5.9%TTbar 140 sf1_nz8_L5x2 5.53E+06 21.19 85.31 4.95E+06 11.6% 20.6 2.9% 82.8 3.0% sf1_nz8_L5x2 5.53E+06 3 4.95E+06 11.6%TTbar 140 sf1_nz4_L5x2_L10x2 1.07E+06 29.40 115.3 1.00E+06 6.9% sf1_nz4_L5x2_L10x2 1.07E+06 18 1.00E+06 6.9%TTbar 140 sf1_nz6_L5x2_L10x2 2.31E+06 23.75 94.07 2.18E+06 5.8% 22.8 4.2% 93.2 0.9% sf1_nz6_L5x2_L10x2 2.31E+06 9 2.18E+06 5.8%TTbar 140 sf1_nz8_L5x2_L10x2 4.22E+06 21.96 91.86 3.77E+06 11.7% 21.1 4.1% 85.3 7.7% sf1_nz8_L5x2_L10x2 4.22E+06 5 3.77E+06 11.7%

12_AM_Sim_stats.txtTTbar 140 sf1_nz6_L5x2 3.28E+06 24.001503 92.08 xTTbar 140 sf1_nz6_L5x2_L10x2 2.45E+06 24.36628 94.94 xTTbar 140 sf1_nz8_L5x2_L10x2 4.74E+06 23.095787 97.07 xTTbar 140 sf1_nz8_L5x2 6.43E+06 23.12380952 92.08 xTTbar 140 sf1_nz4_L5x2_L10x2 1.10E+06 29.39839438 115.7 xTTbar 140 sf1_nz4_L5x2 1454700 27.99699097 108.1 x

13_AM_Sim.txtTTbar 140 sf1_nz4_L5x2 1398900 27.99699097 108.1TTbar 140 sf1_nz6_L5x2 3019700 22.85 89.08TTbar 140 sf1_nz8_L5x2 5528100 21.19 85.31TTbar 140 sf1_nz4_L5x2_L10x2 1070200 29.39839438 115.3TTbar 140 sf1_nz6_L5x2_L10x2 2305800 23.75 94.07TTbar 140 sf1_nz8_L5x2_L10x2 4215400 21.96 91.86

NEW OLD

Increase in PB size given by inconsistency fixing (backup for more infos)!

Page 25: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Average roads!

25!

# Roads per event 0.95 CL60 80 100 120 140 160 180 200

Bank

siz

e

610

710

Comparison between different super-strips configurations

sf1_nz4_L5x2

sf1_nz6_L5x2

sf1_nz8_L5x2

sf1_nz4_L5x2_L10x2

sf1_nz6_L5x2_L10x2

sf1_nz8_L5x2_L10x2

New TT: TTbar PU140sf1_nz4_L5x2 sf1_nz6_L5x2 sf1_nz8_L5x2 sf1_nz4_L5x2_L10x2 sf1_nz6_L5x2_L10x2 sf1_nz8_L5x2_L10x2

Old TT: TTbar PU140sf1_nz6_L5x2 sf1_nz8_L5x2 sf1_nz6_L5x2_L10x2 sf1_nz8_L5x2_L10x2

Comparison between different super-strips configurations

Old results from Status of Pattern Bank Optimization (2016-05-20 Update), Ristori et al. !

Page 26: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency performance!•  Goals!–  Test efficiency!–  Effective TT dimensions and turn-on near edges!!

•  Single Muons Test sample!–  Single muons but with delta rays!–  raw 100k events (effective 20k)!!

•  Denominator definition!–  Global: Tracks inside TT phase-space!–  Binned: TT bound removed in the scanned dimension!

•  e.g.: scanning ε(pT) denominator tracks must be inside TT phase-space in ϕ*, η* and vz, no cut pT is applied!

–  1 miss allowed: 5 out of 6 efficiency!!

26!

Page 27: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency vs PT!

27!

nz4_L5x2!

•  Sharp turn on!•  Average efficiency for PT>3 GeV

99.2±0.1 %!•  No significant differences for nz6

and nz8!

nz4_L5x2!

Page 28: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency vs ϕ*!

28!

•  Blind variable ϕ* (used to define TT)!

•  nz4 shown (no significant differences for nz6 and nz8)!

•  ϕ profile in agreement with expectations (see slide 12)!

•  Very sharp turn on!•  Average efficiency inside TT:

99.2±0.1 %!•  Null efficiency outside TT

borders (no duplicates)!

nz4_L5x2!

Page 29: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency vs η*!

29!

•  Early turn on, effective efficiency wider than definition!•  Average efficiency inside TT: 99.2±0.1 %!•  Turn on dependence from SS configuration!

nz4_L5x2!

Page 30: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Outside track roads matching!•  Particle outside TT definition

match roads:!–  Super strips are defined taking

the maximum range of interesting particles on TT!

–  A single training particle does not lay on the border of every layer!•  Outside particles can do that!!!

•  Pattern bank acceptance is broader than training sample!

•  Dependence from SS dimensions!–  Happens in ϕ too but it is far

smaller! 30!

Training sample!Roads matching!

Page 31: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency vs η* 6oo6!

31!

•  Sharper turn on w.t.r. to 5oo6!

•  Average efficiency inside TT: 90.8±0.3 %!-  PB 95% cut!-  Si efficiency = 1!

•  Module geometry effect!-  Efficiency drops!-  Slope towards high η!

!

Page 32: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Efficiency near borders!

32!

ϕ border :!TT25 = [4,2]!TT26 = [4,3]!TT24 same!

η border :!TT25 = [4,2]!TT17 = [3,2]!

TT33 in progress!No edge issues!!

nz4_L5x2!nz4_L5x2!

Page 33: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Conclusions !What has been done:!•  Study of a new definition of trigger towers !•  Optimization of the R* value!•  Efficiency – number of modules trade-off!•  Production of new module lists!•  Generate AM pattern banks for the new towers!•  Make the new towers and the new AM pattern

banks available to the full trigger simulation!•  Run the full simulation to evaluate new

performance parameters!–  Efficiency, Resolutions…!

!33!

Page 34: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Thank you all!!

Page 35: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

BACKUP!

Page 36: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

R*

beam line

z ranges

η* range

outside η* rangeoutside η* range

Vz range

Out TT track example!

36!

•  Tracks outside TT definitions may match roads if are near border because of SS finite dimensions!

•  Intrinsic duplicate generation!•  Less impact on 6 out of 6!

Page 37: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Resolution!

37!

nz8_L5x2!

Essentially unchanged!!

Page 38: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Focusing on R*ϕ!

38!

[cm]φR*60 70 80 90 100 110

Tota

l num

ber o

f con

nect

ion

5000550060006500700075008000850090009500

10000 - 3.0M sampleφ

Connection required for different R*

barrelintermediateendcapActual value = 58.89ηR*

- 3.0M sampleφ

Connection required for different R*

!•  Max optimization:!

-  4% (intermediate)!-  1% (forward)!-  5% (barrel)!

Page 39: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Module fan-out!

39!Number of TT connected

0 1 2 3 4 5 6 7 8

Num

ber o

f mod

ules

0

1000

2000

3000

4000

5000

6000

7000

8000

9000| < 7 cm

zModules connection, |V

> 2 GeVTP

> 3 GeVTP

| < 7 cmz

Modules connection, |V

Number of TT connected0 1 2 3 4 5 6 7 8

Num

ber o

f mod

ules

0

1000

2000

3000

4000

5000

6000

7000

8000

9000| < 10 cm

zModules connection, |V

> 2 GeVTP

> 3 GeVTP

| < 10 cmz

Modules connection, |V

Number of TT connected0 1 2 3 4 5 6 7 8

Num

ber o

f mod

ules

0

1000

2000

3000

4000

5000

6000

7000

8000

9000| < 15 cm

zModules connection, |V

> 2 GeVTP

> 3 GeVTP

| < 15 cmz

Modules connection, |V

Number of towers to which stubs from a single module must be delivered!

z = [-7cm, +7cm]! z = [-10cm, +10cm]! z = [-15cm, +15cm]!

Page 40: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Barrel example – TT[4,2]!

40!

Training sample!Acceptance!

Page 41: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Forward example – TT[6,2]!

41!

Training sample!Acceptance!

Page 42: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

How many modules?!

42!Trigger Tower number

0 5 10 15 20 25 30 35 40 45

Num

ber o

f mod

ules

0

100

200

300

400

500

600

700| < 7 cm

zModules per tower, |V

> 2 GeVTP

> 3 GeVTP

| < 7 cmz

Modules per tower, |V

Trigger Tower number0 5 10 15 20 25 30 35 40 45

Num

ber o

f mod

ules

0

100

200

300

400

500

600

700| < 10 cm

zModules per tower, |V

> 2 GeVTP

> 3 GeVTP

| < 10 cmz

Modules per tower, |V

Trigger Tower number0 5 10 15 20 25 30 35 40 45

Num

ber o

f mod

ules

0

100

200

300

400

500

600

700| < 15 cm

zModules per tower, |V

> 2 GeVTP

> 3 GeVTP

| < 15 cmz

Modules per tower, |V

Total number of modules from which each tower must receive information (2GeV vs. 3 GeV)!

z = [-7cm, +7cm]! z = [-10cm, +10cm]! z = [-15cm, +15cm]!

Page 43: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

Triple shared modules!

43!

•  Less than 1% triple sharing!

•  Order 4% 4-sharing!

•  16 6-time shared modules only with |vz| up to 15 cm!

Page 44: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

q/PT vs ϕ summary plot!

44!

q

PT=

2↵

R⇤ sin��0 � �⇤

edge

�Equation of boundary:!

R⇤ = 58.89cm↵ = ⇢/PT = 87.72cm/GeV

Overcoverage possibly due to finite module dimensions?!

Page 45: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

z0vs. η summary plot!

45!

Page 46: CMS Track Trigger: Tower definition and optimization · • Assign one tower to each region!! • Define 48 “training samples”, one per tower! – Use single muon sample ! •

How many modules?!

46!Trigger Tower number0 5 10 15 20 25 30 35 40 45

Num

ber o

f mod

ules

0

100

200

300

400

500

600

700total connections

direct connections

> 3 GeVT

| < 7 cm, Pz

Modules per TT, |V

Trigger Tower number0 5 10 15 20 25 30 35 40 45

Num

ber o

f mod

ules

0

100

200

300

400

500

600

700total connections

direct connections

> 3 GeVT

| < 10 cm, Pz

Modules per TT, |V

Trigger Tower number0 5 10 15 20 25 30 35 40 45

Num

ber o

f mod

ules

0

100

200

300

400

500

600

700total connections

direct connections

> 3 GeVT

| < 15 cm, Pz

Modules per TT, |V

•  Dark area: modules directly connected to the TT!•  Light area: modules connected to the TT via TT2TT connections!•  Solid line: total number of modules connected!•  3 GeV/c PT!

z = [-7cm, +7cm]! z = [-10cm, +10cm]! z = [-15cm, +15cm]!