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 3
    • Merge requests 3
  • 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
  • !35

Threshold scan analysis

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Daniel Estrada requested to merge feature/threshold-scan-analysis into main Apr 16, 2022
  • Overview 20
  • Commits 1
  • Pipelines 35
  • Changes 2

Description

This MR aims at implementing an analysis routine for the threshold scan. In particular, the following features are implemented:

  • Non-working channels are identified and saved into a file (distinguishing between broken channels and the channels from a not readout VFAT).
  • A report with the fractions of working, broken, and not-readout channels for each FED and OH is printed on the console.
  • 3D histograms are made to display the number of hits for each channel as a function of the threshold.

Related Issue

Fixes #42 (closed).

How Has This Been Tested?

The current code thr_scan_analysis.py can be used through gemos command.

gemos analyze thresh inputfiles outputdir [--mapping] [--plotting]  

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 Oct 28, 2022 by Laurent Petre
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/threshold-scan-analysis