Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • DaVinci DaVinci
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • LHCb
  • DaVinciDaVinci
  • Merge requests
  • !691

Merged
Created May 09, 2022 by Jonathan Edward Davies@jedaviesDeveloper1 of 1 task completed1/1 task

Functionality added to access HLT1 decisions using FunTuple and example options files included

  • Overview 84
  • Commits 34
  • Pipelines 27
  • Changes 6

HLT1 decisions can now be accessed by FunTuple and included in an ntuple

Needs LHCb!3562 (merged), Moore!1580 (merged)

Phys/DaVinci/python/DaVinci/algorithms.py- added block to get_hlt_reports such that HLT1 DecReports can be read in Phys/DaVinci/options/DaVinciDB-Example.yaml- Example dst used for testing added to options

Example options used for testing: DaVinciExamples/python/DaVinciExamples/tupling/option_trigger_decisions.py DaVinciExamples/python/DaVinciExamples/tupling/option_trigger_decisions.yaml

To do

  • Set up unit test to check HLT1 branches specifically (dst and json files exist already)
Edited May 28, 2022 by Nicole Skidmore
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: HLT1reader