GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 1/31 Overview of End to End Runs Eduardo do Couto...

GLAST LAT Project Apr 1, 2005

E. do Couto e Silva 1/31

Overview of End to End RunsOverview of End to End Runs

Eduardo do Couto e Silva

April 1, 2005

( not it is not a joke, we finally took data!)



Overview of End to End RunsOverview of End to End Runs

• We successfully completed all end to end runs for Tower A

• The infrastructure for data analysis is in place and working well– All plots in this presentation were obtained from the SVAC

reports which are automatically generated at the end of the runs

– Please use them and give us feedback

• Two tower tests will occur in 1 to 2 weeks– We need to look at these data to provide inputs to the test

plan



Retrieving end to end runsRetrieving end to end runs

• Go to the Runs database• To get all runs Query on

– Script name: end2end– Completion Status: PASSED – Duration: > 100

– Bear in mind that Americium runs are 1 min long !

• Look at Config report and digi and recon reports– Currently we are updating the reports based on the results

from these runs– Comments are welcome

– Please come to our Friday meetings if you want to participate



Retrieving Runs from the DatabaseRetrieving Runs from the Database

Can select only one test ID

For all runs fill the fieldsthe red boxes



Results from Database…Results from Database…Data Quality Reports

TEST ID

SerialNumber



Run Numbers (1)Run Numbers (1)

Run ID Events TimeTrigger

Rate Errors DescriptionTEM Diag

1 1 135000894 156761 3601 43.5 8 Baseline all settings nominal (as in flight) OFF3 Baseline all settings nominal (as in flight) ON

2 3 135000896 157894 3601 43.8 9 Change only TKR DAC to 22 ON6 135000898 156809 3601 43.5 27 Read TKR from Right RC ON7 135000900 157225 3601 43.7 20 Read TKR from Left RC ON

3 1 135000902 155737 3601 43.2 7 Only TKR is allowed to open trigger window ON2 135000904 1652 3606 0.5 3 Only CAL_LO set to 20 MeV is allowed to open window ON

4 1 135000909 191588 3601 53.2 8 Overlay rate of 1 kHz ON2 135000915 172201 3601 47.8 9 Overlay rate of 5 kHz ON3 135000918 154559 3601 42.9 10 Overlay rate of 10 kHz ON4 135000931 126848 3601 35.2 10 Overlay rate of 20 kHz ON5 135001024 333081 64 5204.4 0 Americium Source ON6 135000990 328933 303 1085.6 0 only allowed trigger is the pulse generator at 1 kHZ ON

5 3 135000921 124945 3601 34.7 9 Overlay rate of 10 kHz and change only TKR DAC to 22 ON6 135000924 122336 3601 34.0 17 Overlay rate of 10 kHz and and read TKR from Right RC ON7 135000926 121710 3601 33.8 Overlay rate of 10 kHz and read TKR from Left RC ON

7 1 135000906 143123 3268 43.8 8 Zero suppression OFF ON

8 6 135000911 54094 1740 31.1 4 Overlay rate of 1kHz, CAL 4 range, Zero Suppression OFF ON6 135000912 54096 1740 31.1 2 Overlay rate of 1kHz, CAL 4 range, Zero Suppression OFF ON6 135000913 3728 124 30.1 0 Overlay rate of 1kHz, CAL 4 range, Zero Suppression OFF ON8 135000929 23826 3601 6.6 3 Overlay rate of 10kHz, CAL 4 range, Zero Suppression OFF ON

E2E ID

There are more runs with ID’s 4/5 and 4/6



Run Numbers (1)Run Numbers (1)8 6

9 1 135000945 142867 1565 91.3 751 VDG ON , nominal settings, Zero Suppression OFF OFF1 135000946 141370 1395 101.3 672 VDG ON , nominal settings, Zero Suppression OFF OFF1 135000947 57604 644 89.4 268 VDG ON , nominal settings, Zero Suppression OFF OFF2 135000949 284100 3601 78.9 1259 VDG ON , nominal settings, target at 2.5 cm from top of TKR ON3 135000965 291875 3601 81.1 2453 VDG ON , nominal settings, target at 5.1 cm from top of TKR ON4 135000968 234146 3601 65.0 2153 VDG ON , nominal settings, target at 7.6 cm from top of TKR ON5 135000951 298603 3601 82.9 1435 VDG ON , nominal settings, overlay 1 kHz ON6 135000956 288953 3601 80.2 1628 VDG ON , nominal settings, overlay 10 kHz ON7 135000971 138953 3601 38.6 18 VDG ON , nominal settings, shoot from angle below top layer of CAL ON8 135000975 170160 3601 47.3 3056 VDG ON , nominal settings, shoot from angle 10 cm above bottom of TKR ON

B 1 135000933 314677 7201 43.7 17 all settings nominal, with Mu telescope, OFF9 135000935 288470 6594 43.7 18 CAL High Energy muon gain, four range readout with Mu telescope ON9 135000936 26942 609 44.2 1 CAL High Energy muon gain, four range readout with Mu telescope ON

11 135000954 101573 3601 28.2 1312 135000938 54031 1273 42.4 6 Zero suppression OFF, four range readout with Mu telescope ON12 135000939 54033 1274 42.4 1 Zero suppression OFF, four range readout with Mu telescope ON12 135000940 44508 1056 42.1 3 Zero suppression OFF, four range readout with Mu telescope ON16 135000958 314930 3028 104.0 1652 VDG ON ON16 135000959 316850 3060 103.5 1600 VDG ON, all settings nominal ON16 135000960 314930 3067 102.7 1830 VDG ON, all settings nominal ON16 135000961 311027 3181 97.8 2276 VDG ON, all settings nominal ON16 135000962 190878 2070 92.2 1483 VDG ON, all settings nominal ON

Run ID Events TimeTrigger

Rate Errors DescriptionTEM Diag

8 6

E2E ID



Event Trigger Rate for Tower A 43

.5

43.8

43.5

43.7

43.2

0.5

53.2

47.8

42.9

35.2

5204

.410

85.6

34.7

34.0

33.8 43

.8

31.1

31.1

30.1

6.6

91.3

101.

389

.478

.981

.165

.0 82.9

80.2

38.6 47

.3

43.7

43.7

44.2

28.2 42

.442

.442

.110

4.0

103.

510

2.7

97.8

92.2

0

1

10

100

1000

10000

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

Rat

e (H

z)

Event Trigger RateEvent Trigger Rate

CAL_LO only

Am241

VDG1

kHz

5 kH

z10

kH

z20

kH

z

1 kHz

Ho

rizo

nta

co

smic

sl

4 rangeZero Sup OFF

10 KHz

10 kHz

VDG

Rates agree to expectations



Number of Error Events for Tower A 8 9

2720

73

8 9 10 100 0

917

8

42

03

751

672

268

1259 24

5321

5314

3516

2818

3056

17 181

136

13

1652

1600

1830

2276

1483

0

1

10

100

1000

10000

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

Nu

mb

er o

f E

rro

r E

ven

ts

Error Events for Tower AError Events for Tower A

Rea

d T

KR

fro

m

on

e si

de

on

ly

So far we found no packet nor parity errors.Only TEM errors were found VDG VDG



Number of Events for Tower A 15

6761

1578

9415

6809

1572

25

1557

3716

52

1915

8817

2201

1545

5912

6848

3330

8132

8933

1249

4512

2336

1217

10 1431

23

5409

454

096

3728

2382

6

1428

6714

1370

5760

428

4100

2918

7523

4146

2986

0328

8953

1389

5317

0160

3146

7728

8470

2694

210

1573

5403

154

033

4450

831

4930

3168

5031

4930

3110

2719

0878

0

50000

100000

150000

200000

250000

300000

350000

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

Nu

mb

er o

f ev

ents

Number of Events for Tower ANumber of Events for Tower A

Am241

CA

L_

LO

on

ly

4 rangeZ. Sup OFF

VDG

2 hour runs VDG



Event sizes for Tower A

308

339

334

333

337 44

4

334

335

332

331

318

303

336

334

336

711

1861

1861

1885

1848

697

705

1729

317

323

322

316

319

317 37

0

310 36

035

434

118

6318

6318

6131

631

431

632

032

4

0

200

400

600

800

1000

1200

1400

1600

1800

2000

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

Eve

nt

Siz

e (B

ytes

)

Event Size for Tower A (bytes)Event Size for Tower A (bytes)

Z.

Su

p O

FF

4 range Z. Sup OFF

4 range Z. Sup OFF

CA

L_

LO

on

ly

VDGZ sup OFF

For Cosmic rays expected about 300 bytes, CAL 4 range, TEM diag ON, Z Sup ON 200 bytes, CAL 1 range, TEM diag OFF, Z Sup ON

1700 bytes, CAL 4 range, TEM diag ON, Z Sup OFF

VDGZ sup ON



Raw File sizes for Tower A

46

51 50 50 500.

7

6155

4940

101

95

40 39 39

97 96 966.

742

95 95 9586

9072

90 8842

60

9399

9.1

3396 96

7995 95 95 95

59

0

20

40

60

80

100

120

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

File

Siz

e (M

Byt

es)

Size of Raw FITS fileSize of Raw FITS file

2 hour runsVDG

Am241

Z. Sup OFF Z. Sup OFF

Every file is below 100 Mbytes, for 2 towers we want to raise the limit to 200 Mbytes



Digi File sizes for Tower A

60 64 64 61 630.

9

6761

5546

5967

53 52 49

177

120

120

8.3

53

165

165

165

8691

7593 91

4769

121

123

1134 34

123

101

94 95 95 9659

0

20

40

60

80

100

120

140

160

180

200

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

File

Siz

e (M

Byt

es)

Digi File Size (Mbytes)Digi File Size (Mbytes)

Zero SupOFF

Zero SupOFF



Recon File sizes for Tower A

1.4

1.4

1.4

1.4

1.4

0.1

1.3

1.2

1.1

0.9

0.9

0.9

1.1

1.1

1.1

1.3

0.7

0.7

0.0

0.2

0.4

0.6

0.8

1.0

1.2

1.4

1.6

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

File

Siz

e (G

Byt

es)

Recon File Size (GBytes)Recon File Size (GBytes)

Dig

i ti

me

d o

ut

in p

ipe

lin

e

4 r

an

ge

ha

s

a

bu

g i

n r

ec

on

(fix

ed

on

th

e

ne

xt

rele

se

as

e)

4 range has a bug in recon

(fixed on the next relesease)

Am241 and Some VDG runs

Not availableprior to this talk

Pipeline had a recon limit of 1.8 Gbytes in jobOptions (left over from the times when we did not have ROOT 4) and some jobs failed. We also believe we need a faster turn around on processing of recon files, maybe for 2 tower tests we need to try the special queue deal with SCS



Ratio of Digi/Raw Ratio of Digi/Raw

Ratios of Digi/Raw File sizes for Tower A

1.30

1.25 1.28

1.22 1.26 1.29

1.10

1.11

1.12 1.15

0.58

0.71

1.33

1.33

1.26

1.82

1.25

1.25

1.24 1.26

1.74

1.74

1.74

1.00

1.01 1.04

1.03

1.03 1.

12 1.15

1.30

1.24

1.21

1.03

0.35

1.28

1.28

0.99

1.00

0.93

0.73

0.71

0.1

0.3

0.5

0.7

0.9

1.1

1.3

1.5

1.7

1.9

2.1

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

I am sure Heather will have fun looking into these differences….



Ratio Recon/Digi File sizes for Tower A

23.9

22.4

22.4 23

.5

22.8

11.4

19.9

20.1

20.5

20.0 21

.321

.7 23.0

7.5 8.

3

15.3

0

5

10

15

20

25

30

1350

0089

4

1350

0089

613

5000

898

1350

0090

0

1350

0090

213

5000

904

1350

0090

913

5000

915

1350

0091

813

5000

931

1350

0102

413

5000

990

1350

0092

113

5000

924

1350

0092

6

1350

0090

6

1350

0091

113

5000

912

1350

0091

313

5000

929

1350

0094

513

5000

946

1350

0094

713

5000

949

1350

0096

513

5000

968

1350

0095

113

5000

956

1350

0097

113

5000

975

1350

0093

313

5000

935

1350

0093

613

5000

954

1350

0093

813

5000

939

1350

0094

013

5000

958

1350

0095

913

5000

960

1350

0096

113

5000

962

Run ID

Ratio of Recon/Digi fileRatio of Recon/Digi file

Now Heather will have a blast….It deserves some investigation…

Zero Suppression ON

Ze

ro S

up

pre

ss

ion

OF

F



Baseline Run 135000894, ID 1/1 : GEM TriggersBaseline Run 135000894, ID 1/1 : GEM Triggers

TKR ~ DAC 30

CAL_LO ~ 100 MeV (rate agrees with expected rate when only CAL_LO is turned on see ID 3/1)

TKR + CAL_LO

CAL_HI ~ 1 GeV (what are these events?)

TKR + CAL_HI

TKR + CAL_LO

Can we have a “pure” CAL_HI without a CAL_LO?



CAL_HI Trigger: Run 135000894 event 53946CAL_HI Trigger: Run 135000894 event 53946

Didn’t trigger the tracker with 14 clusters associated

with a track?!!!CalEnergySum = 25 MeV




Triggered CAL_HI with 24 MeV? CalEnergySum = 24 MeV



CAL_HI Trigger: Run 135000894 event 7602 CAL_HI Trigger: Run 135000894 event 7602

CalEnergySum = 44 MeV




CalEnergySum = 143 MeV




Didn’t trigger the tracker with 14 clusters associated

with a track?!!!CalEnergySum = 56 MeV



External Pulser @ 1 KHz Run 135000909, ID 4/1: GEM TriggersExternal Pulser @ 1 KHz Run 135000909, ID 4/1: GEM Triggers

TKR ~ DAC 30

CAL_LO ~ 100 MeV

TKR + CAL_LO

CAL_HI ~ 1 GeV

TKR + CAL_HI

TKR + CAL_LO

We will modify SVAC reports to have better resolution on plots

External triggers (last bit) from pulse generator

External + software triggers



Runs with different TKR thresholdsRuns with different TKR thresholds

Run 135000894, ID 1/1, Run 135000894, ID 1/1, LOWLOW Threshold ThresholdTKR DAC ~ 30TKR DAC ~ 30

Run 135000896, ID 2/3, Run 135000896, ID 2/3, NOMINALNOMINAL threshold threshold

TKR DAC ~ 22TKR DAC ~ 22

Fraction of events with Strip hits but TOT = 0Fraction of events with Strip hits but TOT = 0Fraction of events with Strip hits but TOT = 0Fraction of events with Strip hits but TOT = 0



TKR readout from one side only: Average TOTTKR readout from one side only: Average TOT

Only LO/Left side cables are read out

Only HI/Right side cables are read outOnly HI/Right side cables are read out

Run 135000898, ID 2/6Run 135000898, ID 2/6

Run 135000900, ID 2/7Run 135000900, ID 2/7

Note that the color patternis remarkably similar for

both runs

Units of counts1 count = 200 ns



Lower TKR thresholds : Number of hit planesLower TKR thresholds : Number of hit planes

0.22%< 6 planes

0.07%< 6 planes

Run 135000894, ID 1/1, TKR DAC ~ 30Run 135000894, ID 1/1, TKR DAC ~ 30

Run 135000896, ID 2/3, TKR DAC ~ 22Run 135000896, ID 2/3, TKR DAC ~ 22



High Rate RunsHigh Rate Runs

Am241 (TKR and CAL are allowed to trigger)

Only the pulse generator Is allowed to trigger (1 kHz)

Run 135001024, ID 4/5Run 135001024, ID 4/5

Run 135000990, ID 4/6Run 135000990, ID 4/6



GEM Time Interval : High Rate RunsGEM Time Interval : High Rate Runs

Run 135001024, ID 4/5Run 135001024, ID 4/5 Run 135000990, ID 4/6Run 135000990, ID 4/6

Run 135000909, ID 4/1Run 135000909, ID 4/1Run 135000915, ID 4/2Run 135000915, ID 4/2

Am241 @ 5 kHz(TKR and CAL are allowed to trigger)

Only the pulse generator

Is allowed to trigger (1 kHz)

TKR and the pulse generator are allowed to trigger (1 kHz)

TKR, CAL and the pulse generator are allowed to trigger (5 kHz)



VDG RunsVDG Runs

Tower boundary

Reconstructed XY positions

Fraction of events with 0 hits(red means 0 events)

Very few events make into the thick layers

~ 80% of events have at least one track

Run 135000946, ID 9/1Run 135000946, ID 9/1Trigger rate ~ 100 HzTrigger rate ~ 100 Hz



High Priority “Projects”High Priority “Projects”

• Demonstrate that the pulse generator works as expected.– Do we have all the configurations we need to understand the

behavior at high rates? – Should we lower the CAL LAC threshold (for one column) to load

the CAL with data and allow a fair comparison of deadtime?• Do files sizes and deadtime make sense for the possible permutations

of the main register configurations?– (1/4) CAL range readout, zero suppression (ON/OFF), TEM

diagnostics (ON/OFF)• Are there differences in distributions that could be ascribed to

different timing when reading out only from LO or HI side of TKR cables?– Of course use baseline as a reference

• Are there idiosyncrasies in the Error events?– Need to explore in electronics and physical space

• Need to study topologies and rates of different trigger types– As many runs as possible

• More ideas?– Volunteers?



SummarySummary

• This week we all made an spectacular progress !– Thank you all

• Today we will change the code in the pipeline (bug fixes) – We will reprocess all runs

• Depending on your analysis you do not need to wait for the pipeline– Go ahead and adopt a run

• Please let me know how you want to contribute for the data analysis– We need to plan quickly for the two tower tests that will

happen in 1 to 2 weeks

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 1/31 Overview of End to End Runs Eduardo do Couto...

Documents

Transcript of GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 1/31 Overview of End to End Runs Eduardo do Couto...