The STAR experiment

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)

1) Look for PWG helpers for TPC-related tasks: LIST
Conclusions: conveners will bring this back to PWG for discussion, and look for volunteers. 

2) Data production for Run19 19.6 GeV 
- Shifted dE/dx due to its time-dependence. An ad-hoc fix is in DB. QA is ongoing.
- No BemcPidTraits in PicoDst due to that BSMD information is not present. BSMD was not included in data taking. 
- No BEMC tower energy, but ADC values are available which can be used to be converted to energy in analysis code. Is it critical to fix this in PicoDst?
- Aim for Monday to restart the 19.6 GeV production
Conclusions: fixing the issue of wrong BEMC tower energy in the PicoDst is not critical for this dataset. If the BEMC experts can fix this before other issues are resolved, this is great. Otherwise, the production can proceed as it is in this regard.

3) MuDst->PicoDst production priority (Priority list)
Conclusions: JetCorr PWG will discuss whether Run12 pp 200 GeV PicoDst production is urgently needed. If not, Run10 AuAu 200 GeV production can proceed first, which does not require restoration of MuDst files from HPSS. Currently, PicoDst production for Run17 st_physics is placed at 4th priority. However, its priority will be bumped up if the corresponding MuDst files on distribution disk need to be removed, which also serve the purpose of jet tree production for Cold QCD PWG. 

4) Upcoming collaboration meeting: Sep. 13-24
- Parallel session: Sep. 13-17
- Plenary session: Sep. 20-24

Proposal page: https://drupal.star.bnl.gov/STAR/blog/ashik/quark-coalescence-and-directed-flow-auau-collisions

Proposal page: https://www.star.bnl.gov/protected/lfsupc/bkimel/3GeV_pi_K_p_spectra_paper/

1) Look for PWG helpers for TPC-related tasks: LIST
Conclusion: will confirm with a potential helper for item d). This left us with still item c) to identify a helper. 

2) Documentations of GPC discussion and make them available during collaboration review
- BNL mailing list needs subscription to be visible
Conclusion: conveners agree that PAs should document GPC comments and their replies, and link them to the paper webpage. It was suggested to upload these documentations to analysis note page, and have GPC chair approve them before collaboration review. Mattermost was brought up as a central place for GPC communications, but many others prefer emails. Rongrong will bring up this point for discussion during collaboration meeting. 

3) Cold QCD disk space request (PWG_TASKS)
- Run12 & Run13 pi0 tree: 6.5T
- Run17 jet tree: 18T
Conclusion: both requests need about 2-3 years to finish planned analyses. ~6T disk space will be allocated to Cold QCD to be split between the two requests. Once the CME data (~45T) are backed up on HPSS and removed in a couple of months, we should have sufficient space to accommodate both requests. 

4) Upcoming collaboration meeting
- Speakers for PWG reports
- Inputs to management-convener meeting

AOB
Conclusion:
- LFSUPC conveners will follow up with analyzers on the QA work of Run10 AuAu 200 GeV PicoDst conversion. Production team is waiting for the green light from PWG to resume the production.
- PYTHIA8 tuning task force will release a STAR technical paper during collaboration meeting. Such a technical paper will not go through the standard review process. Dan mentioned that a similar technical paper on FXT operation is also under preparation.