1 / 7

Muon DAQ Workshop

Muon DAQ Workshop. Muon Week, CERN 17-21 February 2014 Nicoletta Garelli (SLAC). Workshop’s Goal. LS1 Need to keep DAQ up-to-date Occasion to fix and improve specific items Few people working on DAQ for the 4 subsystems  Try to work together as a whole system Share knowledge

amena-beach
Download Presentation

Muon DAQ Workshop

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. Muon DAQ Workshop Muon Week, CERN 17-21 February 2014 NicolettaGarelli (SLAC)

  2. Workshop’s Goal • LS1 • Need to keep DAQ up-to-date • Occasion to fix and improve specific items • Few people working on DAQ for the 4 subsystems  Try to work together as a whole system • Share knowledge • Identify tasks and priorities • Learn more about progress on specific topics • How to cure the MDT saturation problem  Tiesheng • TGC: How to improve the quality of the clock distribution and the noise burst  Toshi • RPC: progress on the new electronics and the new RCD  Franz • Discussion on some common aspects • Please, stop, ask, interact!

  3. Muon DAQ • Trying to collect information on a dedicated twiki • https://twiki.cern.ch/twiki/bin/viewauth/Atlas/MuonDAQ • Please, use it, update it! • Collect ideas for qualification tasks • Regular short meetings on Tuesday late morning since beginning of the year • Is it useful? • 7.8 FTE expected for 2014 • A lot of work! Ask for (wo)manpower? • Try to improve collaboration with • Monitoring group • DQ group • DB experts

  4. Muon Loop • Idea: to have it working before the new CTP • To run muon system independently • So far: • SLC5/tdaq-04-00-01: MuonLooppartition with MuCTPi and TGC • MuCTPi was generating 500 Hz L1A and the data were flowing from the TGC RODs to the SFIs without errors nor timeouts • Lessons learned: • Detector needed in order to use RODs • DAQ Slice used  good start towards (non ROS-EB) stand-alone data taking • Next Steps • Migrate to tdaq-05-03-00 • Muonsw, L1 sw, DAQ Slice • Integrate the other detectors • Perform timing measurements (L1 help needed)

  5. Muon Loop Plans • In the next months fewer big interventions on the infrastructure scheduled • More time for testing/running • Needed pieces • Experts running the system • Experts checking the timing with L1 people • Experts following up the upgrade of the sw to tdaq-05 • Will to make it working? • If yes, by when? • My guess: it could run in July 2014, if one person would work for a full day per week on it. • Good opportunity for new people to learn how to make the system running

  6. SLC6/tdaq-05 • Migration to SLC6 done by sysadmins • Fine. Few problems under control • Very important to use ticket system to report bugs/ask requests to sysadmins (https://atlasop.cern.ch/twiki/bin/view/SysAdmins/ContactSysAdmins#During_standard_working_hours) • Migration to tdaq-05-03-00 • Release notes actually contain very valuable information • Many new features offered by TDAQ not (yet) used or seriously studied/considered  we can do better • Some muon participation to the TDAQ Training • Was it useful? We should send feedback to TDAQ • Compilation of muonsw against tdaq-05-03-00 • Done a bit at the last moment, basically more than half M1 used for this  too few people working on this?

  7. M1 • We are basically at the first point • Running standalone • After this experience, will we be able to finish the integration during M2 or better aim to M3? • I think it was good to have experts around (despite concurrent Muon week) and progress on the compilation/standalone • but now we should be able to define better our goals for next M run • Shifter assistant and automatic actions by when?

More Related