1. Missing Et Before and After Shutdown Yuri Gershtein

2. 7/8/2003Yuri Gershtein - CALO Meeting2 The Problem Di-EM skim: 2 EM objects Et>7 GeV ~3% of the data MET in gg events with all clean-up cuts except H-matrix (i.e. signal + background together) Tails are obviously worse in the post-shutdown data – WHY? Run < 172K Run > 172K

3. 7/8/2003Yuri Gershtein - CALO Meeting3 Bad runs? Hypothesis: may be the looser selection criteria for post-shutdown data make a difference? run Fraction of events with MET>20 GeV What happened after run 175500? all events from diEM skim Moriond Sample IIIIII

4. 7/8/2003Yuri Gershtein - CALO Meeting4 Bad runs? run Fraction of events with MET>20 GeV Good runs from diEM skim Bad runs from diEM skim

5. 7/8/2003Yuri Gershtein - CALO Meeting5 Two hot regions All events MET > 20 GeV All events MET > 20 GeV MET Azimuth jets EM objects II III

6. 7/8/2003Yuri Gershtein - CALO Meeting6 End of Story? All events Good runs Two hot spots removed Both hot zones are not present after my cleanup cuts – only CC em’s and no jets in ICD region MET

7. 7/8/2003Yuri Gershtein - CALO Meeting7 MET before – after shutdown MET Normalized at MET<20 GeV x2 difference at MET>40 x5 difference at MET>120

8. 7/8/2003Yuri Gershtein - CALO Meeting8 MET v.s. MET Azimuth MET MET azimuth MET > 30 GeV MET > 50 GeV MET > 100 GeV III

9. 7/8/2003Yuri Gershtein - CALO Meeting9 Event from the peak The event has two isolated EM objects – simple cone clustering…

10. 7/8/2003Yuri Gershtein - CALO Meeting10 Run dependence? MET azimuth v.s. run for MET > 30, 50 and 100 GeV 162K <run< 172K – clean run < 162 K – worse run > 172 K – a mess…

11. 7/8/2003Yuri Gershtein - CALO Meeting11 Zoomed For Run > 172K Almost all data is affected Worst for run > 176184 (Apr 26, after a 4 day shutdown…)

12. 7/8/2003Yuri Gershtein - CALO Meeting12 Look for more hot regions EM objects, Et > 20 GeV Run range I (run < 162 K) good runs detector eta azimuth

13. 7/8/2003Yuri Gershtein - CALO Meeting13 Look for more hot regions EM objects, Et > 20 GeV Run range II (162K < run < 172 K) Good runs All events MET > 30 MET > 30, HM > 50

14. 7/8/2003Yuri Gershtein - CALO Meeting14 Look for more hot regions EM objects, Et > 20 GeV Run range III (run > 172 K) Good runs, hot spots removed All events MET > 20 MET > 20, HM > 50 More than ten hot areas!!

15. 7/8/2003Yuri Gershtein - CALO Meeting15 Hot EM regions It seems that there is always some energy in these hot areas: no good EM particles in these areas… HMatrix Chi2 Hot EM Normal EM (same eta) Hot EM Normal EM (same eta)

16. 7/8/2003Yuri Gershtein - CALO Meeting16 Hadronic Hot Regions Run 30

17. 7/8/2003Yuri Gershtein - CALO Meeting17 Hadronic Hot Regions 162< run<172 K, good runs, leading jet MET > 30 MET > 50

18. 7/8/2003Yuri Gershtein - CALO Meeting18 Hadronic Hot Regions run>172 K, good runs, leading jet, MET>50

19. 7/8/2003Yuri Gershtein - CALO Meeting19 Summary (1) Need better monitoring of the calorimeter The typical failure mode in the data is a hot cell/tower/BLS/ADC/… which is fires at a relatively small rate invisible in distributions like jet eta-phi for all events, need monitoring for events with large MET persistent through a long period of time have relatively small energies, from 30-40 GeV to very small…

20. 7/8/2003Yuri Gershtein - CALO Meeting20 Summary (2) Is the data recoverable? Almost all post-shutdown data is affected Possible ways to recover may be the hardware signature can be recognized (similar to the BLS recovery)? may be the cells (if these are cells!!) should be excluded from MET calculation? may be just reject events with energy in the hot areas? – easiest to do, hardest to calculate efficiency of – plus, there are A LOT of hot areas 