1 / 7

Muon DAQ work during LS1

Muon DAQ work during LS1. Info collected by Daniel from : Enrico , Francesco, Masato, Michael, Nicoletta , Stephanie, Thei. Foreseen Central DAQ changes. Migration to tdaq-05 --> migration to SLC6 for the SBCs and detector computers. Spring 2014 ?

kylene
Download Presentation

Muon DAQ work during LS1

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 work during LS1 Info collected by Daniel from : Enrico, Francesco, Masato, Michael, Nicoletta, Stephanie, Thei

  2. Foreseen Central DAQ changes • Migration to tdaq-05 --> migration to SLC6 for the SBCs and detector computers. Spring 2014 ? • Experience shows: usually painless, but needs to be synchronized (drivers,…) • Data sampling for DQ will not be done anymore at the event builder nodes (which will not exist anymore), but through the trigger, using a new “monitoring stream”. To be presented/discussed tomorrow

  3. CSC plans • Old off-detector readout system needed at least until December 2014 to re-commission the wheels once they are both back in working position • New off-detector readout system under development: • Run at 100kHz L1 rate w/o deadtime • Implement ROD stop-less removal/recovery • Implement TTC restart • Abandon the txt files for loading the calibration results into the RODs in favor of using COOL • Improve OKS description to feed the status of resources

  4. MDT plans • Working on an MROD with a second output and with that, one can split the towers with the high rates. • 48 extra read out links and only a few (8 ?) extra MRODs need to be installed.

  5. RPC plans • Fairly extensive review/rewrite of the RPC Lvl1/DAQ software • Upcoming update of the CAN interfaces which requiring porting the software to the new API • Move the configurations to a database • Improve configuration time of the trigger towers and make recovery of misalignments during runs more robust. • Better integrate the RODs and their relative SLs to solve some reconfiguration and timing issues.

  6. TGC plans • Try to reproduce “FE noise burst” problem with test-bench in Blb 188. If something found, will try something with the standalone or global, July~August. • DAQ needed for development of the new Sector Logic firmware. Plan to do some tests using the standalone partition, around May~June. • Later, could try to speed up the access to configuration d/base and the actual configuration. • Work needed in the condition d/base area. Goal: go as standard as possible.

  7. Central issues • "MUON" standalone partition, to run TGC + MDT, RPC + MDT with a muontrigger; setting this up with the LTPI involves work. Do we want it ? • Keeping track of active/inactive/abandoned/removed detector elements in a common way • MRS and TDAQ messaging service. MuonsDDC makes some non-standard use (callbacks hooked to the exchanged messages). Do we want to improve on this?

More Related