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 |
---|---|
- 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 |
---|---|---|
- 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 |
---|---|
- 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 |
---|---|
- One peak should be visibile for all supermodules around 0 if EMCAL is in data taking.
- If the peak moves to the range 20-50 "Min raw amplitude (ADC)" for any supermodule, or a second peak appears for any supermodule in that range , 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 |
---|---|---|
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#
- 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#
- 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.
Number of triggers per Time Frame#
good quality | bad quality |
---|---|
Trigger rate appox. const with minor fluctuations | Trigger rate dropping by several events / timeframe or to almost 0 |
The number of triggers per Time Frame must stay constant while the run is ongoing. In case the number of trigger decreases call the EMCAL on-call (for technical and cosmics runs not during the night). The correct value will depend on the interaction rate and a checker will be implemented soon; for the moment please inform the oncall on case of changes during the run.
Known issues#
-
Do not call EMC oncall during the night for QC plots related errors for non PHYSICS runs, unless a PHYSICS run is expected next.
-
For the plot "Number of Physics triggers per timeframe" the expected value is currently approx 20. If value is below 15 for at least 2 consecutive timestamps, call on-call.
-
Payload Size/Event can be ignored in all runs till further notice
-
In plot "Raw data errors" (error rate) quality is bad if the rate is above 100 errors / minute for several minutes, and good if it is below.
-
An empty region is expected near the bottom-right corner for CAL (Calibration) triggers.