The STAR experiment

For Run-22 offline QA:

From Lanny Ray:

  1. Run 23042061 TPC Sec. 5 RDO 6 was only partially filled with hits. QA issue # 18095. -> happen several times during Run22. Some minor issues with RDO, started a new run will fix the problem. 

  2. In run 23043075 st_fwd data stream, the dE/dx mean is much too high and the ionization energy band resolution is very poor. The st_physics data dE/dx for this same run are normal.

  3. In runs 230045045 the dEdx, TOF and MTD-track matching QA plots are empty. In the past this indicated loss of VPD start time.

  4. In runs 23043051 and 044033 there is an enhancement in the number of BTOW clusters from f = -2 to -1 rad. -> 043051 is a very short run.

  5. Run 043051 only has 1 file processed so far, while 044033 lists ZDC/EPD AND rates as “-1/-1”. -> A very short run, no samples in the database, will get “-1/-1”. Again, if it is a very short run, SL should mark it as bad.

From Cold QCD:

  1. 10% BEMC multiplicity gradually decreases from 23042001 to 23045006. Also from Run 23045006 To 23045007, there is a jump. It looks like there are several “BTOW configuration failed for crate Id 1. • Had to powercycle iTPC RDO S4:3.” error continues to happen in some of the subsequent runs around that time.

  2. Run 23042056 To 23042057, there is a jump 20% increase of EEMC tower Et. Did not see anything in the run log that might explain what happened.

From BulkCorr & HF:

  1. Continue to see strange multi-peak Vz distributions; do not know what the problem is. We start to see this since last week from st_physics branch.

  2. Also continue to see TPC Vz - VPD Vz = 5cm

For BES-II 14.6GeV QA:

  1. Li-Ke and Ahsik updated the run-by-run QA results with duplicated 14.6 GeV data.

  2. 100 consistent bad runs, Ashik find 5 extra bad runs,Li-Ke find 10.

  3. Total 1470 runs, 369(25.1% of total runs) injection runs excluded, 115 (7.8%) bad runs flagged

  4. Total 651M events, 42M(6.5%) injection runs, 44M(6.7%) bad runs

For Run-22 offline QA:
From Lanny Ray: 
1) On day 018, (last Tuesday) the anode voltages in grid area 5 in sectors 8 – 11 were turned off. This persisted from runs 23018065 – 23019026 as reported with QA issue 18064. Flemming was notified. 
    -> Flemming: There were massive TPC anode crash at that time, voltage disappear, DO have to manually set it up. So lots of confusion at that time, it was set to a wrong value 100voltage?, not zero. 
2) TPC tracking: Run integrated signed DCA were shifted >0 on day 015, then shifted <0 towards the end of day 016, remaining so through early Tuesday (day 018) 
   -> ZDC counts were low at day 015, ZDC scalar is not correctly for a few days. There will be efforts to recalibrate this.
3) TPC tracking: Signed DCA vs run-time variations often exceed 0.1 cm.
4) BTOW: A section of towers were reported out for runs 23016081, 082 by D.O. Daniel Kincses (see left plot below). However, such large scale outages are difficult for the QA shift crew to detect when the histograms are dominated by unmasked, hot towers. -> These hot towers were masked starting on Thursday (day 020). -> It looks like experts mask these hot channels out. This is very helpful for offine QA, will continue to check this.

From pwg: 
1. Run23015034/35/36 has 0 good events, marked as questionable in Runlog: iupsal: TOF HV off, no TOF hits
   -> All the events are good if you are not using TOF data. These runs should show up on the bad-run lists for analysis using TOF. 
   -> Also, run 23015031 only had TOF hits for the first ~10% of the run.
2. VPD vz - TPC vz is now centering around 0
3. day 014 has power dip, so take cosmic whole day.

For Run-22 offline QA:
From Lanny Ray: 
1. On day 008, (last Saturday) iTPC 8, RDO 4 was masked, but possibly without rebooting the processor, resulting in what appears as a low number of hits in several runs, e.g. run 23008086. -> This will be discussed in the TPC meeting. 
2. Run 23009044 had an excess number of clusters for eta < 0
3. On day 012 a new spike appeared at ~5 units (GeV?) in the BTOW cluster energy distribution, e.g. run 23012073. It looks like a new hot towers in BEMC, and it is persist till the latest run.
4. On day 012, one tray in the MTD was masked out in backleg 3, channels > 48, e.g. run 23012073: -> This will be mask out through the run.

From pwg: 
1. Bassam found that some of the MuDst files have IO problem. FCS clustering in the production chain may be the reason (it was took out after day 008, then things look normal). But what happened at 364 is not understood, as FCS options were already included before this date.
3. Continue to see vertex difference TPC Vz - VPD Vz = 4cm
4. The signed DCA has large variations, and there are some small difference in proton mass and kaon mass for the positive and negative charges.-> The space charge is not well-calibrated, this maybe the reason..

For BES-II 14.6GeV data QA:
1. 369 Injection runs(~ 25.2%) excluded and No pile-up rejection
2. 116 bad runs(~7.92%) flagged.
3. A few inconsistencies between Ashik and Li-Ke could be due to uncertain rcf behaviour in reading the events