The STAR experiment

- FCV PWG prefers to have a slightly higher priority for O+O than for d+Au. Looking forward towards QM 2023, if we want to show results from O+O, we probably need to produce them immediately after 11.5 GeV Au+Au data. Will continue to discuss this. 
- Run22 datasets will be produced after Run21 datasets. For the four main streams in Run22, st_mtd can be placed with lowest priority. ColdQCD PWG will discuss the relative priorities of the other three data streams.

1) Embedding deputies and helpers (Current list)

• One helper for each PWG
  • Expect to place high priority on assigned tasks, and communicate with the embedding coordinator timely
    • LFSUPC: Yi Fang (Tsinghua), Yiding Han (Rice)
    • Cold QCD: Hannah Harrison (Kentucky)
    • HP: Diptanil Roy (Rutgers)
    • CF: Yongcong Xu (CCNU)
• Two deputies needed: in charge of embedding setup and running QA samples on RCF
  • Need to be committed to the job
  • Expect to spend 20-30% of his/her time

Conclusions: i) FCV PWG will continue to search for a helper; ii) nominations/suggestions for deputies are welcome

2) Questions from trigger group (answers needed by Aug. 1st)

• More midrapidity triggers than those used in Run14/16?
• Cross talk between BEMC and BTOF?

Conclusions: there are interests from LFSUPC to trigger on back-to-back signals, from for example Jpsi decays, in both BEMC and BTOF together, which will require commutations between BEMC and BTOF on the trigger level. This is the only new trigger at mid-rapidity needed for Run23 compared to Run14/16.

3) UrQMD vs. SMASH for BES-II comparison

Conclusions: LFSUPC/FCV/CF PWGs will continue to discuss which generator(s) to use and with what configuration(s). 

4) Forward triggers: concrete plan needed by September

Conclusions: there are two forward triggers proposed for Run23 Au+Au running
- HP PWG: search for charmed nucleus (TOFmult <~ 100, EPD one hit > 3 MIP, HCAL > 25 GeV)
- LFSUPC PWG: will follow up on coincidence trigger between forward and mid rapidity for UPC Jpsi

Proposal page: https://drupal.star.bnl.gov/STAR/blog/jwu/Observation-anti-hypernuclei-4barlambdabarH-RHIC 2) Production news (Gene's report)

• Run21 7.7 GeV COL: production just started; QA feedback needed (trgsetupname=production_7p7GeV_2021,filetype=daq_reco_picodst,production=P22ib,storage=local)
• Run20 FXT MuDst->PicoDst: to be started very soon after UU conversion is done; will not reproduce Run19 FXT data since ETOF was not very useful anyway
• Run17 510 GeV p+p MuDst -> PicoDst: production started; confirming with BTOF experts that correct calibration parameters are picked up
• Calibration: Run20 11.5 GeV, 9.2 GeV, and Run21 17.3 GeV

3) Data accessibility on distributed disk

• Automatic restoration mechanism didn't pick up new datasets since 1 year ago. Fixed now.
• Duplicate datasets on disk 
  • Small
  • Actively analyzed

Conclusions: PWGs will work out a priority list of datasets desired to be duplicated on distributed disk, and then work with the S&C team to implement them to the extent possible. 

Proposal page: https://www.star.bnl.gov/protected/lfsupc/xwang1/papers/Peripheralee/
2) Organizational news - Cold QCD convener rotation (Outgoing: Matt Posik; Incoming: Xiaoxuan Chu)

Conclusions: many thanks for Matt's dedication to the Cold QCD PWG in the last three years. Welcome on board Xiaoxuan. 

3) Embedding helpers (Current list)

• One helper for each PWG
• Expect to place high priority on assigned tasks, and communicate with the embedding coordinator timely
  • LFSUPC: Yi Fang (Tsinghua), Yiding Han (Rice)

Conclusions:
- PWGs will approach existing helpers to see if they are willing to continue to serve. If not, will find new helpers.
- It is very important that helpers place embedding work as one of their priorities and communicate with others in a timely fashion.
- Dan: we should have a coherent approach to FXT embedding. We do not need separate embeddings for all the datasets since the detector acceptance and event multiplicity do not change significantly among different FXT energies. Will look into this and come up with a plan. 

4) Help needed for Yuri to do detailed QA during calibration

Conclusions: Dan will communicate with Yuri to see what kind of help he needs exactly, and then we will try to find helpers in the QA board. 

5) Production priority (PRIORITY)

• 17.3 COL and 7.2 FXT

Conclusions: 17.3 COL and (Run20+21) 7.2 FXT are now placed as the highest priority among all Run21 datasets

6) Questions from trigger group (answers needed by Aug. 1st)

• More midrapidity triggers than those used in Run14/16?
• Cross talk between BEMC and BTOF?

Conclusions: 
- Rongrong will find out whether the BEMC trigger issue during Run22 is fixed or not
- PWGs will continue to discuss at weekly meetings on these questions

7) Forward triggers: concrete plan needed by September

Conclusions: HP and LFSUPC will follow up on the study of potential forward triggers for Run23 Au+Au collisions. Need to come up with initial trigger thresholds and expected rates by September. 

8) Run19 19.6 GeV Glauber parameter uncertainties available (LINK)

• 5% uncertainty in total cross section included as in BES-I. It will be re-evaluated for publication

Conclusions:
- These uncertainties are good for preliminary results. 
- The bad run list for Run19 3.2 GeV (FXT, 4.59 GeV) is now available: https://drupal.star.bnl.gov/STAR/pwg/common/bes-ii-run-qa/FXT-datasets

Proposal page: https://www.star.bnl.gov/protected/lfsupc/zye20/Dielectron_T_measurement/
2) Strategy for BES-II FXT dataset embedding (Dan, SLIDES)

Conclusions: given the large number of FXT datasets recorded during BES-II, it was suggested to merge the embedding requests for the datasets of same TPC status. 

• Here are potential groups of FXT datasets that have the same TPC status and could be combined
  • 2019: 3.2, 3.9, 7.7
  • 2020: 3.9, 5.2, 6.2
  • 2021: 3.0 (first part), 9.2, 11.5, 13.7
• The main idea is to produce embedding samples for the highest energy in a group (see above), which covers the full multiplicity range, and this embedding sample will be used for all the datasets in the group
• Might submit central embedding requests for each group instead of from individual analyzers
• This is possible since the vertex positions of all FXT datasets are the same
• Will check the effect of rapidity change vs. collision energy by comparing the tracking efficiencies at a given multiplicity between existing Run19 3.2 GeV embedding and (to-be-produced) Run19 7.7 GeV embedding
• Dan will coordinate with other conveners and the embedding team to come up with a more concrete strategy

Proposal page: https://drupal.star.bnl.gov/STAR/blog/wissink/Paper-Proposal-500-GeV-EEMC-Dijet-ALL 2) Data production for 7.7 GeV COL

• Current dE/dx calibration is good for a first pass; further improvement mainly for large-mass particles
• Need to see whether the current eTOF calibration is good for a first pass

Conclusions
- the convener panel is supportive of the plan to produce the 7.7 GeV COL data, which overlaps with the 7.7 GeV FXT data. 
- the eTOF calibration and software should be ready for converting Run19/20 FXT MuDst to PicoDst. Will ask the production team to move this forward. 

3) Late request of preliminary results

• Conveners keep track of analysis progress since the abstract submission, and request regular updates from PAs
• If PAs do not respond, conveners should inform management, who will then intervene
• If PWG/conveners do not have time to vet the new results, those results should not be released as preliminary

Conclusions
- We need to watch out for abstracts that over-promise 
- Analyzers should present their results regularly in PWG such that conveners can follow the details of the analyses, to make the approval process smooth. 

4) Embedding deputies and helpers (Current list)

• One helper for each PWG
  • Expect to place high priority on assigned tasks, and communicate with the embedding coordinator timely
    • LFSUPC: Yi Fang (Tsinghua), Yiding Han (Rice)
• Two deputies needed: in charge of embedding setup and running QA samples on RCF
  • Need to be committed to the job
  • Expect to spend 20-30% of his/her time

Conclusions: conveners will follow up on this.

5) Questions from trigger group (answers needed by Aug. 1st)

• More midrapidity triggers than those used in Run14/16?
• Cross talk between BEMC and BTOF?
• BBC trigger readout issues seen in Run22 will be fixed with DSM2 board for Run23. BEMC trigger readout issue is negligible. 

Conclusions: the preliminary answer is that we do not need anything more than what was there in Run14/16. PWGs should follow up on this in the next two weeks. 

6) FXT embedding strategy: proton sample for all datasets for comparison and cross check

Conclusions: the highest priority for embedding should be pions in 3.2 GeV FXT such that one can compare TPC performance at positive and negative eta. Then we should produce embedding samples at 3.2 and 7.7 GeV FXT in order to verify whether one can group several FXT datasets together for embedding purpose. 

7) Collaboration meeting

• Time: Sep. 12-16
• Location: BNL
• LFSUPC: organize a dedicated parallel session for freeze-out parameter extraction, especially at low energy (3 GeV FXT)

Conclusions: PAs of spectrum analyses at 3 GeV FXT will start the discussion about freeze-out parameter extraction before collaboration meeting

Proposal page: https://drupal.star.bnl.gov/STAR/blog/fengyich/Correlation-between-Lambda-and-CME-Webpage

• Tuesday, Wednesday: parallel sessions
• PWG reports during plenary session
• Management-convener meeting: noon or evening?

Conclusions: tentatively, we will schedule the management-convener meeting in an evening during the collaboration meeting. 

4) pwg_tasks space for BES-II UrQMD simulations

• 10 million events at each energy
• 2T disk space

Conclusions: conveners are in support of this proposal. FCV, CF and LFSUPC will discuss within PWGs and decide on the configuration of UrQMD that is useful for majority of analyses. 

AOB
- Run19 14.6 GeV centrality calibration is being wrapped up, and should be made available to the whole collaboration soon. We should not approve any centrality-dependent preliminary results before that. 
- Authors should really obey the rule and send slides/proceedings to PWGs 2 weeks ahead of deadline. 

Proposal page: https://www.star.bnl.gov/protected/bulkcorr/taknn/Paper/pzisobar/HP/index.html

Proposal page: https://drupal.star.bnl.gov/STAR/blog/adams92/Global-polarization-Λ-and-̄Λ-hyperons-AuAu-collisions-√sNN-196-and-27-GeV

• PAs should present the status of the analysis before proposing an abstract for a conference aiming for new preliminary results
• After abstract submission/acceptance, PAs should present analysis updates regularly (at least 1-2 times a month) at PWG meetings

Conclusions: conveners will keep this in mind, and we need all the analyzers to give regular updates in the PWG. 

• DNP, Oct. 27-30, hybrid: abstract due July 1st
• CIPANP, Aug. 29 - Sep. 4, in person only (Florida): abstract due Aug. 1st

Proposal page: https://drupal.star.bnl.gov/STAR/blog/djs232/Paper-EA-and-UE-Corrs-High-Q2-Events-pAu-sNN200-GeV-Collisions-STAR

• Strangeness production in Run16 d+Au (embedding won't be ready)
• pi/k/p in 54.4 GeV

• Run17 MuDst -> PicoDst st_physics: issues found with BTof calibration. Production stopped, and will resume after fix
• Run21 7.7 GeV COL: new correction scheme developed for TPC cluster ADC nonlinearity; recalibration needed for all produced BES-II data if want to apply (SLIDES)
• Run19/20 FXT data: need to be reprocessed after ETOF calibration/alignment is fixed

• Note: it should be written as $p$+$p$ and $p$+Au, etc, which is different from the guidance

6) Need a maintainer for StEmcADCtoEMaker

Proposal page: https://www.star.bnl.gov/protected/bulkcorr/dmallick/WebPage_Deuteron/index.html

• New "JetCorr" convener: Nihar Sahoo
• Will merge JetCorr and HF very soon. How about calling it HardProbes (HP)?
• Raghav and Hanseul will step down when the merging takes effect.

• Run21 7.7 GeV COL calibration (need a few more weeks)
  • Done: BTof
  • In progress: ETof, TPC dE/dx, EMC
• Run17 510 GeV st_physics MuDst->PicoDst (~23% done, need a few more months)
  • More central disk space removing the need to do it in batches. Already communicated with T. Lin. 
• Run19 & 20: st_zerobias data stream needs to be produced
  • Does this need to be in the same library as st_physics productions? (thinking of PicoDst issues)

Proposal page: https://drupal.star.bnl.gov/STAR/blog/kshen/jpsi-production-auau-collisions-544-gev

• Mismatch in NHitsFit for pion: https://drupal.star.bnl.gov/STAR/system/files/embedding_status_20220504.pdf seen in embedding
  • Run19 14.6 GeV embedding for pion/kaon (not needed for sQM any more)
  • Run19 19.6 GeV embedding for strangeness 

Conclusions:
- Will re-tune TPC simulation for pion/kaon/proton simultaneously, and reproduce all the affected embedding samples
- PWGs will check the current Run19 19.6 GeV sample to see if the same mismatch exists

3) Production news

• DAQ production
  • Run18 Isobar st_mtd: 12% submitted
  • A sample for QA: /star/data14/GRID/NFS_FileList/production_isobar_2018_P22ia_QA.txt
• MuDst->PicoDst conversion
  • Run17 pp 510 GeV st_physics: 18% completed

4) eTOF needs for 2023+25

Conclusions: eTOF is not critically needed for the CF PWG