Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 168
    • Merge requests 168
  • 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
  • !49632

Merged
Created Jan 13, 2022 by Magnar Kopangen Bugge@mkbuggeContributor

Add calo-tagging working point based on CaloScore NN-based discriminant

  • Overview 17
  • Commits 6
  • Pipelines 4
  • Changes 3

This MR adds the possibility to use the new NN-based calo-tagging in MuonSelectionTool. A new property is added, "UseCaloScore". The default value for now is false, in which case the old CaloMuonIDTag variable is still used, and the Loose working point is unchanged wrt. the current version. When the property is set to true, the selection of calo-tagged muons for the Loose working point is based on the CaloScore variable, using the so-called "WP4" working point from here. This working point was constructed to achieve a flat rejection of fakes across pT by a pT-dependent cut on the discriminant. (Rejection is here defined in terms of a fraction of reconstructed candidates passing the discriminant cut.)

The performance of the working point will be further evaluated using new mc20 samples with increased statistics, and it is not unlikely that the precise cut definition will change. We decided to merge this now in any case to put into place the technical setup so that only the cut itself needs to be changed later.

I noticed that the current implementation extracting the CaloMuonIDTag variable would silently reject muons in the case of the variable missing, so I promoted the corresponding message from VERBOSE to WARNING and allowed this to be printed also in the case of an exception caught. (And then I used the same setup for CaloScore as well.)

Tagging @mvanadia , @gabarone , @yoyamagu

Edited Jan 13, 2022 by Magnar Kopangen Bugge
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: master-addCaloScoreWP