---------------------------------------------------------------------------

Tracking efficiencies from Mike/Boris (1)

> tight track is:
> track +  dca <0.02cm +  chi2<4 + #smthit>0.
>
> We loose 10% of efficiency because of  the SMT acceptance.
>
> >>in this talk is presentend "loose_track" efficiency.
> >>what is called "loose_track" corresponds to a cut on the dca of the track.
> >>This lower the efficiency by ~1.5 with respect to overall tracking 
> >>efficiency.
> >>
> >>-track_loose efficiency (as on the plots)  93.8% -track_loose with 
> >>restriction  eta<1.5 : 96.5%
> >>
> >>-track efficiency  95.2%
> >>-track with restriction eta<1.5: 97.8%
> >>
> >>I think the plots will give you this 96.5% if you properly convolute 
> >>it with the muon eta distribution.
> >>
> >>cheers
> >>Boris
> >>
> >>>However, in the plots from your talk as a function of eta, in the 
> >>>regions eta<1.5 it still looks like loose muons are closer to 95% 
> >>>and tight muons between 75 and 90%.
> >>>

 ---------------------------------------------------------------------------

Muon ID Efficiencies (Boris, mu_plots.tgz)

  Hi,
  attached is a bunch of files with the two efficiencies (Look at .ps file,
  here also the various jpg,eps and even a  root file to redo everything.)
  I provided

    -muid loose efficiency
    -tracking efficiency.

  with respect to what you demand, the plot "Loose muon ID efficiency vs 
    eta (track match required)"  is missing, but I understand it is the 
    product of the  two other plots.

cheers
Boris

 ---------------------------------------------------------------------------

Electron ID efficiencies

>>  Z->ee Loose electron efficiency vs. eta (no track match) - Christian 
Version: 2
Quality: Loose_notrk
Isolation: 0.2
EMFraction: 0.9
pT: 3
HMx8: 75 (is for CC quasi identical with HMx7CC: 50 which we use for the scale corrections)

in

/home/schwanen/emid/public_results_p18.05.00/results_for_CERN/loose_notrk/data/hTotalEff_DetEta_hmx8_bkgSub.eps
/home/schwanen/emid/public_results_p18.05.00/results_for_CERN/loose_notrk/mc/hTotalEff_DetEta_hmx8_bkgSub.eps
/home/schwanen/emid/public_results_p18.05.00/results_for_CERN/loose_notrk/data_mc/hTotalEff_DetEta_hmx8_bkgSub.eps

>>  Z->ee Loose electron efficiency vs. eta (track match)    - Christian S
Version: 2
Quality: Loose_trk
Isolation: 0.2
EMFraction: 0.9
pT: 3
LHood: 0.2

in

/home/schwanen/emid/public_results_p18.05.00/results_for_CERN/loose_trk/data/hTotalEff_DetEta_bkgSub.eps
/home/schwanen/emid/public_results_p18.05.00/results_for_CERN/loose_trk/mc/hTotalEff_DetEta_bkgSub.eps
/home/schwanen/emid/public_results_p18.05.00/results_for_CERN/loose_trk/data_mc/hTotalEff_DetEta_bkgSub.eps

 ---------------------------------------------------------------------------

Momentum resolution (Mike S)

> 	I have attached a plot of the momentum resolution
> from the TDR as a function of eta.  This has been measured in
> the data at only one point that I know of (I also know how to 
> do it at other points, but haven't), and it was within a 
> factor of 2 of the TDR.  The resolution is parameterized as 
> sigma_pt/pt = sqrt(0.015^2 + (0.0014 pT)^2)
> 

 ---------------------------------------------------------------------------

Electron energy resolution (Jan)

The fractional energy resolution for electrons from Z -> e e at normal
incidence on the CC [is_fiducial()] is 3.7 %. This corresponds to an average
over some energy spectrum given by nature. The spectrum spikes at 46 GeV. As we
stay in the CC, but go to eta = 0.7 , the fractional energy resolution degrades
to 4.8 %, despite the fact that the energy spectrum now spikes at 52 GeV (which
is higher than 46 GeV).

The uncertainties on the resolutions are below 5 % (relative !), and I can
easily bring that down - with more advance warning.

Our physics analyses typically include electrons that reach the CC under
physics eta of 1.3 . I could come up with a number for that regime, but people
would hate me for reporting this number.

 ---------------------------------------------------------------------------

Timing (Avto, with caveat from Jan)

> To simulate and reconstruct a ttbar MC event (without ZB overlay) in 
> Run IIb (with L0) environment takes about 3 minutes on a P4 3.2 GHz 
> machine. Time in GEANT, Digitization and Reconstruction steps is spent 
> as follows:
> 
> d0gstar: ~ 2.5 min., d0sim: ~10 sec and d0reco: <~0.5 min.

 ---------------------------------------------------------------------------

Trigger bits:
  L1 - 256
  L2 - 1024 (?)
  L3 - ???

  We include all necessary triggers, including calibration trigger and adjust
  the rates using prescales.