ITTF “Re-View” Session,August 11, 2003

Manuel Calderón de la Barca Sánchez

ITTF Evaluation for Spectra

ITTF Evaluation for Spectra

2

Eta Distributions

3

Eta Ratio (ITTF/TPT)

4

Pt Distribution

5

Pt Ratio (ITTF/TPT)

6

East & West vs run number

7

Looking at log files For some events

No tracks are found on the eastNext event, no tracks are found on the west…For the same event, numbers are comparable:

TPT ITTF

Good globals 1212 1353

H+ East 136 132

H- East 158 148

H+ west 96 0

H- west 87 0

Next event has nothing in the west… then maybeagain in the east… Has to be a bug!

8

Hit and Tracking Data set used:

Hijing b<3 simulations Usually, absolute value of efficiency is too

ideal … comparisons between current code & IT

From loose to tight cutsLook at midrapidity (|eta|<0.5) mainlyAccepted MC tracks == 10 MC Hits at leastReconstructed track cuts:

Fit Points >= 10, no dca cut (3 cm for primaries)

Fit Points >= 24, dca < 1cm

9

Fit Points, Then and Now

Cuts:Central HijingGlobal dca<1,Fit Pts>=10

Integral normalized to 1

10

What’s the deal? Efficiency vs pT

Here, efficiency is:

Found & MatchedMC Accepted

June Review Aug. 6 Production

“Loose cut” data set

Tuning effort by our Wayne guys!! Note: some CVS glitch probably happened, as I’ve seen better numbers (Andrew).

11

…tighter dca and tighter fit points

Cuts like thoseused in identifiedspectra papers

June Review Aug. 6 Production

12

Efficiency vs eta, tight cuts

Cuts like thoseused in identifiedspectra papers

Asymmetry, wasn’tthere before…

13

Eta efficiency, loose cuts

Zbigniew sees thesame with loose cuts.

14

What’s happening? Distribution

Need to mask sectors properly

15

Efficiency and Bias

Again:Current best tune was not used for this production.

From Zbigniew,Bias and pullswere better before.Note scale.

16

pt Resolution

17

Curvature and tan() pulls.

18

Snapshot

Proper tuning of tracking parameters has led to improvements (Andrew). Efficiency improved

The best tune was not used for the Hijing production

Masking of sectors needs to be addressed No hardcoding of time-stamps (integration into BFC).

Energy loss calculation needs to be debugged for final tuning of bias.

Must have a consistent parameter set for the production that we all use. Need to finalize and commit BEST parameter set to the

library, which gives the performance we always advertised.