1 / 5

EMu Slicetest Meeting

EMu Slicetest Meeting. April 26, 2006. SX5: ME+1 (6+12) All me+1/1 are timed in. me+1/2 are timed in. me+1/3 are about to be timed in. Next: calibration ME+2 (5) me+2/1/14, me+2/2/27-30 timed-in, calibrated ME+3 (4) me+3/1/14, me+3/2/27-29 timed-in, calibrated Green Barrack Trigger

waldo
Download Presentation

EMu Slicetest Meeting

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. EMu Slicetest Meeting April 26, 2006

  2. SX5: ME+1 (6+12) All me+1/1 are timed in. me+1/2 are timed in. me+1/3 are about to be timed in. Next: calibration ME+2 (5) me+2/1/14, me+2/2/27-30 timed-in, calibrated ME+3 (4) me+3/1/14, me+3/2/27-29 timed-in, calibrated Green Barrack Trigger SP uses all 4 MPCs CMS-type trigger: one muon on ME+2 or ME+3 and any other station effectively: 2-out-of-3 TTC production LTC (GB cont’d) FED 4 DDUs (3 in use) non standard set-up: one DDU per peripheral crate (easier diagnostics) 1 DCC with one S-Link 2nd S-Link ready to be installed Local DAQ two DAQ PCs. each takes care of 2 spy-channel inputs currently only 3 out of 4 spy channels read out FMM DDUs, DCC and TF plugged in outputs to Global DAQ and EMU-LTC Global DAQ overnight runs 15 chambers, coincidence trigger, FMM, no local daq 1.4M and 170k events. data is moved to castor some issues with DCC and Local DAQ status

  3. Short term plans • YE+1 (this week, end: early next week) • finish timing of ME+1/3 • set up 4th DDU and Local DAQ hook-up • finish calibration of all ME+1 chambers • Dubna request: ME+1/1 HV scan • dedicated ME+1/1-only trigger at TF • Global DAQ runs • FED (next week) • set-up 2nd S-Link in DCC • rearrange DDUs: each DDU takes care of one PerCr • easier diagnostics • ME+2 and ME+1a in one S-Link while ME+3 and ME+1b in the 2nd S-Link • emudaq02: free up 2nd Gbit for me+1b readout. • YE+2 (start: end of next week) • Maraton LV for all 18 CSCs and 2 PerCrs • added DMBs to allow remote LV control for all CSCs • replace TMBs and RATs with production versions • fill up crates: 2x9 chambers • Redo calibration on all chambers

  4. Open Issues • Local DAQ stable running • reading from 4 DDUs • interfacing: cscSV integration, standalone GUI • need 2nd Gbit on emuslice06 • currently in use by DCS • Peripheral Crate Core Lib • tag & release core/applic lib • support for xdaq v3 and OSU-CC only • rearrange directory structure • reflect core/applic separation • documentation … • FED • uncovered DCC issue when FED crate not fully loaded. • workaround exists, but not tested. also removes the DCC from FMM • Jianhui at CERN next week. • update hyperdaq FED software for DCC • no red-alert for newer firmware versions

  5. Important Dates • Friday May 19: Comprehensive MTCC readiness review • hardware and software readiness of each subsystem

More Related