1 / 18

FCLR aborts in the BMUON DAQ system

DESY, 7/2/07 DIFF. Weekly Meeting. FCLR aborts in the BMUON DAQ system. A. Bertolin. Brief outline: what was the problem ? (quick reminder) how to correct the data ? what are the affected events ?. what was the problem ?.

mac
Download Presentation

FCLR aborts in the BMUON DAQ system

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. DESY, 7/2/07 DIFF. Weekly Meeting FCLR aborts in the BMUON DAQ system A. Bertolin • Brief outline: • what was the problem ? (quick reminder) • how to correct the data ? • what are the affected events ?

  2. what was the problem ? • the GFLT is sending to ALL ZEUS components a two-bit word called “read out type” (rot) • the original assignment was: • rot=0: normal trigger • rot=1: off beam trigger • rot=2: test trigger • rot=3: init trigger • Þ BMUON TLT and Offline were analyzing ONLY events with rot=0 • after theactivation of the FCLR aborts in the ZEUS trigger (HERA II data) the assignment changed to: • rot=0: normal trigger • rot=1: normal trigger directly after a FCLR abort • rot=2: test trigger • rot=3: init trigger • by mistake nothing was changed in the BMUON TLT and Offline • Þ BMUON was loosing ALL “rot=1” events (i.e. “good” physic events directly after a “bad” event aborted by the FCLR)

  3. how to correct the data for this effect • at the TLT level for any BMUON slot BEFORE the update of the TLT code: • nevt_recorded = nevt_rot=0 • nevt_corrected = nevt_rot=0 + nevt_rot=1 • = nevt_rot=0 (1+ nevt_rot=1/ nevt_rot=0) • < nevt_rot=1/ nevt_rot=0 >: • TLT slot independent • nevt_corrected = nevt_rot=0 (1+ < nevt_rot=1/ nevt_rot=0 >) • easiest solution: increase the number of BMUON events by • (1+ < nevt_rot=1/ nevt_rot=0 >) • how to compute < nevt_rot=1/ nevt_rot=0 > ? • how to do it in practice ? • how to test if this correction is fine and how accurate it is ?

  4. how to correct the data for this effect (cont.) < nevt_rot=1/ nevt_rot=0 > can be taken from another TLT slot (like DIS03) by running an analysis job over ALL the ZEUS PHYSIC runs … • HFL30 • DIS03 < nevt_rot=1/ nevt_rot=0 > or much more easily from the run summary ntuples as suggested during discussions at the Trigger Meeting … but do we get the same results ?

  5. how to correct the data for this effect (cont.) • HFL30 (measured) • estimated from the run summary ntuple • DIS03 (measured) • estimated from the run summary ntuple • as expected by the trigger experts the result is the same (DIS03: higher accuracy test)

  6. < nevt_rot=1/ nevt_rot=0 > 2003/2004 pos. run Î[46370,51245] 2004/2005 ele. run Î [52258,57123] first run with FCLR aborts enabled: 49565 13-MAY-2004 23:57:56 PHYSICS STD_040513_HIGH 2003/2004 pos. 2004/2005 ele. 2006 ele. run Î[58207,59947] 2006 pos. run Î[60005,61229[ 2006 ele. 2006 pos.

  7. how to correct the data for this effect (cont.) • for what has just been shown we learn that, even after taking into account a large “trigger type” dependence ( _HIGH and _LOW), < nevt_rot=1/ nevt_rot=0 > shows a significant run to run dependence: • different trigger configurations • beam quality • run by run corrections to test the procedure use: • 200 runs taken from the 2004/2005 ele. sample • DIS03 recorded events • using only the number of recorded events with rot=0 and the run summary ntuple data we have to find out the total number of events, rot=0+rot=1, and compare it with what was recorded online

  8. how to correct the data for this effect (cont.) from the run summary ntuples FLCR abort fraction rot=0 = 792781 rot=1 = 36933 rot=0+rot=1 = 829714 rot=0(1 + <rot=1/rot=0>_run) = 829639 829636-829714/ 829714 < 0.1 ‰ Þthe run by run correction is accurate at the < 0.1 ‰ level

  9. how to correct the data for this effect (cont.) other solution: compute a luminosity weighted average of the FCLR abort fraction for the run range under analysis (xi ºFCLR abort fraction for run i) • S (xi / si2) / S (1/ si2) • si = lumii • big weight, 1/ si2, to low luminosity runs Þdiscard this formula • S (lumiixi) / Slumii • “center of gravity” formula looks more appropriate rot=0 = 792781, S (lumiixi) / Slumii = 0.047... rot=1 = 36933 rot=0+rot=1 = 829714 rot=0(1 + FCLRaf_lumi. weighted) = 830340 830340-829714/ 829714 ~ 0.7 ‰ < 1 % accuracy

  10. what are the affected events • rot=1 event with a muon in BMUON which fires also DIS03 (or HPP01, or any other TLT slot NOT using BMUON data): • saved at the TLT because of DIS03 • will not have any BMUON TLT of Offline data because the “abort bit” is set BUT the BMUON “RAW” data is available and consistent • Þ by running mbrecon ³v2006a.1 the BMUON Offline data will be recovered • Þno extra correction factor is required • rot=1 event with a muon in BMUON not taken by other ZEUS TLT slots: • will not have any BMUON TLT of Offline data because the “abort bit” is set • will not be saved at the TLT by other ZEUS slots (by construction) • Þ lost withoutany remedy • will have to correct for it • summary: ONLY exclusive BMUON TLT events have to be corrected for this effect

  11. what are the affected events (cont.) • some simple examples: • elastic J/y (®m m) events • inelastic J/y (®m m) events • BH events • are known to be triggered predominantly by BMUON Þuse the correction factor worked out previously • m + di-jet analysis starting from the “HPP15: jj PHP (cone)” TLT bit • F2(charm,beauty) using m + MVD starting from the “SPP01: Incl DIS(mid Q2)” or “DIS03: Medium Q2” TLT bits • events kept at the TLT using non-BMUON data • Þ no correction factor required • Þ recover BMUON Offline data using mbrecon ³ v2006a.1 while linking ORANGE

  12. run ranges taken from http://www-zeus.desy.de/physics/lumi/ • 1 + FCLRaf_lumi. weighted factors: • 2003/2004 pos. data + evtake + mbtake • run range: [45783 ,51245] • FCLRaf_lumi. weighted = 0.020108 • 2004/2005 ele. data + evtake + mbtake • run range: [52258,57123] • FCLRaf_lumi. weighted = 0.114817 • 2006 ele. data + evtake + mbtake • run range: [58207 ,59947] • FCLRaf_lumi. weighted = 0.136457 numbers checked by Monica T. numbers valid for ANY exclusive BMUON TLT slot: MUO03, HFL30, EXO11, EXO12 …

  13. what are the affected events (cont.): SPP, DIS, HPP & EXO based on the STD_061211_HIGH / LOW trigger config. • any SPPxy (xy=01 … 16)Þmbrecon ³ v2006a.1 • any DISxy (xy=01 … 32)Þmbrecon ³ v2006a.1 • any HPPxy (xy=01 … 31)Þmbrecon ³ v2006a.1 • EXO01: Elastic ee, EXO02: CC Good Track, EXO03: Hi Et, EXO04: NC High Et, EXO05: NC No Backward E, EXO06: CC, EXO07: NC High Q2 • EXO08: FMU VSA/SA, EXO09: FMU LA Þ BMUON-like correction • EXO10: Dimuon … BMUON – FMUON mixed slot • EXO11: BMU, EXO12: RMU Þ1+FCLRaf_lw • EXO13: Diffractive CC, EXO14: Inelastic ee, EXO15: Island Et, EXO16: High Pt electron, EXO17: Total Et + e, EXO18: High Total Et • EXO19: Cosmic showers • EXO20: CC,EXO6+vtx+Pt cut • EXO21: Cosmic showers+BAC

  14. what are the affected events (cont.): MUO • MUO01: FMU isolated, MUO02: FMU High Et Þ BMUON-like correction • MUO03: BMU Þ1+FCLRaf_lw • MUO04: FMU elastic old, MUO05: FMU elastic new, MUO06: FMU dimuon, MUO07: FMU DOS, MUO08: FMU Jets, MUO09: FMU CC • MUO10: BAC DI-MUON Þmbrecon ³ v2006a.1 • MUO11: FBAC ISO MUON • MUO12: BRBAC ISO MUON • MUO13: FBAC HI-PT MUON • MUO14: BRBAC HI-PT MUON

  15. what are the affected events (cont.): HFL …    … • HFL01: HFL mesons in PHP • HFL02: HFL mesons in DIS • HFL03: HFL mesons in CC • HFL04: Diffr. HFL mesons • HFL05: (di)jets in PHP • HFL06: (di)jets in DIS • HFL07: (di)jets in CC • HFL08: Diffr. (di)jets • HFL09: semil. e in PHP • HFL10: semil. e in DIS • HFL11: semil. e in PHP • HFL12: Diffr. semil. e • HFL13: semil. mu in PHP • HFL14: semil. mu in DIS • HFL15: semil. mu in CC • HFL16: Diffr. semil. mu • HFL17: NC DIS w/2 trks • HFL18: D* gold selection • HFL19: D0/D0=bar mixing • HFL20: meson + meson • HFL21: meson + jet(s) • HFL22: meson + e • HFL23: meson + mu • HFL24: (di)jets + e • HFL25: (di)jets + mu • HFL26: e + mu • HFL27: MVD incl. trigger • HFL28: MVD incl.beamspot • HFL29: elastic mu+mu- … • HFL30: inelastic mumu    • HFL31: dimuon from MV • HFL32: dimuon double tag • up to: • TLT ver. v2006_9 i.e. • 59581 ³ run (end of 2006 ele.) • onlygreen and pink • since: • TLT ver. v2006_12 i.e. • run ³59586 • red appears

  16. how to correct the data for this effect: more complicated scenario elastic J/y analysis based on the (MUO03 .or. MUO05) TLT bits • event from a BMUON .or. FMUON TLT slot • rot=1 event (taken by FMUON) Þ kick it out • correction needed, which one ? • BMUON correction: FCLRaf_lw will use evtake + mbtake ®FCLRaf_lw_mb • FMUON correction: FCLRaf_lw will use evtake + fmutake ® FCLRaf_lw_fm • if FCLRaf_lw_mb » FCLRaf_lw_fm wrong: in 03/04 ele. the FMUON number differs by -5.4 %, in 04/05 pos. by +5.7 % … • if FCLRaf_lw_mb ¹ FCLRaf_lw_fm • BMUON event Þ FCLRaf_lw_mb weight • FMUON event Þ FCLRaf_lw_fm weight • taken by both Þ ?

  17. how to correct the data for this effect: more complicated scenario (cont.) • but in the MC simulation both BMUON and FMUON “detectors” are working at the same time and hence in the run bookkeeping requirements one should use: mbtake=1 .and. fmutake=1 correction: FCLRaf_lw using evtake + mbtake + fmutake • run ranges taken from http://www-zeus.desy.de/physics/lumi/ • 1 + FCLRaf_lumi. weighted factors: • 2003/2004 pos. data + evtake + mbtake + fmutake • run range: [45783 ,51245] • FCLRaf_lumi. weighted = 0.018773 • 2004/2005 ele. data + evtake + mbtake + fmutake • run range: [52258,57123] • FCLRaf_lumi. weighted = 0.118303 BMUON .or. FMUON TLT requirement

  18. conclusions • TLT fixed since run 61229 • Offline fixed with the release of mbrecon v2006a.1 • mbrecon v2006a.1 incorporated in the current Zephyr (i.e. the one used to reconstruct the data we are taking NOW) & in the Zephyr used for the 2003/2004 pos. reprocessing • most of the ZEUS TLT slots, including MUO03, HFL30 ..., can be easily corrected, prelim. numbers are available • HFL slots mixing BMUON, FMUON and BAC require more work … but ONLY exclusive BMUON (and FMUON) TLT events have to be corrected for • try to have a common BMUON and FMUON prescription, if possible • how large was the effect for exclusive BMUON TLT slots in round numbers: • no effect for HERA I data • @2 % for 2003/2004 pos. • ~ 10 % for 2004/2005 ele. and 2006 ele. • no effect since run 61229

More Related