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 179
    • Merge requests 179
  • 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
  • !23086

Merged
Created Apr 30, 2019 by Tomas Dado@tdadoDeveloper

AnalysisTop - add BadBatman cleaning option

  • Overview 13
  • Commits 6
  • Pipelines 3
  • Changes 5

This MR adds option to use BadBatman cleaning option via the standard AnalysisTop config file by setting UseBadBatmanCleaning True (it is set to False by default). Additionally BadBatmanCleaningRange XXXX:YYYY is available where XXXX and YYYY are RunNumbers where the cleaning is applied, default is set to 15/16.

The cleaning is applied during the JETCLEAN step and is applied to both EMTopo and EMPFlow jets. The cleaning is applied only to Data.

If the RunNumbers include 2017 RunNumbers, the code throws an error to prevent accidental runs on 2017 data, as this is not recommended.

Closes ANALYSISTO-794

Edited May 01, 2019 by Tomas Dado
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 21.2-AT-BadBatmanVeto