PHS#
Physics PbPb runs#
Monitor if plots are not empty and timestamps are updated.
If plots are empty or not updated please inform the on-call.
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 expert is not informed yet. If PHS is not busy but you see this message then inform the on-call.
If you see other red messages please check known issues. If issue is not known please inform the on-call.
[QC on QC merger node] Global PHS quality#
Good plot:
The plot summarize PHS quality. If global quality is not good then please check below the details.
-
Number of cells increases
assures that digits are being produced. If bad then follow the procedure aboveIf you see "Number of entries has not changed in the past cycle"
above. -
Number of clusters increases
assures that clusters are being produced. If bad then follow the procedure aboveIf you see "Number of entries has not changed in the past cycle"
above. -
Cells check
assures that cells occupancy is good. If not good then checkCells HG occupancy
plots and follow the instructions. -
Clusters check
assures that mean cluster energy size is within allowed limits. If not good then please inform the on-call. If medium - put a log entry and inform the oncall during morning and afternoon shift. No need to call during night. -
Errors check
assures that occured number of errors is within limits. If 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.
[QC on QC merger node] Global quality trend#
Good plot:
The trend shows evolution of global PHS quality. It can become medium for small portion of cycles due to failure of fit procedure. In this case run to be considered as good.
If the trend is not good for significant part of the run then run quality must be setted to bad. Put bad flag even if issue is known. Expert will have a look and adjust the qaulity later if needed.
[QC on EPN] Error occurance#
Good plot:
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.
[QC on EPN] Cell HG occupancy in M1, 2, 3, 4#
Please check known issues
Good plots: The plots represent number of cells seen in each channel. It should be more or less uniform.
If red messages say Not OK then put log entry and inform the oncall. Note that messages can be false positive. If you think the plots are not different too much from reference then just put log entry, no need to call during night. If they are differ too much (big empty/hot regions, etc.) then call the on-call. Please do not hesitate to call the on-call if you have any doubts: it's better to wake up us at night than loose data!
Actions to be taken by QC shifters#
-
Minimal duration after SOR before taking any action required by these instructions: 5 min at 500 kHz.
-
Follow the instructions above.
Known issues#
- COSMIC, TECHNICAL, PHYSICS_PP runs Cell HG occupancy, mod[1-4]: white horizontal stripes can be seen which differs from the reference plots. QC shifter can ignore these patterns, because they are caused by dynamic FEE mask which is changed by the PHOS experts without prior notice. Only completely empty plots should be reported by the QC shifter to PHOS/CPV on-call
- COSMIC, TECHNICAL, PHYSICS_PP runs Cell HG occupancy, mod1 shows missing data in the area x=(32,47);z=(0,27) since end of March 2023. This is a known issue and is being investigated by PHS experts. No need to report it in the QC EOS reports and no calls to PHS/CPV shifters are needed.
- COSMIC, TECHNICAL, PHYSICS_PP runs. Sometimes QC shifters report on the error message in EPN infoLogger: Trailer decoding error: Last RCU trailer word not found. These errors are persistent, they appear in all COSMIC, TECHNICAL, PHYSICS runs since the beginning of Run3, and caused by a bug in SRU firmware. All these errors should be ignored.