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
  • Issues
  • #42
Closed
Open
Created Mar 11, 2022 by Camilla Galloni@cgalloniOwner

Threshold scan analyis implementation

Description

A csv file with the results of the threshold scan analysis can be found: /afs/cern.ch/work/c/cgalloni/public/4Threshold_scan/ An analysis routine should be developed to do:

  • established the number of broken channels (within their location VFAT - Chamber - Endcap -Total) [no hit]
  • established the number of non-fully functioning channels (within their location VFAT - Chamber - Endcap -Total) [low number of hits] A disjoint development would be the plotting feature:
  • make plots to display the number of hits in each channel as a function of the threshold
Assignee
Assign to
Time tracking