60 likes | 215 Views
The DTTF Status. Giuseppe Codispoti (Universidad Autónoma de Madrid) For DTTF Group. Overview. Software Status Hardware status. Software status. Trigger Supervisor: working smoothly Masking tool provided for DTTC (decoupled from DTTF configuration)
E N D
The DTTF Status Giuseppe Codispoti (Universidad Autónoma de Madrid) For DTTF Group G.Codispoti – Muon barrel Workshop
Overview • Software Status • Hardware status G.Codispoti – Muon barrel Workshop
Software status • Trigger Supervisor: working smoothly • Masking tool provided for DTTC (decoupled from DTTF configuration) • Rate playback monitor: working smoothly • Alarms: in place since last MWGR • Many improvements and refinements: • Alarms provided only during collisions • Separated action suggested for input/output rate problems • DQM & emulator: working fine G.Codispoti – Muon barrel Workshop
Hardware Overview • All crates fully operational in P5 • PHTFs: • Working smoothly: no major problems • A list of minor issues in the next slide • ETTFs: • ETTF S5 : always read-out =0 for all wheels • Inputs masked because of high rates: • S2: N2 MB3 • S5: N2 MB1/2/3 ; S5 N1 MB1/2/3; S5 P0 (unlocks in MB1/2, to be checked MB3) • S9: P0 MB1; S9 P2 MB1/2/3 (ETTF input problem?) • S10: N1 MB3 • S11: P1 MB2 • More about inputs: • S9 N2 MB1 fluctuating from very high to very low rates • S6 N1 MB1 low rate (?) G.Codispoti – Muon barrel Workshop
PHTFs minor issues • “LUT” Problems: • P1 S4 MB2 (double peak both position and direction) • N2 S11 MB3 (low impact, from 2010) • N2 S6 MB2 (Sector Collector problem) • MB4 LUT problems (new saga?) • Last time many of them, disappearing after a crate reboot • Last appeared N2 S3 and P1 S3 • Other minor issues • S5 N0: trigger ok, but data not read-out • S12 P0: receiving extra rate from neighbor P1 (MB2) • Just waiting for enough time to address all of them (technical stop) G.Codispoti – Muon barrel Workshop
DTTF Out-of-Sync’s: a brief report • At some point OOS caused by a problematic board: • S3 P0, exchanged on April 12th • Almost no more OOS for the rest of April! • In the last days some OOS due to S2 P0 • run recovered by resync’s • problem disappeared after crate reboot as soon as it was allowed • Defined strategy in case of new occurrences: • Call the expert before any action on the system during working hours • Just in order to identify the problematic board • Automatic resync in the other cases • trigger management request for deadtimes reduction • crate reboot as soon as it is allowed • fixes the problem for long periods, eventually waiting for a technical stop for intervention G.Codispoti – Muon barrel Workshop