Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos-analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos-analysis
  • Merge requests
  • !37

Make a routine to analyze the cluster mask rate scan

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Camilla Galloni requested to merge feature/cluster-mask-analysis into main Sep 07, 2022
  • Overview 1
  • Commits 5
  • Pipelines 9
  • Changes 4

Description

MR is prepared and left in draft just in case the format of the masking is decided soon in the firmware. At the moment the masking is implemented as a window of a certain width, starting at some delay (BX units). It seems convenient to implement a mask based on individual delays, since in most of the onto hybrids the scan results favor delays that are not adjacent. Output files for both cases are produced, with plots (optional).

At the moment the pool implementation for making plots in parallel is not working.

Related Issue

How Has This Been Tested?

Output of the analysis of a scan taken in p5 is : /afs/cern.ch/work/c/cgalloni/public/4Laurent/cluster-mask-scan-out-width1-2sigma-2022082604

fed1467-slot1-oh2

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
Edited Sep 09, 2022 by Camilla Galloni
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/cluster-mask-analysis