The STAR experiment

For Run-22 offline QA:

 1). Run 23098061 – iTPC 20 completely out:

 2). Run 23098063 st_fwd – has no TPC hits in events from the 4 files processed. St_physics data stream not available.

 3). Runs 23100025, 23100049, 23102014, 23104003 st_fwd, 23104004 st_physics, - large number of missed MTD-TPC track matches.

 3). Run 23104052 st_physics has very few primary vertices, relative to the total number of HT triggers. The st_fwd data stream is normal.

     -> It looks like beam was lost, but keep taking data. Most of that time there was no beam, the rich scaler is not there.

 4). eTOF QA plots appeared in several runs. All plots were empty. These were, for example in runs 23102056, 23104036, 23104050, 051

     -> eTOF group is doing some test. Geary and Norbert taking on the control, so eTOF do appear in the daq sometimes.

 5). Run 23098035 had several new BTOW spikes and energy clusters.

From different PWGs:

 1). Jump in from ~ idx 223: 23101064 to ~ idx 264: 23102068  

  -> ETOW: configuration failed -- watch ETOW triggers or restart run. " and ETOW: failed crate Ids: 2

  -> ETOW was taken out of the trigger chain starting from run 23102018 and it was brought back in run 23102019.

    In general, a lower when compared to last week.

 2). Run23097054, bToFMult drop, no information for this run in Shiftlog.

     -> see unusual low number of reconstructed events compared to HT from offline QA;

     -> 5mins short run.

 3). Due to the THUB problem, there is no VPD West hits, so VPD Vz also not available.

Please pay attention to Gene's list of questionable runs, and check if some of these runs are already in the list of your Run-22 QA list.
 

For Run-22 offline QA:

 1). Runs 23095006 – 23095038, 23096064: MTD was out of run 

     -> One of the MTD software is not running properly 

 2). Runs 23095006 – 23095052 (all day 95): BTOF was out of run Run 23095030 has no TPC hits and could not be examined. 

     -> one of the THUB failed 

 3). Run 23096027 was very short; poor dE/dx resolution and low mean value. 

 4). Run 23097011 – no dE/dx, 1/b or MTD-TPC track matches

     ->  there is dE/dx cut used for MTD-TPC match, so if dE/dx is not there, then it will cause the problem.

 5). Runs 23096049 st_fwd, 23096063 st_physics and st_fwd, 23097012 st_fwd, and 23097073 st_fwd had an excessive numbers of missed MTD-TPC track matches.

From PWG:

 1). Also confirm that TOF information is missing for runs between 23090032 to 23091074, and also 23094049 to 23095052;

     -> TOF was taken out due to THUB current issues.

 2). vpdVz info not available for runs after 23091005, it is set to -999.0

     -> also due to THUB problem. 

 3). Continue to see double vz peak.

 4). TPC Vz - VPD Vz = 5cm

 5). See jump in BEMC tower multiplicities from 23089039 to 23089043 and also 23094049 to 23095006

 6). See fluctuations in the Eemc tower multiplicities.