Skip to content

CPV#

Technical runs#

If you see "Number of entries has not changed in the past cycle" but run is still ongoing then most probable reason is that PHS bacome busy. You can check with ECS shifter and inform the on-call if he is not informed yet. If PHS is not busy but you see this message then inform the on-call.

Message "Cold (hot) 3G cards (N/X)" is tolerated if plots look like reference.

Good plots: alt text

The plots represent number of digits seen in each channel. It should be more or less populated. In case when it is very different from reference please inform CPV on-call.

[QC on EPN] Error occurance#

Good plot:

alt text

If plot is not OK then put a log entry and call the oncall during morning and afternoon shift. No need to call at night if there are no other issues. No need to put bad flag for run if there are no other issues.

Minimal duration after SOR before taking any action required by these instructions: 10 min

  

EMC#

Don't call EMC expert during the night if run is not physics

[QC on FLP] Error Type for SM (Super Module)#

Green: good quality Red: bad quality
ErrorTypeOK ErrorTypeError
  • If no entries, a green message "No Error: OK" inform you that everything is working properly.
  • In case of errors, a red message will appear: EMCAL oncall should be informed if EMCAL is in global runs and if it is not during night shift. Take note of the error-type in the y axis.
  • If the errors appear during nigh shift:
  • add a note in the logbook, don't call the on-call.
  • in case LHC is preparing for collisions the on-call should be notified at "Prepare Ramp" (even during the night in this case) in case of such errors occur in a technical run before, so that the cards can be recovered before taking physics data.

[QC on FLP] Payload Size/events#

good quality bad quality empty
PayloadSizeEvOK PLEvError PLEvempty
  • If "Data OK" is shown, everything is fine.
  • If some of the DDL presents entries that are larger than the others, a red message will appears: please call EMCAL oncall.
  • If the plot is empty, and EMCAL is included in the data taking, call EMCAL oncall.

[QC on FLP] FECidMaxChWithInput_perSM#

bad quality empty
FECerror FECempty
  • If "Data OK" is shown, everything is fine.
  • If a FEC is noisy (not uniform distributions) please call the EMCAL oncall.
  • Ignore the red messages: they are not yet tuned for data.
  • If the plot is empty, and EMCAL is included in the data taking, call EMCAL oncall.

[QC on FLP] Bunch minimum amplitude EMCAL+DCAL#

good quality bad quality empty
BunchOK BunchError BunchEmpty
  • One peak should be visibile if EMCAL is in data taking.
  • If a second peak appears around "Min raw amplitude (ADC)" in the range 20-50, call EMCAL oncall
  • If the plot is empty, and EMCAL is included in the data taking: please call EMCAL oncall

[QC on EPN] Cell Occupancy plots (PHYS) for E>0.2 GeV and E<0.2 GeV and Cell Occupancy plots (CALIB) for E>0.5 GeV#

good quality good quality bad quaity
OccEabove OccEbelow OccErr

IF PHYSICS RUN - The occupancy plots should be uniformly filled during Physics runs.
- if something noisy appears, please call the EMCAL oncall. - If the plot is empty, and EMCAL is included in the data taking, call EMCAL oncall.

IF CALIBRATION RUN monitor: Digit Occupancy plots (CALIB) for E>0.5 GeV - it should be uniformly filled during Calibration runs.
- if something noisy appears, please call EMCAL oncall.

[QC on EPN] Cell Amplitude#

DigitAmplitude

  • no instructions for the moment.
  • If the plot is empty, and EMCAL is included in the data taking, call EMCAL oncall.

[QC on EPN] Cell Time#

DigitTime

  • If the plot is empty, and EMCAL is included in the data taking, call EMCAL oncall.
  • If the errors appear during nigh shift:
    • add a note in the logbook, don't call the on-call.
    • in case LHC is preparing for collisions the on-call should be notified at "Prepare Ramp" (even during the night in this case) in case of such errors occur in a technical run before, so that the cards can be recovered before taking physics data.

  

FDD#

In the global TECHNICAL runs the FDD HV is set to 0 V. Zero counts is expected.
No online QC is provided.
Actions:
- None.

  

FT0#

In the global TECHNICAL runs the FT0 HV is set to 0 V. Zero counts is expected.
No online QC is provided.
Actions:
- None.

  

FV0#

In the global TECHNICAL runs the FV0 HV is set to 0 V. Zero counts is expected.
No online QC is provided.
Actions:
- None.

  

HMP#

Busy time#

[QC on FLP]busy_time

The plot shows the busy time of the detector. In case more than three equipments exceeds 120 microsec or the plot is empty call HMP on-call

Event size#

[QC on FLP]event_size

The plot shows the busy time of the detector. In case more than three equipments exceeds 13 kB or the plot is empty call HMP on-call

  

ITS#

General considerations#

If any of the plots listed in this page remains empty during a run, please call the ITS on-call.

Fake-hit rate overview#

[QC on FLP - plot integrated over the run]its_t1 Overview of the fake-hit rate for all ITS staves. In the case of entries, the fake-hit rate is displayed with the colored scale in hits/event/pixel for every stave. For the technical run, this plot is expected to stay empty. Please call the ITS on-call if you see any entries.

Trigger count vs TriggerID and FeeID#

[QC on FLP - plot integrated over the run]its_t2 Plot summarizing trigger flags. The colored scale represents the counts in each bin. The normal plot is shown on the left panel, while the problematic one is depicted on the right. QC can plot the following error messages:

  • Quality::GOOD
  • Quality:: BAD: Trigger flag (TRIGGER_NAME) of bad quality

Call the ITS on-call in the case of BAD quality messages and also in the following cases:

  • there are x-bins without entries (i.e., vertical white lines on the plot)
  • entries are present in the empty lines in the example plot above.
  • the plot is completely empty

Payload size vs FeeID#

[QC on FLP - plot integrated over the run]its_t3

Plot showing the payload size of every link (FeeID). Values on the y-axis must be like in the plot or all identical to each other. QC will provide the following data quality messages for this plot:

  • Quality::GOOD
  • Quality:: BAD: Payload size too large for technical runs
  • Quality:: BAD: Payload size is missing for some FeeIDs

Call the ITS on-call in case of BAD quality messages or plot will differ from the provided example.

  

MCH#

Quality Summary#

[QC on EPN]mch-qualitysummary

The left panel show a summary of the automated checked on the MCH data, in a human-readable format. The top line describes the aggregated quality status, followed by a message suggesting the appropriate action according to the quality level: * Bad: immediately inform the MCH on-call * Medium: write a logbook entry, tagging MCH * Null: the plots are completely empty. Check in DCS if MCH is in STANBY. If not, inform the MCH on-call.

The right panel shows a trending plot of the aggregated quality. The message in the left panel always corresponds to the most recent point in the trending plot.

If the quality in the trend plot is Bad for the whole duration of a run, MCH should be marked as Bad in the Bookkeeping flags for the run.

Quality Plots#

The following plots show the distribution of various estimators of the MCH data quality. Each horizontal bin shows the value of the monitored quantity, averaged over one Detection Element(DE). The vertical dashed lines show the boundaries between each of the 10 MCH chambers. An horizontal dashed line shows the threshold used by the checker to decide if a given detection element is considered good or bad.

The checker assigns an overall Good (green), Medium (orange) or Bad (red) quality flag to the plot, depending on the number and pattern of bad DEs. In general, the quality is still considered Good if only few DEs are bad. The quality is set to Medium if several DEs are Bad, but no significant impact on the detector acceptance is expected. If the number and pattern of bad DEs is such that the acceptance will be degraded, the quality is set to Bad.

The overall aggregated MCH quality is the logic AND of the qualities of the individual plots.

Fraction of Synchronized Boards#

[QC on EPN]mch-syncfrac

The plot shows, for each Detection Element, the fraction of FEC boards that are properly synchronized. A given DE is coinsidered bad if the corresponding fraction is below the horizontal dashed line.

Fraction of Boards not in Error#

[QC on EPN]mch-noerrorfrac

The plot shows, for each Detection Element, the fraction of FEC boards that do not have decoding errors. A given DE is coinsidered bad if the corresponding fraction is below the horizontal dashed line.

Fraction of Boards with Good Rate#

[QC on EPN]mch-goodfrac

The plot shows, for each Detection Element, the fraction of FEC boards that have a correct hit rate. A given DE is coinsidered bad if the corresponding fraction is below the horizontal dashed line.

Average Hit Rate#

[QC on EPN]mch-meanrate

The plot shows the average hit rate (in kHz) for each detection element. A given DE is coinsidered bad if the corresponding rate is below the horizontal dashed line.

  

MID#

Local boards occupancy map (DigitsQC)#

[QC on EPN]mid-locboard

The plot shows fired local Boards. In case of :

  • empty column.

  • empty or very high rate on several neighboring boards of the detector.

    call expert in case of PHYSICS or COSMIC run

Hits multiplicity (DigitsQC)#

[QC on EPN]mid-hit-mult

These plots show hits multiplicity by plane for bending and non-bending

  • if mean value > 100.

    call expert

  

PHS#

Technical runs#

Monitor if plots are not empty and timestamps are updated.

Ignore any red messages except "Number of entries has not changed in the past cycle".

If you see "Number of entries has not changed in the past cycle" but run is still ongoing then most probable reason is that PHS bacome busy. You can check with ECS shifter and inform the on-call if he is not informed yet. If PHS is not busy but you see this message then inform the on-call.

[QC on EPN] Cell HG occupancy in M1, M2, M3, M4#

Good plots: alt text

The plots represent number of cells seen in each channel. It should be more or less populated. In case when it is very different from reference please inform PHS on-call.

[QC on EPN] Error occurance#

Good plot:

alt text

If plot is not good then please inform the oncall. If medium then put a log entry and inform the oncall during morning and afternoon shift. No need to call at night if there are no other issues. No need to put bad flag for run if there are no other issues.

Minimal duration after SOR before taking any action required by these instructions: 10 min

  

TOF#

Ignore alarms if TOF is not READY

Readout map (Slot Participating)#

[QC on FLP - plot integrated over the run]

slotpart_good

The plot shows a map of TOF readout slots per crate. The checker controls if enough crates are in the readout, if it detects lower than expected the quality is set to BAD. In case of red allarm please call TOF oncall.

Hit Multiplicity#

[QC on EPN - plot integrated over the run]

hit_multiplicity_good

The plot shows the number of hits detected by TOF, a checker provides instructions for the shifter based on measured counts. ~~In case of yellow allarm please contact TOF on-call via email, in case of red alarm call TOF expert.~~

  

TPC#

TPC Technical#

[QC on EPN] rawDig_nClusters To be checked:

  • The time stamp at the bottom should update every two 2 minutes during running.

  • When run is ongoing all Qualities in the list should be GOOD after 3 update cycles (6 minutes). In case of a bad quality put log entry.

  • If in the quality trending, the quality is constantly BAD for multiple cycles (>10 minutes) call On-Call.

  • In case the Raw task quality is bad you can check if there are holes in the N RawDigits plots and call On-Call.

  

TRD#

Experts will check quality of technical runs

  

ZDC#

General considerations#

If any of the plots listed in this page remains empty during a run, please write a mattermost message to the ZDC on-call

  • Typical Data Rate: 54 MB/s
  • Run duration: To manually stop
  • DCS state: SS

This run will not create any object in the CCDB.

Alignment#

[QC on FLP] alt text

A plot related to a good calibration will have every channel aligned to sample 6 like in the picture. Otherwise it will be considered bad, as in the picture below.

If this plot is empty or shows an error, please write a mattermost message to the ZDC on-call. Please remember that this plot must not have empty channels, the only good output is the one in the picture. Below is an example of bad plot. alt text

Baseline Summary#

[QC on FLP] alt text

This plot is self-checking, just look if the run number is correct and the status is OK as in the picture above.

If this plot is empty or shows an error, please write a mattermost message to the ZDC on-call. Below is an example of bad plot.

alt text

Raw Data Error#

[QC on FLP] This plot should always be empty, if at the end of the run there are entries please write a mattermost message to the ZDC on-call. Please remember to check the run number at each run.

Example of good plot: alt text

Example of bad plot: alt text

Rate#

[QC on FLP] zdc_rate_good

A good plot will have every channel at (4.0+-0.2) KHz. If any channel does not respect that please write a mattermost message to the ZDC on-call. Please remember to check the run number at each run.

Example of bad plot: zdc_rate_bad