Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M MooreAnalysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCbLHCb
  • MooreAnalysis
  • Issues
  • #24
Closed
Open
Issue created Oct 14, 2021 by Ross John Hunter@rjhunterDeveloper

HltEfficiencyChecker: chain HLT1 and HLT2 so we can work out a total HLT efficiency

FYI @rmatev @sstahl @mvesteri @gligorov

This feature has been requested by at least a couple of people now. @mkenzie put it very nicely to me today (quoting):

It's also hard to tell how much better you can do. My Hlt2 line is currently 50% efficient on C.R.C, but Hlt1 is only about the same. So is my line actually 100% on what it will eventually see?

You can get a HLT1 dst and manually filter out those events that fail your HLT2 lines, but it would be good if we could just chain HLT1-HLT2 jobs together in HltEfficiencyChecker, save decisions from both to the tuple and the construct e.g. HLT2 efficiency with an HLT1 line in the denominator.

In principle this doesn't sound too difficult to do, but not sure how much it would break things in practice.

Edited Oct 14, 2021 by Ross John Hunter
Assignee
Assign to
Time tracking