Calibrations & monitoring for DT

1. Calibrations & monitoring for DT For DT chambers, “calibration” is mainly a timing/syncronization issue : • Trigger level • e.g.: - internal local clock phase adjustment of BTI • - absolute syncronization (using the LHC bunch structure) • - Track Finder LUT’s calibration • TDC level • - threshold calibration • - t0 calibration • - gap test/ test-pulse • - rate measurement • - tmax, vdrift measurement • - alignment with muons 3/04/02

2. BTI synchronization First ideas have been developed (Trigger TDR, CMS-IN 2000/031 ) considering typical L1 trigger rates of ~ 12 KHz in dedicated technical runs (e.g. with ‘single station’ technical trigger), looking to mean-time distribution as a function of the internal synchronization phase (in “minimal BTI acceptance” configuration) ~1000 ev/chamber/’point’ adequate for the procedure P.Zotto at al. 3/04/02

3. BTI synchronization High quality Trigger efficiency (caution: curve may be distorted by time-dependent LHC luminosity) P.Zotto at al. Meantime r.m.s. MC (unaffected by lumi variations) At 1034, the procedure should take ~ 2h for the barrel detector (plots from MC tracks, normal incidence to the chamber; procedure also tested on H2 testbeam) 3/04/02

4. DT calibration At DAQ level (i.e. L2 or before (DDU level?)) we’ll likely want to have meantime distributionsin each chamber for different GMT output (eg L1A from DT only, from RPC only) ~ few min. run @ 1033 ( 6 Hz/m2 prompt muons in MB4, 30 Hz/chamber, ~ 2 KHz rate total ) Drift time distribution, integrated over all SL cells Tmax from local tracks in a SL (=> drift velocity measurement) 3/04/02

5. DT calibration flow (M.Dalla Valle, Calibration workshop Sept.’2000): • these run types are currently being considered: 3/04/02

6. DT calibration/monitoring Which “local software tool” we need (and where they run)? How do we spy data? Where the ‘local DAQ path’ will be splitted from the normal DAQ ? 172,200 channels 250 chambers 5x12 = 60 sectors 10,960 FEB 16 channels/FEB 60 ROS Master Opt.link 1,440 ROB 5 DDU DAQ 120Mb/s On chamber “MINICRATE” In 1 ROB: 4 32-channels TDCs 1 per sector (4 chambers) 1 per 12 ROSM 3/04/02

7. DDU CMS TriDAS layout 3/04/02

8. fast monitoring ROS ROS ROS ROS ROS ROS ROS ROS ROS ROS ROS ROS Final DDU block diagram (R.Cirio, 20/3/2002 PD Electronics meeting) Input FIFOs TTC ‘FPGAs’ VME - DCS Output FIFOs CMS readout 3/04/02

9. DT calibration/monitoring • Which “fast monitoring” we may think of ? • at DDU level, data from entire sectors available.... • - fast meantime analysis @ chamber level • - fast local tracks in chamber (see testbeam online data analysis) • - fast muon reco (‘reduced version’ of L2 reco running in DAQ farm) 3/04/02

10. - fast meantime analysis: SL test in Legnaro A.Meneguzzo 3/04/02

11. - fast local tracks in chamber (see testbeam online data analysis) BC 3 Online Event Display S.Vanini, A.Colaleo RPC SL 3() SL 2() SL 1() BC 2 RUN 642 BC 1 Oct.2001 3/04/02

12. - fast muon reco (‘reduced version’ of L2 reco running in DAQ farm) Where do we foresee to do that? Compare L1 TrackFinder vs L2 3/04/02

13. LUTs calibration Could also be HLT output... DB DAQ RECO DTTF Global Muon Trigger RPC CSCTF LUT Calibration Input Data Spy Local Software Tools Comparisons between the locally stored input to the Global Muon Trigger and the reconstructed data will be used to calibrate the matching look up tables and to calibrate the look up tables for the candidate selection and ranking 3/04/02

14. Summary • Many ‘on-line’ software items implied by DT calibration/monitoring • procedures • they concern both Trigger & RO systems • understand sharing between local DAQ monitoring & central DAQ • define which methods & tools • develop prototype to be used in next testbeam runs 3/04/02