Muon piquet report April 3-10, 2012

13
Muon piquet report April 3-10, 2012 Rolf Oldeman Muon operations meeting Aprl 10, 2012

description

Muon piquet report April 3-10, 2012. Rolf Oldeman Muon operations meeting Aprl 10, 2012. Last week’s fills with stable beam. Th 5/424693x31h30RICH timing scan. VELO out 247048x484h00VELO/ST timing scan 247148x482h20 OTscan - PowerPoint PPT Presentation

Transcript of Muon piquet report April 3-10, 2012

Page 1: Muon  piquet report April 3-10, 2012

Muon piquet report April 3-10, 2012

Rolf OldemanMuon operations meeting Aprl 10,

2012

Page 2: Muon  piquet report April 3-10, 2012

Last week’s fills with stable beamTh 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 MUONFr 6/4 2479 264x264 3h00 Bfield OFF. 45M minbiasSa 7/4 2482 264x264 3h30 HLT trouble

2486 84x84 1h30 LHC orbit studiesSu 8/4 2488 264x264 4h20 power glitches no ECAL

2489 264x264 4h15 some TELL1’s missing2490 264x264 1h15 HLT trouble2491 624x624 10h15 OK with mu=0.8 bare-bone TCK

Mo 9/4 2493 624x624 6h20 OK with mu=1.6 bare-bone TCKTu 10/4 2497 624x624 2:40 OK with mu=1.6 bare-bone TCK

Page 3: Muon  piquet report April 3-10, 2012

HV raised for some chambers

Page 4: Muon  piquet report April 3-10, 2012

PAD MAPS

Looks pretty good!

Page 5: Muon  piquet report April 3-10, 2012

Timing

M1R1 (GEM) seems early by ~1 bin(1.6ns) wrt reference. Not understood.

Otherwise pretty goodtiming, based on 2011calibration

Page 6: Muon  piquet report April 3-10, 2012

Some timing systematics though:

Page 7: Muon  piquet report April 3-10, 2012

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

Page 8: Muon  piquet report April 3-10, 2012

HV tripsNew Twiki by Oleg:

Page 9: Muon  piquet report April 3-10, 2012

Hotspot in M3R2

Present for a few fills. Then disappeared spontaneously

Page 10: Muon  piquet report April 3-10, 2012

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 sincethe HLT DB tag was updated

Extensive set of expert histosput on DQ logbook https://lblogbook.cern.ch/Data+Quality/6144

Page 11: Muon  piquet report April 3-10, 2012

Extra shielding behind M5• Effectiveness of to be studied in mode detail

April 5, long TAE run 11128550ns bunch trains

March 30, short TAE run 1102703x3 bunches (holes from TELL1bug)

~5xmore afterpulsethan real hits?

~same afterpulseas real hits?

Page 12: Muon  piquet report April 3-10, 2012

DM: what’s that hole in M5?

thanks to extra shieldingor shorter pulse length?

Page 13: Muon  piquet report April 3-10, 2012

Does the Alu ‘wall’ help shielding?

M5C, column A, row 32-27 currents Sept 8, 2011row pos gapA gapB gapC gapD 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?

Two hints: