Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 198
    • Merge requests 198
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !22788

Merged
Created Apr 18, 2019 by Scott Snyder@ssnyderDeveloper

TrigT1Monitoring: Fix use of HVScale conditions object.

  • Overview 3
  • Commits 1
  • Pipelines 1
  • Changes 2

The data in the HVScale conditions object is different from that gotten from the old tool in that the scales in the conditions object have been divided by the online scale values. L1CaloHVScalesMon was using the unnormalized scales, so convert back.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: hvcorr.TrigT1Monitoring-20190418