Muon Tracking Meeting

SOR issue First priority Diagnostic: MCH DetectorScriptError Arriving at the initialization stage: the whole or part of a Crocus is in error Not coming from a particular Crocus During last TS, stabilization of SOR in Standalone runs by increasing the timeout of the script sequence and adding a second try for init => timeout and second init try also set for global partition runs but without success => In any case the origin of the problem is not completely identified => Problems with TCL encapsulated script in global mode: => solve the very large majority of SOR stops (several hours in TEST_3 partition without problems – 100 runs + technical runs..) => the origin of “real” SOR problems not solved …. But rare => In parallel, one suspects a not complete reset at one fpga level: => check at Orsay

EOR issue: busy during run Second priority (second cause of run stop due to MCH) Diagnostic: MCH DetectorBusy Arriving during a run: One (or several) Crocus is(are) stuck; cannot control it => run is stopped; decrease data taking efficiency Origin not yet found Not too much impact on data taking efficiency if we can Pause/Configure(Reset)/ Resume => PAC (Pause And Configure) has been tested successfully on ldc (locally) by Orsay and Filippo => during their stay, Orsay team will test PAC at P2 in global mode, with the help of Franco (includes some ECS commands like ttcinit…): sucessfully done but still little things to look on Franco’s side SYNC is an automatization procedure for the PAC, with (re-)synchronization of detectors Part of SYNC can be tested in local mode: => during their stay, Orsay team will contact Anton: successfully done in local mode Origin ?: at least need probes on DSP => probes and the whole setup (PC, probes power supplies, software..) have been fixed on one Crocus => we would like to see if the busy during run is coming from SEU (?) Setup tested successfully in B OFF Connection lost when switching ON the magnet => try to move a little more the transformer away from the magnet : can be done during short access => if it does not solve the problem of connection, a detailed inspection is needed: in this case we must enter FASS and we have to wait the next TS (end of June)

L1r issue Conflict when running with EmCal L1r Increase of deadtime as a function of rate Causes token loss error MCH can run in another configuration …. but has to be investigated => Test will be done soon at Orsay -Anton provided the sequence giving problem - a special fiber (between LTU and Fan out of Trigger Dispatcher) has been ordered and is now at Orsay: test can start

« New » issues SIU old product to be changed during next TS. It does not impact data taking in the meantime => Change done LV power supply has too high temperature on CH6L: switched OFF Will be changed during next TS or before during access Can be also flushed ? Last news: attempt to replace LVPS yesterday during access but: - problem with new LVPS : USB port not working - new problem on LVPS Crocus: one dead channel => 1 crocus not readable => 1 half-chamber CH9L => Need a new access (2h) to replace 2 LVPS (we have spares)

Long Shutdown LS1: 2013 – mid 2014

Work on slats Occupancy / busbar connections Large occupancy mainly due to bad busbar connections  Soldering bypass wire on -2.5 V line on each link between two busbar sections  During each winter shutdown (2 – 3 months), about 25 slats repaired ( 3 had been repaired during the previous winter shutdown) Winter : 24; Winter : 28 => Total 52 slats repaired; Total slats: 140 => ~ 90 remaining slats  at least 8 – 10 months of work ( year 2013)  Probably more: - station 3 more difficult and to be opened - more tests  each week : a team of 3 -4 people ( among them, ~ 2-3 » technical » people; at least 1 physicist knowing daq running)  Groups have to plan manpower and budget for this LS1  Manpower: technical + physicists  Budget: - mission budget for physicists - M&O B (and mission budget) for Technical staff  Discussion on M&O B during Muon IB

Work on slats ? Occupancy / MANU connections How to improve MANU / Translator connections ? Think about => Suggestions ? Parity errors (mainly on stations 3, 4, 5 but not only) Origin ? How to improve ? Suggestions ? Discussions with Orsay (Sylvain…) Tests in laboratories on spares ? Gas leakage Mainly due to not tight connections => be careful and check during mounting of slats (Improving slats leakage ?) => need gas during shutdown for check (Ar-CO2 not mandatory for a long period; but needed at some point for tests)

Work on quadrants Change / repair of quadrant => dismount quadrant Quad / PCB repair: problems on PCB ? MANU change Mechanical positioning of quadrants of station 2 Difficulties to position correctly Quadrants inclined => difficult to align => need to think and prepare new procedure, tools (Kolkata) Photogrammetry / survey Need to think how, where to add « mires » on quadrant: to improve alignment

Answers Rate limits: HV trips during B OFF run (very high background) – till only few trips Test of rates can be done now (?) Cooling system: no upgrade, improvement Gas system: no upgrade; we can reduce the flux but need gas to check leakage during slats/quadrant repairing Cables: no new cable to add Hardware intervention: see LS1 plans above Extension: no DCS, no network outlets, no rack Interlocks: OK