Skip to content
Snippets Groups Projects

introduce a mechanism to exclude specific cuts from subsequent use

Merged introduce a mechanism to exclude specific cuts from subsequent use
krumnack/athena:or_selection into main
Merged Nils Erik Krumnack requested to merge krumnack/athena:or_selection into main

The main usage here is that if OR is run before MET we don't want to use the OR selections with MET. A similar issue is expected to come up with fakes/fakeable objects, i.e. some specific baseline cuts should not be applied (in fact they are inverted), but only for very specific users.

The mechanism chosen here is to mark the cuts when they are registered and then exclude by the attached name when requesting the selection.

cc @ravinab @jmcgowan

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
Please register or sign in to reply