The STAR experiment

1) Policy of promising isobar data in FCV abstracts: shall we continue not promise any results from Isobar data until the CME paper is accepted?
- Suggestion from management: we continue not to mention Isobar in FCV abstracts. Results on Isobar can be shown, after approved by PWG, after the CME paper is submitted. 
Conclusions: conveners agree with the proposal from management. Will follow up whether the CME paper will be submitted to arXiv. If so, other FCV results using Isobar data can be presented upon approval after CME paper is submitted. If no arXiv submission, need to wait until the paper is published. 

2) Run22 data: what triggers and rates does each PWG want?

3) Trigger upgrade: feature of cross talk between TOF and BEMC

4) TPC rate improvement for Run23+
- Calculation in the BUR

• 14 weeks with 50 kHz: 10.7 nb^-1 + 20B (5k DAQ rate)
• 34 weeks with 100kHz: 51.9 nb^-1

- Can data taken at 100k be used for MB analyses?
- What physics can we do with 20B+ events?

We are thinking of having a dedicated parallel session in September collaboration meeting on this topic
Conclusions: conveners will discuss 2)-4) in PWG meetings

1) 32 bit vs. 64 bit validation in physics analysis
- pp 510 GeV embedding sample available
-- W- -> e-, with the 64bit setup at Cori: /star/embed/embedding/pp500_production_2017/Wminus2eminus_500_20201502/
--Previous sample produced at RCF (with the 32bit setup): /star/embed/embedding/pp500_production_2017/Wminus2eminus_400_20201502/
- More samples coming: 2016 200 GeV Au+Au , 19.6 GeV Au+Au from BES-I

Conclusions: HF and LFSUPC PWGs will reach out to potential analyzers to carry out the validation work on the Au+Au datasets

1) Tracking efficiency of Isobar data: https://drupal.star.bnl.gov/STAR/system/files/Isobar_efficiency_summary_Jul23.pdf
Conclusions:
- The tracking efficiency is seen to rise from 85% at 1 GeV/c to 89% at 5 GeV/c for MB events when gDCA < 1 cm cut is applied. The rise is largely reduced if using gDCA < 3 cm cut.
- Such a rise originates from the pt-dependent gDCA distribution for tracks in the TPC boundaries. It is observed that the biggest effect is for tracks of 0.9-2.5 GeV/c. 
- The efficiency-corrected yield is mostly flat as a function of azimuthal angle, indicating that the TPC tracking efficiencies at boundaries are well reproduced. A small imperfection at boundaries is seen for 1.5-2.0 GeV/c bin
- Will request a small test sample for tracks between 3 and 10 GeV/c, to check the pt dependence above 5 GeV/c. If the efficiency saturates, the full production will be done with 0-5 GeV/c. 
- No showstopper for full production

2) Isobar blind analysis is completed. RCF nodes and disk space are released to all analyzers. People can run through Isobar data as well.

3) StSpinMaker, StHbtMaker: appear unmaintained and outdated; not needed for data production. Can they be removed from StRoot?
Conclusions: CF and Cold QCD PWGs will discuss whether these classes are used. If it is decided to keep them, a point of contact needs to be provided. 

4) Followup discussion
- Run22 data: what triggers and rates does each PWG want?
Conclusions: 
- Cold QCD: there have been quite some discussions on this topic. Still need to decide what fraction of forward triggers should read out TPC, and whether coincidence triggers between mid and forward rapidities are needed
- FCV: there are interests to take high multiplicity events when the luminosity is low, which is probably at the beginning of the run. Will determine the luminosity range in which such a trigger is feasible. 
- JetCorr: interested in mid-rapidity HT triggers, and possibly some coincidence triggers between mid and forward rapidities
- HF: will discuss whether BEMC and MTD triggers are desired for this run
- More discussions will take place within PWGs

- Trigger upgrade: feature of cross talk between TOF and BEMC
- TPC rate improvement for Run23+. Calculation in the BUR

• 14 weeks with 50 kHz: 10.7 nb^-1 + 20B (5k DAQ rate)
• 34 weeks with 100kHz: 51.9 nb^-1

- Can data taken at 100k be used for MB analyses?
- What physics can we do with 20B+ events?

Conclusions: conveners will continue bringing these for discussion in PWG meetings

1) Data production news

• DAQ production
  • Run17 pp 510 GeV, st_physics: done
  • Run17 pp 510 GeV, st_rp: 65%
  • Run19 AuAu 19.6 GeV: ~170M events available for QA
    • nSigmaPi centers around 0.5 (SLIDES)
    • m2 drops with momentum (SLIDES)
    • Are BEMC and eTOF behaving well?
    • Latest startless T0 calculation not included. Need to add chain option "pppAMode"
    • Need to change "picoVtxVpdOrDefault" to "picoVtxDefault"
• MuDst -> PicoDst
  • Library ready for Run12 pp 200 GeV. Will start at a proper time.
• Data restoration 
  • AuAu_200_production_2016 st_mtd P16ij picoDsts: almost done
  • pp500_production_2017 st_physics P20ic MuDst
    • Do we need to keep MuDst after producing jet tree and reproducing PicoDst?
    • Do jet trees need to reproduced for the entire dataset with updated BEMC calibration?

Conclusions:
- LFSUPC indicates that not ideally calibrated dE/dx is in principle fine for their analyses since analyzers usually determine the center of dE/dx themselves for each bin. However, this could cause issues for other working groups unless they adjust cuts accordingly to compensate the off-center dE/dx. 
- For pp500_production_2017, MuDst files are not needed on distributed disk after jet tree and PicoDst production. The Cold QCD PWG needs to run through the entire dataset to reproduce jet tree. Furthermore, the Cold QCD will investigate whether Lambda trees need to be produced from MuDst, or PicoDst can be used for such studies. Will need to coordinate between MuDst restoration, PicoDst production and PWG tree production. 

2) Run22 trigger requirements from PWG
Conclusions:
- Cold QCD & JetCorr: simulations are being run to study correlations between forward and mid-rapidity, and trigger feasibility.
- HF: propose to have dimuon and HT triggers with similar rates as Run17

3) eTOF running plan: experts will work on eTOF this summer and turn it on during Run22 for a few weeks to test DAQ readout. Plan to do some maintenance work next year, and run eTOF through likely 2025. 

4) Upcoming collaboration meeting: Sep. 13-24
- Parallel session: Sep. 13-17
- Plenary session: Sep. 20-24
Conclusions: i) will use BNL time for the meeting to avoid any confusion; ii) for parallel sessions, it is up to individual working groups to decide whether meetings are held only in the mornings or also including afternoons. 

5) StSpinMaker, StHbtMaker: appear unmaintained and outdated; not needed for data production. Can they be removed from StRoot?
Conclusions: Cold QCD and CF PWGs will follow up on this

6) Add PWG weekly meeting to Drupal (https://drupal.star.bnl.gov/STAR/event)