1 / 11

Energy Deposited in a Crystal and GemDeltaEventTime

Energy Deposited in a Crystal and GemDeltaEventTime. Yvonne 1/28/08. GEM DT of Protons : Difference in Rates at SPS and PS. PS 6.0 GeV Proton run Few events after 2 ms GemDT. SPS 100.0 GeV Proton run Most events saturate GemDT.

boris
Download Presentation

Energy Deposited in a Crystal and GemDeltaEventTime

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Energy Deposited in a Crystaland GemDeltaEventTime Yvonne 1/28/08

  2. GEM DT of Protons :Difference in Rates at SPS and PS PS 6.0 GeV Proton run Few events after 2 ms GemDT. SPS 100.0 GeV Proton run Most events saturate GemDT 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

  3. Average energy deposited in a crystal increased by 5% for 6 GeV-PS-Protons from no GemDt cut to GemDt > 3.0ms 0.5ms cut 1.0ms cut 1.5ms cut Cuts Layer == 0 Crystal == 6 Tkr1ZDir < -0.98 Energy in [0,40] GemDt Specified on Plot Bin Width = 0.1 MeV 2.5ms cut 3.0ms cut 2.0ms cut DEavg = 5 %

  4. Average energy deposited in a crystal did not change for 100-GeV-SPS-Protons from no GemDt cut to GemDt > 3.0ms Cuts Layer == 0 Crystal == 7 Tkr1ZDir < -0.98 Energy in [8,40] GemDt Specified on Plot Bin Width = 0.1 MeV DEavg = 0.4 %

  5. Average energy deposited in a crystal did not change for 20-GeV-SPS-Pions from no GemDt cut to GemDt > 3.0ms DEavg = 0.1 %

  6. Average energy deposited in a crystal did not change for 18-GeV-GSI-Carbon from no GemDt cut to GemDt > 3.0ms DEavg = -0.2 %

  7. For 6 GeV(PS) Protons the energy deposited in a crystal for the MC is 9% higher than in the Data Data GemDT > 3 ms MC DEavg = 9.2 % DEpeak = 8.4 %

  8. For 100 GeV(SPS) Protons the energy deposited in a crystal for the MC is 2% lower than in the Data Cuts Layer == 0 Crystal == 7 Tkr1ZDir < -0.98 GemDeltaTime > 6.4e4 Energy in [8,40] Bin Width = 0.1 MeV DEavg = 2.4 % DEpeak = 2.6 %

  9. For 18 GeV(GSI) Carbons the energy deposited in a crystal for the MC is 25% lower than in the Data Cuts Layer == 0 Crystal == 4 Tkr1ZDir < -0.98 GemDeltaTime > 6.4e4 Bin Width = 0.5 MeV DEavg = 25 % DEpeak = 25 %

  10. 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 RECON From DIGI

  11. 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

More Related