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
  • #28

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

Use case: noise comparison

Summary

Optimizing the detector configuration to reduce the electronics noise is crucial to maximize the detection efficency. If the S-curves can be used to extract the electronics noise of a given VFAT channel, we need a tool that allows to compare different configurations. The comparison must be doable for n chambers with m sets of S-curves.

For instance, in the legacy software, the following comparison plots can be produced for every chamber.

image

What is the expected correct behavior?

It must be possible to compare S-curves (but probably also other scans, such as S-bit rate scans). For convenience, it should be possible to assosciate one (or more) symbolic name to every run (i.e. dataset).

Assignee
Assign to
Time tracking