1. Muon commissioning status and plans G.P. C. De Plano

2. 29/11/2006 Muon Meeting Test with L0 Extensive test performed last week with Marseille. Several time alignment problems found. Mainly in M1. Most of them solved by Caterina Remaining problems:  9 LogPads not seen by L0 (all in M1)  34 LogChan seen by L0 and (sometimes) not seen in data (mostly in M1; 2 in Q3M3R2  12 Log Chan not time-aligned (Mostly in M1; see later)  55 LogPads missing both in L0 and in data (mostly in M1; see later)

3. 29/11/2006 Muon Meeting “xcel file” bug A bug has been found by Alessia and Roberta in a set of xcel files where the delay to compensate the length of the I2C cables are coded. In a few cases a wrong delay has been evaluated. The effect is a shift of several ns of the time alignment of large regions namely:  Q3M3R4  M5A (large error only in R4)

4. 29/11/2006 Muon Meeting How to proceed Problems in M1:  “trivial” timing problems will be fixed as much as possible  Hardware problems (~60-70 pads over 9216 !) will be left aside. Problems in M2-M5  2 hw problems (2 pads in M5R1) will not be touched (mask the 2 channels)  An hw problem in Q3M2R2 must be fixed this week  A few timing problems are being fixed by Caterina and GP “xcel bug”: will be fixed by correcting the delays and re- running the timing procedure on:  M5R4A (2 HU)  Q3M3R4 (2HU)

5. 29/11/2006 Muon Meeting Plans for the coming weeks Noise. Several noise runs and threshold scans have been taken. The threshold settings determined with the well known algorithms seem to be reasonable but there are a few channels which are still noisy and seem to escape the general understanding of the noise and threshold. In addition the threshold scan seems to show an instability of the offset value. To understand better:  take more threshold scans: useful but time consuming and difficult because of the not perfect reproducibility of the procedure  take noise runs: easy but needs offline analysis. Requires a few recipes to be compared. Maybe it's worth to merge thresholds from different threshold scan runs

6. 29/11/2006 Muon Meeting Plans for the coming weeks Timing. From the cosmic data a reasonably good time alignment of the whole muon system is confirmed. However, there are some extended regions that are not aligned with the rest of the system. In addition we see a systematic effect due to the not perfect compensation of the I2C cable length that shift the time of the last channels in an I2C chain with respect to the first channels. To understand better:  take (many) more cosmics. a lot of work. Need to prepare new recipes with all the known time corrections obtained by hand or by new timing runs  perform a few additional timing runs to correct for obvious bugs: time consuming, must be restricted to a very few cases

7. 29/11/2006 Muon Meeting Plans for the coming weeks synchronization with L0. An extensive pulse test shows a general good agreement between the data measured by the muon system and the data received by the L0 trigger. However there are still some mismatches, often due simply to a wrong time alignment, but in some cases due to hardware problems. To understand better:  complete the test with Marseille and perform hardware interventions

8. 29/11/2006 Muon Meeting Plans for the coming weeks Data to TELL1. The data flow to the DAQ do not show particular problems but in some cases, mismatches with the L0 seems to indicate hardware problems in the transmission of data to the TELL1s To understand better:  complete the test with Marseille and perform hardware interventions  take data (cosmics) and study pathological cases (missing channels etc.)

9. 29/11/2006 Muon Meeting Plans for the coming weeks We have to set some priorities because we can not do everything. I think we should proceed like this: 1.Complete all the L0 tests and fix as many HW problems as possible this week. Then I am afraid we have to freeze the system and live with what we have. 2.This week: take a couple of noise runs to set the final threshold configuration and spot the noisy channels in order to study them and decide whether they need a higher threshold or to be masked. I think there is no more time for further studies with the threshold scan and we have to prepare a recipe with our best knowledge of the thresholds. 3.This week: prepare the recipes for the timing with the best knowledge to date (including xcel file bug fix), after the L0 pulsing test (and possibly the new timing runs). Negotiate to have 1 or 2 cosmic runs. 4.Next week : Prepare alternative timing recipes possibly with all the "hand" corrections calculated by Sandro/Caterina program. Negotiate to have a couple of cosmic runs. 5.Freeze the system and go to data taking.