Energy Deposited in a Crystaland GemDeltaEventTime

Yvonne

1/28/08

GEM DT of Protons :Difference in Rates at SPS and PS

GEM Delta event time counter in ticks of 50ns. Saturates at 3.3ms(6.6x104 ticks).2 ms is 4x104 ticks.Cut = 1 Hit in each cal layer

SPS 100.0 GeV Proton runMost events saturate GemDT

PS 6.0 GeV Proton runFew events after 2 ms GemDT.

Average energy deposited in a crystal increased by 5% for 6 GeV-PS-Protons from

no GemDt cut to GemDt > 3.0ms

CutsLayer == 0Crystal == 6Tkr1ZDir < -0.98Energy in [0,40]GemDt Specified on PlotBin Width = 0.1 MeV

0.5ms cut 1.0ms cut 1.5ms cut

2.0ms cut 2.5ms cut 3.0ms cut

Eavg = 5 %

CutsLayer == 0Crystal == 7Tkr1ZDir < -0.98Energy in [8,40]GemDt Specified on PlotBin Width = 0.1 MeV

Eavg = 0.4 %

Average energy deposited in a crystal did not change for 100-GeV-SPS-Protons from

no GemDt cut to GemDt > 3.0ms

Eavg = 0.1 %

Average energy deposited in a crystal did not change for 20-GeV-SPS-Pions from no

GemDt cut to GemDt > 3.0ms

Eavg = -0.2 %

Average energy deposited in a crystal did not change for 18-GeV-GSI-Carbon from no

GemDt cut to GemDt > 3.0ms

For 6 GeV(PS) Protons the energy deposited in a crystal for the MC is 9%

higher than in the Data DataGemDT > 3 ms

MC

Eavg = 9.2 % Epeak = 8.4 %

CutsLayer == 0Crystal == 7Tkr1ZDir < -0.98GemDeltaTime > 6.4e4Energy in [8,40]Bin Width = 0.1 MeV

Eavg = 2.4 % Epeak = 2.6 %

For 100 GeV(SPS) Protons the energy deposited in a crystal for the MC is 2%

lower than in the Data

For 18 GeV(GSI) Carbons the energy deposited in a crystal for the MC is

25% lower than in the Data

CutsLayer == 0Crystal == 4Tkr1ZDir < -0.98GemDeltaTime > 6.4e4Bin Width = 0.5 MeV

Eavg = 25 % Epeak = 25 %

Retrieving information about the energy at each crystal end from the MC files

• ADC values from digi file. CalXtalReadout.getAdc(face) • Energy values from recon file. CalRangeRecData.getEnergy(face)

From Anders: •The energy stored in the recon file is the total xtal energy (the geometric mean of the two ends). The reason the same energy is stored twice, once for each end, is historical. A long time ago we actually stored the two end energies, but this was changed. And the old data structures were kept.•Cal Recon itself has access to the two end ACD values which ituses to calculate both the position in the xtal and the total xtalenergy.•All this is common for both data and MC.

Looks like we can get face energies from CalTuple which is not available for MC Data

From DIGI From RECON

Summary

• Have learned a lot about the CAL

• PS Proton data suffers from pileup which may affect agreement with MC

• BT-MC files do not have face energy information stored

• No new ideas about antiquenching