RP Trigger studies L. Grzanka; J. Proch azka 9th March 2010 L. - - PowerPoint PPT Presentation

rp trigger studies
SMART_READER_LITE
LIVE PREVIEW

RP Trigger studies L. Grzanka; J. Proch azka 9th March 2010 L. - - PowerPoint PPT Presentation

RP Trigger studies L. Grzanka; J. Proch azka 9th March 2010 L. Grzanka; J. Proch azka RP Trigger studies 9th March 2010 1 / 15 Talk Summary 1 CC Hardware 2 CC Simulation 3 CC properties: ideal vs. real logic 4 Testbeam data samples 5


slide-1
SLIDE 1

RP Trigger studies

  • L. Grzanka; J. Proch´

azka 9th March 2010

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 1 / 15

slide-2
SLIDE 2

Talk Summary

1 CC Hardware 2 CC Simulation 3 CC properties: ideal vs. real logic 4 Testbeam data samples 5 Physics

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 2 / 15

slide-3
SLIDE 3
  • 1. CC Hardware

Data input: trigger outputs of 20 VFATs (RP case) Data output: dedicated trigger VFAT (RP: 1 VFAT per 2 CC) Data flow diagram:

READOUT

CC CC

strip bits trigger bits 1 detector 4 VFAT s VFAT Trigger CC

Connector TRIGGER Monitor SECTOR Output VFAT Ch Channel ODD Planes 1 GOH4-Data9 A16 72 70 2 GOH4-Data10 A15 76 74 3 GOH4-Data11 A14 80 78 4 GOH4-Data12 A13 84 82 5 GOH4-Data13 A12 88 86 6 GOH4-Data14 A11 92 90 7 GOH4-Data15 A10 96 94 8 GOH4-Data16 A9 100 98 9 GOH4-Data1 A24 40 38 10 GOH4-Data2 A23 44 42 11 GOH4-Data3 A22 48 46 12 GOH4-Data4 A21 52 50 13 GOH4-Data5 A20 56 54 14 GOH4-Data6 A19 60 58 15 GOH4-Data7 A18 64 62 16 GOH4-Data8 A17 68 66 EVEN Planes 1 GOH5-Data9 B23 42 40 2 GOH5-Data10 B22 46 42 3 GOH5-Data11 B21 50 48 4 GOH5-Data12 B20 54 52 5 GOH5-Data13 B19 58 56 6 GOH5-Data14 B18 62 60 7 GOH5-Data15 B17 66 64 8 GOH5-Data16 B16 70 68 9 GOH5-Data1 A8 104 102 10 GOH5-Data2 A7 108 106 11 GOH5-Data3 A6 112 110 12 GOH5-Data4 A5 116 114 13 GOH5-Data5 A4 120 118 14 GOH5-Data6 A3 124 122 15 GOH5-Data7 A2 128 126 16 GOH5-Data8 B24 38 36

Mapping between CC outputs and trigger VFAT !

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 3 / 15

slide-4
SLIDE 4
  • 2. CC Software

L1TriggerTotem:CoincidenceChip — library implementing CC logic and few plugins DataFormats:TotemL1Trigger — RPCCBits (+RPCCId), T2TriggerBits, T1TriggerBits From where CCBits information comes from ? Simulation: RPCoincidenceProducer, T2CoincidenceProducer Testbeam data: RawToDigi module

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 4 / 15

slide-5
SLIDE 5
  • 3. CC Properties

TOTEM Experiment COINCIDENCE CHIP SPECIFICATION

TOTEM Project Document No: Institute Document No. Created: 28/04/05 Page: 1 of 33

CC

EDMS id Modified: 29/03/2007

  • Rev. No.: 3

Important blocks: V out of NP, W out of NP (neighbours) Bug in CC (number of planes) — see following example

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 5 / 15

slide-6
SLIDE 6
  • 3. CC Properties - Or 1 bug

Ideal (old documentation) logic:

After V out of NP Sectors 12345678

  • Coinc. 1111111111111111

After And/Or Sectors 12345678 Coinc. 111111111 After W out of NP Sectors 12345678 Coinc. 111111111 After Z out of 16 or 8 Sectors 12345678 Coinc. After And/Or 2 Sectors 12345678 Coinc. 111111111 After Or 2 = OUTPUT Sectors 12345678 Coinc. 111111111 INPUT Sectors 1 2 3 4 5 6 7 812345678 Plane 1 1 Plane 2 1 Plane 3 1 Plane 4 1 Plane 5 1 After Or1 Sectors 1 2 3 4 5 678 Plane 1 1 1 1 11 11 Plane 2 1 1 1 11 11 Plane 3 1 11 111111 Plane 4 1 11 111111 Plane 5 111111111

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 6 / 15

slide-7
SLIDE 7
  • 3. CC Properties - Or 1 bug

Real (new documentation) logic:

After V out of NP Sectors 12345678 Coinc. 1 1 1 After And/Or Sectors 12345678 Coinc. 11111 After W out of NP Sectors 12345678 Coinc. 11111 After Z out of 16 or 8 Sectors 12345678 Coinc. After And/Or 2 Sectors 12345678 Coinc. 11111 After Or 2 = OUTPUT Sectors 12345678 Coinc. 11111 After Or1 Sectors 1 2 3 4 5 6 7 8 Plane 1A 1 1 1 1 1 1 1 Plane 1B Plane 2A 1 1 1 1 1 1 1 Plane 2B Plane 3A 1 1 1 1 1 1 Plane 3B Plane 4A 1 1 1 1 1 1 Plane 4B Plane 5A Plane 5B 1 1 1 1 1 1 1 INPUT Sectors 1 2 3 4 5 6 7 812345678 Plane 1 1 Plane 2 1 Plane 3 1 Plane 4 1 Plane 5 1 Before W out of NP Sectors 1 2 3 4 5 6 7 812345678 Plane 1 1 1 1 1 1 1 1 Plane 2 1 1 1 1 1 1 1 Plane 3 1 1 1 1 1 1 Plane 4 1 1 1 1 1 1 Plane 5 1111111

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 7 / 15

slide-8
SLIDE 8
  • 3. CC Properties - Z bug

Designed (old documentation) logic:

After V out of NP Sectors 12345678 Coinc. 1 1 1 1 After And/Or Sectors 12345678 Coinc. 1 1 1 1 After W out of NP Sectors 12345678

  • Coinc. 1111111111111111

After Z out of 16 or 8 Sectors 12345678 Coinc. After And/Or 2 Sectors 12345678 Coinc. 1 1 1 1 After Or 2 = OUTPUT Sectors 12345678 Coinc. 1 1 1 1 INPUT Sectors 1 2 3 4 5 6 7 8 Plane 1 1 Plane 2 Plane 3 1 Plane 4 Plane 5 1 Plane 6 Plane 7 1 Plane 8 Plane 9 Plane 10 1 After Or1 Sectors 1 2 3 4 5 6 7 8 Plane 1 1 Plane 2 Plane 3 1 Plane 4 Plane 5 1 Plane 6 Plane 7 1 Plane 8 Plane 9 Plane 10 1

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 8 / 15

slide-9
SLIDE 9
  • 3. CC Properties - Z bug

Real (new documentation) logic:

After V out of NP Sectors 12345678 Coinc. 1 1 1 1 After And/Or Sectors 12345678 Coinc. 1 1 1 1 After W out of NP Sectors 12345678

  • Coinc. 1111111111111111

After Z out of 16 or 8 Sectors 12345678

  • Coinc. 1111111111111111

After And/Or 2 Sectors 12345678 Coinc. After Or 2 = OUTPUT Sectors 12345678 Coinc. INPUT Sectors 1 2 3 4 5 6 7 8 Plane 1 1 Plane 2 Plane 3 1 Plane 4 Plane 5 1 Plane 6 Plane 7 1 Plane 8 Plane 9 Plane 10 1 After Or1 Sectors 1 2 3 4 5 678 Plane 1 1 1 Plane 2 Plane 3 1 Plane 4 Plane 5 1 1

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 9 / 15

slide-10
SLIDE 10
  • 4. Testbeam data

Summary of testbeam data POT9 ... POT12 Stored in /data2/totem/RPtest

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 10 / 15

slide-11
SLIDE 11
  • 4. Testbeam in H8

POT/CC events Nt

TMraw Nt TMsimu Nt TMnotTheSame Nt

9A 16784 9479 0.99 0.99 0.02 9B 10898 5992 0.99 0.99 0.02 10A 3344 1350 0.94 0.99 0.03 10B(vth=15) 3676 1458 0.96 0.99 0.03 10B(vth=10) 3338 1334 0.96 0.99 0.02 11A 5141 2220 0.99 0.99 0.01 12A 11904 7045 0.99 0.99 0.01

CC Settings: A: 3 18 240 136 128; 2 planes, no neighbors, falling edge B: 3 18 240 136 0; 2 planes, no neighbors, rising edge Nt - RECO tracks; 3 planes in U and V (no difference if 2 planes) TMraw output of trigger vfat if at least one bit ON/CC TMsimu simulated output of trigger vfat (if at least one bit ON/CC) based on sectors selected by the RecoTrack and CC settings TMnotTheSame different pattern CCs-raw vs. CCs-simu For all pots: if VFAT output = 0 (”empty events”, no hit in a pot) then TM gives also 0 (no trigger)

slide-12
SLIDE 12
  • 5. Physics - ”delta sectors”

5 planes (U or V orientation); each detector divided into 16 sectors ∆S difference between ON sectors in 1th and last plane

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 12 / 15

slide-13
SLIDE 13

Figure: Simu ES; β∗ = 2.5m; E = 3.5TeV; one RP (120); only if we are able to

reconstruct a track

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 13 / 15

slide-14
SLIDE 14

Figure: Simu ES; β∗ = 2.5m; E = 3.5TeV; one RP (120); only if we are able to

reconstruct a track

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 14 / 15

slide-15
SLIDE 15

What next?

Simulate the full CC chain with the same CC settings and with ES or SD protons generated at IP

  • L. Grzanka; J. Proch´

azka RP Trigger studies 9th March 2010 15 / 15