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 142
    • Merge requests 142
  • 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
  • !50609

Closed
Created Feb 18, 2022 by Walter Lampl@wlamplOwner
  • Report abuse
Report abuse

Include Tau Reco into RecoSteering

  • Overview 39
  • Commits 12
  • Pipelines 3
  • Changes 6

Follow-up to !49968 (merged): Include the CA-based Tau-Reconstruction to RecoSteering.py

While testing this, I ran into the following error:

IOVDbFolder 0 0 ERROR Tag CaloH1WeightsCone4Topo-02-000 cannot be resolved for folder /CALO/H1Weights/H1WeightsCone4Topo

Current RecExCommon-based reco doesn't set a folder-level tag but resolves the folder like

INFO HVS tag CONDBR2-BLKPA-RUN2-09 resolved to CaloH1WeightsCone4Topo-RUN2-02-000 for folder /CALO/H1Weights/H1WeightsCone4Topo

Question to @adbailey : Why to we set a folder level tag in the new style tau config?

Edited Feb 25, 2022 by Walter Lampl
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: TauToRecoSteering