1 / 10

Muon Planning

Muon Planning . A. Polini & Z. Yan August 21 th 2012. Outline Recap of last week Muon Ongoing Issues/Activities Plans and Outlook. Last Week. Inst . lumi record: 7.20 x 10 33 ; peak mu 32.25; ( more than 1.5 10 11 ppb) 0.8 fb -1  Please check Chamber current limits etc.

chelsa
Download Presentation

Muon Planning

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. Muon Planning A. Polini & Z. Yan August 21th 2012 Outline • Recap of last week • Muon Ongoing Issues/Activities • Plans and Outlook

  2. Last Week • Inst. lumi record: 7.20 x 1033 ; peak mu 32.25; • (more than 1.5 1011 ppb) • 0.8 fb-1 •  Please check Chamber current limits etc. • CSC deadtime visible at begin of fill. •  Presentation by Michael on rate tests and further rate improvements

  3. Last Week + Status • CSC: • Reappearing of link lost at run configure for Sector A07 (HW swap?) • MDT: • Several dropped mezzanines with corrupted data (run 208811)  ok after power cycle • RPC: • LVL1: 2 out of 404 towers masked (s50t2 A10, s58t2 A14, no new towers) • Sometimes one sector s51 misaligned (Sector 11 A HV noise…). • Access: • Broken ADC replaced and now OK (Igap monitoring sector 11-12) • Pad s35t3 in sector A03 replaced, now OK; • Another ADC (sector 15-16) failing  recovered via power-cycle of service voltage • BOL3A05 off due to LV problem: high pt of s35t2and s36t2 • Pending access requests: • LV problem in BOL3A05 Vth adapter to install (recover ¾ of the chamber) • MDT Gas group access: One faulty pressure sensor • RPC Gas group access: one gas line rack61 ch14 showing zero flux

  4. TGC Busy • TGC holding busy either permanently or while long recoveries requiring a TTC restart • Unfortunately this is becoming the sticking out problem • Unfortunately we make us unappreciated to ATLAS also because we appear as not following up the problem and lack a clear and reproducible fix • Need to find either a solution or a reliable workaround which reduces the impact and provides

  5. Plans and Outlook • Technical stop: • Physics running till beginning of Technical Stop (start Sept. 17th). • Prepare list of cavern activities, dedicated runs, • Muons already requirement for magnets off (RPC, MDT Alignment). • No official statement but should be ok. • Preparation for alpha run: • ATLAS wish for including Muons(as done last time) • LHC won’t declare Stable Beams • HV override (anybody against?) • Latency settings (followed by experts? instructions?) • Run Extensions + Shifts • Detector Status and Activities during Xmas Shutdown • Shift Booking: • Open ACR Shifts Booking on about 10 days from now • Some priority to institutes who didn’t get any shifts before

  6. LHC Schedule Update

  7. Backup

  8. Rate Tests Results (Run 208484, 208485)

  9. Occupancy Comparison From Trigger Group: • Quick comparison of the CSC fragment size between runs 208354 and 208485 (both with <mu> ~29)  ~25% reduction (6248 words). • On the other side, 48 words is roughly the fragment size at mu=18 before the change of the readout window size. So naively would have expected that the deadtime at mu~29 with the reduced readout window size should be similar to mu~18 with the larger readout window size which seems not the case… Run 208354 Run 208485

  10. Info from last Muon Week https://indico.cern.ch/getFile.py/access?contribId=3&sessionId=1&resId=0&materialId=slides&confId=194531

More Related