1 / 8

Offline issues in RTTC Runnign the Trigger Applications

Offline issues in RTTC Runnign the Trigger Applications. RTTC meeting 14 juillet, 2005. Acknowledgments & Disclaimers. We (the Online-team) and me in particular are not very experienced in handling the offline-software

karleigh-williams
Download Presentation

Offline issues in RTTC Runnign the Trigger Applications

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. Offline issues in RTTCRunnign the Trigger Applications RTTC meeting 14 juillet, 2005

  2. Acknowledgments & Disclaimers • We (the Online-team) and me in particular are not very experienced in handling the offline-software • We are grateful for the lots of patience and help which we got from our offline friends. Especially from Markus, Marco and Patrick Thanks Niko Neufeld CERN, PH

  3. Lessons from MEP production • Some detectors (VELO, RICH) do not always generate a RAW bank for all TEL/UKL1s as is mandatory: • Unexpected - but not a big problem for us • Generate simply empty MEP fragments • The responsibles have been informed • Memory leaks: • Quite a few fixed during MEP preparation • Long test will bring out event very small occasional leaks Niko Neufeld CERN, PH

  4. Options file • The uniformity between “Online” and “Offline” option-files has to be pushed further • In general works quite well, but • Many algorithms in particular in HLT depend on information in Rec / Trig problems for “offline” running on stripped DSTs – excessive (?) use of DataOnDemandSvc in online • Need still a few “hacks”, which shouldn’t be strictly necessary (e.g.: GaudiPoolDB DLL in online) Niko Neufeld CERN, PH

  5. Data handling • RTTC data are provided in 70000 tiny files • Data handling very cumbersome, have to strive for bigger files • It has proved to be invaluable to have a private disk-server for all the data, even though we did not inject the data directly from the server Niko Neufeld CERN, PH

  6. Debugging tools • All of the following debugging tools have been extremely useful: • L1: MonitorSvc to compare offline decision to online decision • HLT: HltCompare2RawBuffer unfortunately does not work at the moment (needs the RawBuffer _not_ the RawEvent!) • Direct input of raw-event files into GaudiOnline • mepcat and related hex-editors for the raw-data Niko Neufeld CERN, PH

  7. Offline rates • L1-Yes = Euler accept rate is 6.1% (should be 4%) • HLT-Yes = Moore accept rate is 1.6 % (should be 5%) • This seems to be understood: Missing Muon channel in L1, Velo geometry, etc… • HLTGeneric seems to be fine (comes out with 10 kHz) Niko Neufeld CERN, PH

  8. Status • MEP production: • 25% ready • This includes: • L1MEPs for all L0 accepted events • HLTMEPs for all L1 accepted events • Merged / stripped DSTs • Per job (in total 28) I produce • A merged DST (raw and l1 buffer only) of all L0 accepted events • A stripped DST (raw and l1 buffer only) of all L1 accepted events • A stripped DST (raw and l1 buffer only) of all HLT accepted events • MEPs and DSTs are available from lbfsrk4076:/shift/lbfsrk4706/data02/rttc/$jobid • Use rfcp and rfdir ($jobid varies between 00 and 06currently) Niko Neufeld CERN, PH

More Related