ROS Monitoring Histograms


All the ROS Monitoring histograms are defined and filled inside the file ROSMonSCT.cxx, that is of course part of the SctRosMonitor code. They can be divided into four categories:

  • SCT ROD Errors
  • SCT ROS Errors
  • SCT MOD Occupancies
  • SCT ROS Occupancies

The SCT ROD Errors histograms contain informations about all the possible errors that can occur on the ROD level, while the SCT ROS Errors histograms contain informations about the errors occurring in one ROS (corresponding to 11 or 12 RODs).
The SCT ROS and MOD Occupancies contain informations about the number of hits recorded by an entire ROS (~528 modules) or by a single module. The Occupancy plots are filled two times, once with "simple" hits (in the code are called "remain"), and once with coincidence hits (called "coinc" in the code). The coincidence hits are identified by a very simple algorithm (opposite side +/- 128 Strips).

All the histograms are published for all the 8 indipendent ROSs that are inside the SCT:

  • BA-00
  • BA-01
  • BC-00
  • BC-01
  • ECA-00
  • ECA-01
  • ECC-00
  • ECC-01

Error Histograms

ROS Level














ROD Level

Occupancy Histograms

ROS Level


Called m_sum in the code, this histogram contains the number of hits vs the module number. The module numbering is ROS internal, but the conversion to the other coordinates systems is available on

occ_time (m_sum_time)

This histogram contains the total number of hits in the ROD vs time (expressed in seconds). It is a rolling histogram, in the sense that all bins are periodically (every four hours?) rolling from right to left. In each moment, the total number of bins is 2^14=16384 (in the code you will see 1<<14), enough for the 14400 seconds that are contained in 4 hours.

occ_evt (m_sum_evt)

This histogram contains the total number of hits in the ROD vs the event id. This is also a rolling histogram, but it has some specific problems due to the number of bins. Since we have more than one event for second, 2^14 bins are not enough, and we need to have 2^16. With so many bins the histograms is too heavy to be presented in OHP, and for this reason we decided to create the following histogram.

occ_thr_evt (m_thr_evt)

This histogram is filled with the total number of hits in the ROD ONLY IF the number of hits per single module is greater than 384 (this corresponds to 25% of occupancy, number oh hits in a module divided by the nominal number of chips). In other words, only the module with an occupancy greater than 25% contribute to this histograms. On the x axis we still have the events, but they are no more identified by the event id because our goal was exactly to reduce the number of bins not considering all the events, but only the ones containing at least one module with more than 25% occupancy. On the x axis we will have then just an integer initialized to the event id of the first event plotted and growing

occ_la1 (m_sum_l1a)

occ_bci (m_sum_bci)

bci_time (m_bci_time)

max_mod (m_max)

nmaxmod_time (m_max_time)

evt_time (m_evt_time)

evt_bci (m_evt_bci)

avg_time (m_avg_time)

max_time (m_max_time)

Module Level






OHP Histograms

-- EleonoraBenhar - 28-Mar-2011

This topic: Sandbox > TWikiUsers > EleonoraBenhar > EleonoraBenharSandbox
Topic revision: r8 - 2011-05-16 - EleonoraBenhar
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