Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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 135
    • Merge requests 135
  • 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
  • !50172

Merged
Created Feb 02, 2022 by Teng Jian Khoo@khooDeveloper

ATR-24839 -- flesh out jLJ thresholds

  • Overview 40
  • Commits 5
  • Pipelines 3
  • Changes 11

Defined additional jLJ thresholds replacing jLJSPARE. For commissioning we retain four thresholds:

  • jLJ80
  • jLJ120
  • jLJ140
  • jLJ180 After commissioning, in production (and for MC sim) we would additionally enable
  • jLJ60
  • jLJ100
  • jLJ160
  • jLJ200 The lower thresholds 60-160 are for support chains, whereas 200 is inserted as an additional backup threshold. As we write all saturated events with J400/jJ500, a jLJ saturation threshold is probably not required.

HLT chains corresponding to the production-only thresholds are added to the MC menu.

FYI @cantel, @ayana, @dzanzi

Coincidentally cleaned up the inconsistent use of 'Main' and PhysicsStream in the Physics menu.

Edited Feb 07, 2022 by Teng Jian Khoo
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master-TMMT-jLJThresholds