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
  • #19
Closed
Open
Issue created Jun 23, 2021 by Patrick Koppenburg@pkoppenb🍃Developer

HltEfficiencyChecker should switch to using functors+FunTuple rather than TupleTools+MCDecayTreeTuple

What is the future of tupling in MooreAnalysis? I see development of TupleTools for MooreAnalysis Analysis!604 (merged) while on the other hand we want to remove all TupleTools https://gitlab.cern.ch/lhcb-dpa/project/-/issues/7.

To satisfy https://gitlab.cern.ch/lhcb-dpa/project/-/issues/7, all remaining TupleTools were moved to MooreAnalysis in !55 (merged).

Tupling should be done with FunTuple+functors rather than the outdated MCDecayTreeTuple+TupleTools. Please see discussion below for progress/bottlenecks on this.

cc @rmatev @rjhunter

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