Skip to content

GitLab

  • Menu
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 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & 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

Draft: Threshold scan analysis

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Daniel Estrada Acevedo requested to merge feature/threshold-scan-analysis into main Apr 16, 2022
  • Overview 6
  • Commits 19
  • Pipelines 21
  • Changes 3

Description

  • Broken channels were established and saved into a file.
  • Not-readout VFATs [never send hits] were established and saved into a file.
  • Not-fully functioning channels [low number of hits] were established and saved into a file.
  • A report with the fractions of broken, not-fully working, and not-readout channels for VFAT, chamber, and endcap.
  • Plots to display the number of hits in each channel as a function of the threshold were made.

Related Issue

#42.

How Has This Been Tested?

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

gemos analyze thresh inputfiles outputdir [--mappig] [--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 Jun 24, 2022 by Daniel Estrada Acevedo
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/threshold-scan-analysis