The STAR experiment

For Run-22 offline QA:
From Lanny Ray: 
1. RDO issues happened quite often last week, can be tracked with a unique QA issue number for each instance and can be examined for each RDO
and run number at:https://www.star.bnl.gov/devcgi/qa/QAShiftReport/issueDashboard.php
2. FCS QA continue to look normal.
3. Current offline QA need TPC vertex, but many FWD triggered events do not have TPC information.
   1) Including the FWD tracking can help offline QA.
   2) For FCS, can change to include hits without TPC vertex: plots for events have TPC and events do not have TPC.

From pwg:
1. Run22365106, Vz jumps up, can not find this run in the shift log. -> It is short run, Shift leader should mark each run in the log, even though it is short or failed. 
2. Similar as last week, continue to see TPC Vz - VPD Vz = 4 cm.

For BES-II Data QA by Ashik:
Update the injection run list for 14.6 GeV.

For BES-II data QA:

19.6 GeV:
1. From Dan Cebra: check the bad runlist from last week, divided into 5 major category: 21 are short runs; 16 runs have issues with BEMC (vertex issues); 10 runs are injection runs; 9 runs are junk runs; 39 runs are good, do not see problems from shift-log;
2. Will go through the 81 bad run lists found this week and try to assign to different categories;
3. Injection runs and bad runs lists to be separated in the stbadrunchecker for those who may use it;
4. Will work on 14.5GeV soon.

For Run-22 offline QA:
1. From Lanny Ray: have setup things ready for offline QA shift. 
2. Current offline QA only uses st_physics stream. Forward upgrade data will have separate data stream, and the QA code can take this new stream into the chain.
3. Current offline QA need valid TPC information, but many of FWD data will not have TPC. Gene is working with Akio and Navagyan on the FCS data format and QA code.
4. There is also st_w stream in pp runs, need feedback from ColdQCD group to see if we need QA for st_w stream.

For Run-22 offline QA:
There is about 10 runs from day 349 available for QA:
1. From Lanny Ray: No major QA issues in these first few runs from offline QA shift.
2. From pwg:
      BulkCorr (Ashish): DCA plots seems not very reasonable. 
            Gene: TPC has some distortions that may make DCA shape like this.
      LF (Chenliang): need to change the vertex z cuts to smaller values.
      HF (Kaifeng): use picoDst to do QA, do not see BTOW hits.
            Gene: picoDst production has some problems in BEMC code.             
      JetCorr (Tong): The BEMC Et is problematic, may due to the pedestal and gains issues. 
      ColdQCD (Bassam): working on the code.

BES-II data QA:
1. For 19.6 GeV, find some runs with problematic TPC RDO that is not identified by the code. Suggest to move it out.
2. Dan Cebra will compare the new bad runlist from Ashik and Li-ke, then group them into different categories;
3. The run rejection summary should be in statistic (like how many statistics we loose if reject these runs) instead of the counts of runs;
4. Some of the variables proposed by HF group still need to discussed if they are needed in the QA.

From Lanny Ray: 
1. Offline QA software get stuck this morning.
2. Run 22355023 – 22357011 have excessive hits in various RDOs. Tonko power cycled the TPX FEE’s and that seems to have fixed the issue. This will very likely to affect the track quality. Need to check with TPC expert if we want to mark these as bad or not.
3. Mean dE/dx has been slowly decreasing since the first run e.g.22349015 with MIP at 2.4 keV/cm, which continued on days 351 & 352, but then reduced to more normal values (2.2 keV/cm) on day 353 to the present. Also need to check with expert about the real reason if it happen again.

From pwg:
1. Most of the problematic runs have been identified by offline QA shift, also noted in the shift-log.
2. Vz – vpdVz distribution is shifted by about 5cm. 
3. Vr shifted during the last few runs in day 356.

For Run-22 offline QA:
From Lanny Ray: 
1. RDO 20-3 in runs 364014 and 364023 are not empty of hits but rather appear to have excessive noise, similar to what we saw in Run 21 when the cpu’s for masked RDOs were not rebooted. These two runs need to be looked at by experts to determine if this sector/RDO should be masked in software.
2. The total number of RDOs masked out at this time is 14.
3. FCS plots are now available, but need the instruction from experts about what features to look at.

From pwg:
1. Two spots in Vx vs. Vy: Two different beam line constrain in different time
2. Continue to see that VPD Vz - TPC Vz = -5cm, but seems stable across the runs.