Reference plots and instructions for shift crew (Current, Official Version)

Attached are critical reference plots for every subsystem with description, instructions on what to look for in every plot and finally what action should be taken.

0 - Experts should do their best to select plots that are independent of the triggers we are running.
1 - Experts should limit their critical plots to a maximum of 4 plots for every subsystem.
2 - Experts should maintain their plots up to date and inform the period coordinator of any updates.
3 - Period coordinator should make sure that the printed hard copy matches the online copy.
4 - Shift crew should closely monitor all of the corresponding plots online.


------------------------------------------------------

Note:
Experts description for every plot should answer the following questions:

1- What the plot is showing?
2- What aberrations to look for in the plot?
3- What to do if there is a problem?


------------------------------------------------------

I'm going to copy the documents below as links here to group subsystems together:

BTOW critical plots (Run 22 and Run 23)

EEMC critical plots (06/08/23)

EPD


eTOF

FCS critical plots (Run 22 and Run 23)

FST (05/06/24)

sTGC (03/30/22)

TOF critical plots (08/23/2024)

MTD critical plots (07/23/2024)

VPD critical plots (01/08/20)


TPC plots and comments (09/18/2024)

Misc advise (01/05/22)

  • Do not only check plots with references, check the entire set of plots (l4 and shift). Even if you don't understand what a plot means you can observe holes in the plot or a plot not filling when it usually does.
  • Check the L0Trg plots (usually) on page 21. If the BBC is not configured the BBC TAC difference plot will be empty. That is: shift > Trigger > Trigger_Detector_Vertex > BBC TAC Difference
  • FST MPV plots only fill at the end of a run, so they'll look empty during it.
  • The GMT plot Shift > GMT > Timing > Sum is empty for some runs and not others. Nikolai said “QA plots can be sometimes empty because the occupancy / statistics for GMT is rather small one." It does not require contacting the expert.
  • Check the TPC drift velocity during laser runs. If it's empty the shift crew/leader likely forgot to check the laser in in run control. A laser which doesn't turn on should be obvious to the DO.
  • The statistics in the drift velocity plot are not very indicative of the number of events recorded. It shows a sampling that can vary run-to-run and will always have far fewer entries than events recorded.
  • Double peaks in the TPC drift velocity plot may not show anything serious. This comes about from the online code which is not the same code used offline. The expert probably can't do anything, but you can note it in the shift log.
  • A hot tower can dramatically change the scale of the BEMC eta phi plot, making almost all channels the same color. This is typical in fact, and not cause for alarm.