Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T ttbbRun2Bamboo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Sebastien Wertz
  • ttbbRun2Bamboo
  • Merge requests
  • !38

Only flag relevant sub-processes (ttB) as signal

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Sebastien Wertz requested to merge signal_subprocesses into master May 19, 2021
  • Overview 1
  • Commits 1
  • Changes 2

As mentioned in !37 (merged) , it would be better to only flag the ttB sub-process as signal, to avoid producing (in principle empty) migration matrices for ttcc and ttjj.

I've added in the sample configs a list of subprocesses to be flagged as signal. The is_signal flag is then inserted when filling in the sample template.

If you work with the insertSamples.py script instead of the --samples argument of the plotter, don't forget to regenerate the sample list.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: signal_subprocesses