The STAR experiment

For Run-22 offline QA:
From Lanny Ray:
  1. Continue to see normal distribution for most of the runs. 
  2. All iTPC sectors were masked out in runs 23029012 and 013. 
  3. In runs 23032041 – 065 TPC sector 8 anode sections 5 and 6 appeared to be at very low voltage. Flemming asked Jeff Landgraf to include TPC plots for 2D ADC and clusters for the online QA shift crew to help them catch such issues earlier. -> Do not have good pedestal for these runs.
  4. sign-DCA have fluctuations -> Gene: Not much improvement can be done to sign-DCA fluctuations at this stage, as it is caused by pile-up tracks.

From pwg: 
  1. About Idx 15: 23026057 To About Idx 35: 23027046, lower values for nSigmaTofPi in JP triggers. -> need to compare with the offline QA, see if problems can be found.
  2. 23029047, low statistics, very short run -> should marked as bad
  3. Continue to see TPC Vz - VPD Vz = 5 cm

For BES-II data QA:
  1. 14.6GeV QA status update:  
    1). Still non-negligible difference between the results from Ashik and Li-Ke.
    2). 14.6GeV data are duplicated on RCF now, so the QA code should be able to use the same data files. -> Suggest Ashik and Li-Ke to run the code over again, so we can get more consistency. 
  2. QA For FXT runs:
    1). some of the dataset is ready.
    2). Run-by-run is on going, need to discuss the software issues for new users.

For Run-22 offline QA:
From Lanny Ray:
  Single run issues:
    1. Run 23037073 all padrows in outer sector 8 appear hot, but the number of hits is reduced. Runs before and after are OK.
    2. Run 23039057 the number of hits in sector 23, RDO/anode 2 are non-uniform and generally low, unlike either an RDO or anode voltage issue and more like a problem with multiple FEEs. Flemming and Tonko discussed this briefly but as it only affected one run there’s not much they can do about it.
    3. In run 23037050 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. -> only st_fwd stream, the st_physics stream is normal.
    4. In run 23035011 there is an enhancement in the number of BTOW clusters from f = -2 to -1 rad.

 For multi runs:
    5. Starting in run 23037042 and continuing to the present, there is an extra spike in the BTOW cluster energy distribution at about 4 GeV.
    6. In run 23038042 the dEdx, TOF and MTD-track matching QA plots are empty. In the past this indicated loss of VPD start time or database issue. 
    7. In the last few days many fastoffline production jobs for st_fwd have seg-faulted causing many runs to have empty QA plots, and therefore no offline QA examination of these data could be done. Some of the crashed jobs are for runs 23039018, 031, 036, 040 and 23040003. Problem persist yesterday. There are likely others. -> Gene checked into the problem, fixed it and today fast offline processing for st_fwd is working well and is beginning to catch up with the QA from yesterday (day 041), but failed jobs from days 039 and 040 remain. Gene stop running the crashing code, it is not fixed yet, but will done soon. Not likely to do the QA for 039 040 again, 

From pwg: 
 1. Some of the problems only see in JP trigger, not in other triggers. Most problematic runs are short runs.
 2. BulkCorr group found that Vz has multiple peaks, very different from what we see weeks ago (See slide3 from Ashish’s report).
 3. Continue to see the offset in |TPC Vz - VPD Vz| ~ 5cm

For BES-II data QA:
 1. For 14.6GeV QA, found runs with 2 RDO that is problematic, that will likely to reject 12M events.
 2. For 3.2GeV QA, it is starting but have not get report ready yet. Will schedule a meeting to discuss the QA details. 
 3. Li-ke and Ashik are doing consistency check, will report next week.

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 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