SCAL

SCAL Function Manager

(Warning, important Page still under construction)

Machines used by the SCAL Function manager can be found at: WbmMachines. In short, we have 2 machines involved in fetching, publishing and recording information: one for LHC information (cms-lhcgmt) and another one for Trigger / DAQ one (cms-scalers). Both are controled by a dedicated RCMS machine (cmsrc-scal).

Details and documentation are at the following restricted pages:

Main tasks done by SCAL are related to:

  • LHC real-time information:
    • Retrieve (via the GMT interface)
    • Publish (in DIP)
    • Record (in DB)
    • Detect if beam status changes to/from Stable Beams and create runtime periods in DB
    • Used by DQM, Fill Summary, RTL, Lhc Monitor, Bunch Fill, Current Bunches
  • GT Trigger information (including, but not limited to, Trigger rates)
    • Retrieve (via xmas::las XDAQ Trigger GT interface)
    • Publish (in SCAL XDAQ flashlists)
    • Record (DB)
    • Detect if we stop/start getting data and create downtime entries in DB
    • Add to data stream sent to Tier 0
    • Used by DQM, RTL and WBM Trigger Rates
  • DCS
    • Retrieve status from CMS sub-systems (via DIP)
    • Record such status (in DB)
    • Used by
      • WBM: Last Value, Page Zero, Condition Browser, iPlot, CMS Page 1
      • DQM GUI and RunRegistry
      • Trigger monitoring scripts
  • Luminosity
    • Retrieve luminosity information (via Lumi PC)
    • Record it (in DB)
    • Used by RTL, Fill Report, iPlot

This can be summarized in the following table:

Service Retrieved from Published by SCAL via Recorded by SCAL in Used by Additional info
LHC info GMT DIP OMDS DB DQM, Fill Summary, RTL, Lhc Monitor, Bunch Fill, Current Bunches Detects if beam status changes to/from Stable Beams and create runtime periods in DB
GT Trigger xmas::las XDAQ Trigger GT SCAL XDAQ flashlists OMDS DB DQM, RTL and WBM Trigger Rates Adds to data stream sent to Tier 0. Detects if we stop/start getting data and create downtime entries in DB
DCS DIP, published by each sub-system   OMDS DB DQM and WBM Last Value, Page Zero, Condition Browser, iPlot, CMS Page 1 Used by the WbmDcsWatchdog to raise sound alarms at the control room in case of DCS problems
Luminosity Lumi PC   OMDS DB RTL, Fill Report, iPlot Lumi PC provides online luminosity. Offline one includes additional corrections so lumiCalc2 and pixelLumiCalc will not show the exact same luminosity.

Data Recorded by SCAL and Who Uses It

Click on the data object name to list the contents

  • BeamSpotOnline (x,y,z) position of beam, with widths and errors - used by HLT tracking triggers
  • DcsStatus HV status bits of all CMS subdetectors - used by several detector DQM jobs online and offline
  • L1AccceptBunchCrossing vector of the last n bunch and orbit numbers - synchronization checks by tracker
  • Level1TriggerScalers list of run and current level 1 trigger counters - used by L1 online DQM for rate monitoring
  • LumiScalers current values of the integrated and instantaneous luminosity - used by Lumi online DQM and HLT

In the CMSSW framework, the classes are defined in the DataFormats/Scalers package. Also note the Level1TriggerRates class, a utillity that converts triggers counts into rates. See the link http://cmssdt.cern.ch/SDT/lxr/source/DataFormats/Scalers/interface/ for class definitions.


SCAL Discussion during LS1 and related information

-- KaoriMaeshima - 2018-05-29

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2018-05-29 - KaoriMaeshima
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback