1 / 13

Muon piquet report April 3-10, 2012

Muon piquet report April 3-10, 2012. Rolf Oldeman Muon operations meeting Aprl 10, 2012. Last week’s fills with stable beam. Th 5/4 2469 3x3 1h30 RICH timing scan. VELO out 2470 48x48 4h00 VELO/ST timing scan 2471 48x48 2h20 OTscan

keola
Télécharger la présentation

Muon piquet report April 3-10, 2012

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 piquet report April 3-10, 2012 Rolf Oldeman Muon operations meeting Aprl 10, 2012

  2. Last week’s fills with stable beam Th 5/4 2469 3x3 1h30 RICH timing scan. VELO out 2470 48x48 4h00 VELO/ST timing scan 2471 48x48 2h20 OTscan 2472 84x84 4h20 VELO CCscan & 10M TAE for MUON Fr 6/4 2479 264x264 3h00 Bfield OFF. 45M minbias Sa 7/4 2482 264x264 3h30 HLT trouble 2486 84x84 1h30 LHC orbit studies Su 8/4 2488 264x264 4h20 power glitches no ECAL 2489 264x264 4h15 some TELL1’s missing 2490 264x264 1h15 HLT trouble 2491 624x624 10h15 OK with mu=0.8 bare-bone TCK Mo 9/4 2493 624x624 6h20 OK with mu=1.6 bare-bone TCK Tu 10/4 2497 624x624 2:40 OK with mu=1.6 bare-bone TCK

  3. HV raised for some chambers

  4. PAD MAPS Looks pretty good!

  5. Timing M1R1 (GEM) seems early by ~1 bin(1.6ns) wrt reference. Not understood. Otherwise pretty good timing, based on 2011 calibration

  6. Some timing systematics though:

  7. TELL1 firmware • Xavier Gremaud optimized TELL1 firmware for speed to readout M1 @ 1MHz • Also fixed ‘last missing MEP’ bug • But many errors in MUON/L0MU comparison • Julien Cogan’s Tool to debug L0 actually used to debug MUON! • Received v5.0.13 on Tu 3/4: no more errors • In time before stable beams! • Thanks Xavier, Julien

  8. HV trips New Twiki by Oleg:

  9. Hotspot in M3R2 Present for a few fills. Then disappeared spontaneously

  10. Dataquality feedback Offline efficiency calculations indicate low efficiency in M4/M5 First thought to be related to outdated HLT DB with outdated muon positions But hasn’t changed since the HLT DB tag was updated Extensive set of expert histos put on DQ logbook https://lblogbook.cern.ch/Data+Quality/6144

  11. Extra shielding behind M5 • Effectiveness of to be studied in mode detail March 30, short TAE run 110270 3x3 bunches (holes from TELL1bug) April 5, long TAE run 111285 50ns bunch trains ~5xmore afterpulse than real hits? ~same afterpulse as real hits?

  12. DM: what’s that hole in M5? thanks to extra shielding or shorter pulse length?

  13. Does the Alu ‘wall’ help shielding? Two hints: M5C, column A, row 32-27currents Sept 8, 2011 row posgapAgapBgapCgapD 32 front 2.4 2.4 2.4 2.4 31 back 3.8 3.8 2.4 3.0 30 front 2.7 2.5 2.3 2.3 29 back 3.4 3.6 3.2 3.4 28 front 3.0 2.8 2.6 3.0 27 back 3.8 3.4 3.0 3.4 No significant gap-gap difference, But chambers behind wall draw ~30% less current In TAE run, chambers behind wall have ~30% fewer hits than those in front Install a small thin shielding in behind one or two chambers?

More Related