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

Closed
Open
Created Jun 03, 2020 by Andrew Michael Levin@anlevin

Asymmetric error bar calculation

Following up on https://gitlab.cern.ch/cmsgemonline/gem-online-analysis/-/issues/15#note_3503273, we should try to use statistically meaningful error bars when handling scurve and possibly other types of data. In ROOT there is a dedicated class

https://root.cern.ch/doc/master/classTEfficiency.html

with many options (which are probably not relevant for our purpose).

From a quick search of scipy

https://docs.scipy.org/doc/scipy/reference/search.html?q=efficiency&check_keywords=yes&area=default

I don't see anything similar, but it could of course be there without "efficiency" in the name.

Assignee
Assign to
Time tracking