The STAR experiment

From Lanny Ray:

Single run issue:

  1. Run 23049049 decreased number of hits in mid-section of Sector 8, RDO 7

  2. Run 23052056 iTPC sector 13, number of hits very low; ADCs low.

  3. Run 23053023 st_fwd and st_physics data streams, the dE/dx mean is much too high and the ionization energy band resolution is very poor.

  4. Run 23055041, Run with problematic Scalar. Gene investigated and determined that the absence of RICH scalers in the first part of this run prevented TPC distortion corrections from being calculated and caused those st_physics files analyzed by fastoffline QA to fail. The files used for st_fwd QA did have RICH scalers and produced normal QA histograms. These QA analyzed files were taken at about 1000 s into the run.  Gene recommends that the first part of this run, without RICH scaler information, be marked BAD, but the rest are good.

Some general issues:

   Tracking: 

      Starting last week the QA shift crew (Leszek) noticed that the distribution of the number of primary tracks was starting to decrease. Gene constructed a plot showing the trends. This plot confirms Leszek’s observation. The degradation in primary track yield appears in MB, HT and st_fwd XX trigger groups in the QA (see QA issue 18109).

   Vertex Z:

      Primary vertex z-distribution: We checked the fast-offline QA for the dip in PV distributions at z=0 and found that it goes back as far as the QA is still available, about 2 weeks to 20 days. It appears in MB, HT and XX. The MB case was hard to recognize because the usual st_physics stream has very few triggers and PVs in the plots. 

      We note that the global track DCA distributions are broad (from -200 to +200 cm) and peaked near z = 0 as expected, even when the PV distributions dip at z=0.

      Interestingly yesterday’s runs 23055064, 065 with very low ZDC/EPD rates, where sTGC settings were being tested, show normal looking PV distributions.

From different PWG groups:

   1. 23050020-> is laser run, after loss beam. Not any thing physics. 

   2. Continue to see strange multi-peak Vz distributions; located at +-50cm. Also see this from the hlt monitor trigger. Need to ask experts about the real issues.

   3. We see TPC Vz - VPD Vz = 10cm from HF with 45cm vertex cut; TPC Vz - VPD Vz = 5cm from BulkCorr without vertex cut.
 

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: 
  In run 23025052 RDO 11-2 was out, but not completely. The problem went away in run 025053 but returned in 025060, and remained fully masked out after that.
  In run 23027017 RDO 1-8 midpadrows displayed reduced hit number:
  In run 23024003 the dE/dx resolution was poor:
  In run 23022065 there are no TPC hits in the 4 files processed.
  In runs 23023022, 23027046 the BTOF, dEdx and MTD-TPC track matching plots are all empty. Usually this indicates the absence of a good start time for the collision. 
  Starting on Wed. (day 026) the run integrated signed DCA distributions were shifted negative < -0.8 cm.
     -> it maybe calibration issues, but calibration changes happen last week ~Jan. 21, not likely to have big impact on this week.

From pwg: 
 1. For run 23022065, Tof is out of this run, so 0 events with tof requirement.  
 2. JP2 and JP1 trigger ID changes (JP1: 890209 to 890229. JP2: 890210 to 890230), related to the exclusion of the forward detectors from these. 
     -> Gene: For MuDst, see trigger ID for JP2 and JP1: root -l -b st_blah.MuDst.root, then: MuDst.Scan("MuEvent.mTriggerIdCollection.mL1TriggerId.mId[]")
 3. Continue to see Vz - VPD Vz = 5 cm in fast offline QA (same as last week, a mistake in last week’s email).
 4. There is shift observed in <DCA> and pion yields, at the same run 23026056 seen by Bulkcorr group. Shift log says: "TPC sector 17 channel 3 tripped, "clear trip" didn't work. We cleared it manually following the operations from the instruction, worked".
 5. Tong check the QA plots for "890210 trigger for runs 22351048 - 23019026" as asked by Raghav. Not all of the files are available, so it is not very meaningful to report/mark the problematic runs. 
 6. TPC calibration happened on Dec.22, Jan 21. So there maybe something changed after these date. 

For BES-II data QA:
  1. Dan is goring through the final 14.6GeV QA list. 
  2. Data production is going well, will have QA for the other dataset soon.
  3. Li-ke is writing a document about the QA.