STAR QA Board

["Ting Lin" <tinglin@sdu.edu.cn>]

Hi all:

A brief minutes for today's meeting:
https://drupal.star.bnl.gov/STAR/comp/qa/pwg-qa/run-22-qa

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.

Next Friday is parallel sessions, so we will continue to have QA meeting as 
run is ongoing.

Best,
Ting


> -----Original Messages-----
> From: "Ting Lin" <tinglin@sdu.edu.cn>
> Sent Time: 2022-02-10 14:43:43 (Thursday)
> To: "star-qaboard-l@lists.bnl.gov" <star-qaboard-l@lists.bnl.gov>
> Cc: 
> Subject: QA Board Meeting Feb. 11
> 
> Hi all:
> 
> We will have a QA board meeting on Friday at noon BNL time, 
> https://drupal.star.bnl.gov/STAR/comp/qa/pwg-qa/run-22-qa
> 
> If you have slides to show, please link to the meeting page (in below link) 
> or send it to me.
> https://drupal.star.bnl.gov/STAR/event/2022/02/11/QA-Board-Meeting
> 
> Join ZoomGov Meeting:
> https://urldefense.com/v3/__https://bnl.zoomgov.com/j/1618435669?pwd=L3B6M3JKcjRFMVFxQTNhaEdBdkZ5UT09__;!!P4SdNyxKAPE!XFytYT6Vt2UkGJMhfyU_b3QGxXvNpRQ-ER-FYz_lacsHsIwhRJh5ERcrmdbN8DRS_ki3MF1igUs$
>  
> Meeting ID: 161 843 5669
> Passcode: 194299
> 
> Thanks.
> Ting