Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LHCb
  • MooreAnalysis
  • Merge requests
  • !11

Closed
Created Apr 07, 2020 by Ross John Hunter@rjhunterDeveloper1 of 4 tasks completed1/4 tasks
  • Report abuse
Report abuse

WIP: HltEfficiencyChecker for @abrossag use case

  • Overview 11
  • Commits 16
  • Pipelines 7
  • Changes 2

This MR (not for merge at this stage) is to try and use the HltEfficiencyChecker for @abrossag's use case. We want to be able to use the pre-made options file (renamed and put in HltEfficiencyChecker/options/arnau_hl2_example.py) to derive the input files and decay-specific information in order to run HltEfficiencyChecker with HLT2. Thus this MR builds off !10 (closed).

Then we want to add a couple of new tuple tools to the control flow so that @abrossag can do some specialised analysis on the output.

This is a helpful test case for generally using HltEfficiencyChecker with HLT2 lines, and commits made here can be cherry-picked to !10 (closed).

TODO:

  • Get a working decay descriptor
  • Add TupleToolMCBackgroundInfo and TupleToolMCTruth to the control flow
  • Figure out if number of candidates > number of events is a big issue
  • Add a DecayTreeTuple of reconstructed kinematics?

cc @tlatham @mkenzie

Edited Sep 30, 2021 by Ross John Hunter
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: rjhunter-abrossag-hlt2-hltEfficiencyChecker