Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 196
    • Merge requests 196
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !28173

Merged
Created Nov 21, 2019 by Junpei Maeda@junpeiDeveloper

Bug fix for incorrect BCID from L1MUEndcap to MuCTPI in MC for 21.X (ATR-20569)

  • Overview 8
  • Commits 1
  • Pipelines 1
  • Changes 1

The bug only in MC causes L1MuonEndcap (TrigT1TGC package) was always sending current bunch ID (0 for MC) to MuCTPI, even when detector hits and the candidate decision is calculated for the different bunches. Since Run-2 upgrade, L1MU simulation takes into account the timing and bunch crossing identification for L1Topo LateMuon trigger. Although TGC digitization and TrigT1TGC calculates properly, but sending always fixed number to MUCTPI (0). The bug caused zero count of L1_LATE-MU10_XX in the endcap region (i.e. the current counts is coming from barrel only.)

The compilation, the test script test_mc_pp_v7_build.sh and private MC tests are fine.

The merge request for master (22.x) branch is done here. Please sweep this MR to only 21.X.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 21.xForATR-20569