Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 29
    • Issues 29
    • 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
  • #30

Closed
Open
Created Oct 25, 2020 by Laurent Petre@lpetreOwner

Use case: channel loss monitoring

Summary

The S-curves allow extracting the noise of a given VFAT channel. When a VFAT channel is damaged after a propagating discharge, its noise level changes significantly, it either drops close to 0 fC or increases. One must be able to detect changes in noise across runs and automatically detect input channel damages.

Typically, a S-curve scan is taken daily and compared with the one from the previous n days. Then, summary plots are provided for extend periods of time that can span over years.

What is the expected correct behavior?

It must be possible to automatically compare the noise levels between S-curves and detect damaged channels. The evolution of the number of dead channels over long periods of time must be easily accessible to the end user.

Assignee
Assign to
Time tracking