Info

• Cosmic toroid-off run: AMUONRC-277
• Collision toroid-off run: AMUONRC-260
  • Run 325030
    • Start Tue May 30 13:10:57 CEST 2017
    • End Wed May 31 00:32:41 CEST 2017
    • Delivered Lumi (pb-1) 31.5
  • Run 325558
    • Start Sat Jun 03 03:11:43 CEST 2017
    • End Sat Jun 03 12:55:48 CEST 2017
    • Delivered Lumi (pb-1) 30.4
• Mail from Christoph, 2017-06-05:

Hi All,

the toroid-off collision running is over. We got two runs, 325030 and 325558, of about equal size. According to our usual metric, muon events with a track accepted by the HLT with a pT(ID)>10 GeV, we got some 40-50M events, i.e. about twice the amount of data of 2015.

Some complications for data analysis:

Between the two runs the toroids were ramped up to 15 kA (!) and down again. Most likely the detector geometry is not the same before and after.

In run 325030 Pixels had tested some firmware, which caused some desyncs in some regions. They claim the affected region should be in phi about 0°-90°. Plots of HLT rates rather seem to suggest an overall lower efficiency (by ~10%) for linking muon tracks to ID tracks.

For barrel alignment you might want to look for cosmic runs taken in the period between those collision runs. There should be quite a few millions of events for you, though nowhere near 50M. You could maybe consider making a barrel alignment from collision and cosmic tracks combined.

Cheers Christoph

Input samples:

• Cosmic run, cumulated in container: user.giraudpf.data17_cos.JuneCosmicsBoff.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325236.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325255.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325265.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325283.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325275.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325460.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325473.physics_CosmicMuons.recon.ESD.f826
  • data17_cos:data17_cos.00325464.physics_CosmicMuons.recon.ESD.f826
• Collision run:
  • data17_13TeV:data17_13TeV.00325030.physics_Main.merge.DESDM_MCP.f830_m1816
  • data17_13TeV:data17_13TeV.00325558.physics_Main.merge.DESDM_MCP.f831_m1816

Full stat MuonAlignTrk samples:

• Cosmic run:
  • JEDI-11628625
  • user.giraudpf.data17_cos.JuneCosmicsBoff.f826.MuonAlignTrk.noSkim.2017-07-07
• Collision run:
  • JEDI-11628583 and JEDI-11628593
  • user.giraudpf.data17_13TeV.00325030.DESDM_MCP.f830_m1816.MuonAlignTrk.2017-07-07
  • user.giraudpf.data17_13TeV.00325558.DESDM_MCP.f831_m1816.MuonAlignTrk.2017-07-07

Test or buggy samples:

Full sample, 2017-07-04

• Bug found: MDT hit read from amdc rather than GM. Invalid wire positions when as-built parameters are applied
• Cosmic run:
  • JEDI-11596042
  • user.giraudpf.data17_cos.JuneCosmicsBoff.f826.MuonAlignTrk.noSkim.2017-07-04
  • Expiration date set: 2017-08-06
• Collision run:
  • JEDI-11596066 and JEDI-11596072
  • user.giraudpf.data17_13TeV.00325030.DESDM_MCP.f830_m1816.MuonAlignTrk.2017-07-04
  • user.giraudpf.data17_13TeV.00325558.DESDM_MCP.f831_m1816.MuonAlignTrk.2017-07-04
  • Expiration date set: 2017-08-03

Test sample with small stat, 2017-06-26

• Sample user.giraudpf.data17_cos.00325283.f826.MuonAlignTrk.noSkim.testSample.2017-06-26: single cosmic run, limited statistics (--nfiles 400)
  • Size: 6.3 GB
  • Expiration date set: 2017-08-06
• Sample user.giraudpf.data17_13TeV.00325030.DESDM_MCP.f830_m1816.MuonAlignTrk.2017-06-27:
  • toroid-off run, 1 complete run.
  • Bugs: Improper decoding for BMG in countMDTHitsNeighbouringTrack, bug in scatterer surface causing crash for a few jobs
  • Size: 1.3 TB
  • Expiration date set: 2017-08-03

-- PierreFrancoisGiraud - 2017-07-04