The STAR experiment

PA: Shengli Huang, Zhenyu Chen, Jiangyong Jia, Roy Lacey, Pengfei Liu, Maowu Nie, Yuri Sato, Chunjian Zhang 
Target journal: PRC

NOTES

2) New data production requests (production priority)
- Isobar st_mtd, st_upc

Conclusions: these two new requests are added to the same category as the current Run17 st_mtd data production

3) Discussion of QM abstracts (ABSTRACTS)

Conclusions: the merge list is updated after discussion
 

- Run19 19.6 GeV - done
- Run19 14.6 GeV - days 119-154 done; waiting for eTOF calibration for days 94-118 (early next week)
- What's next? 
-- Run19 FXT: bTOF ready; waiting for final dE/dx calibration (~ 1 week); eTOF will NOT be included

-- Run20 FXT: bTOF ready; will need dE/dx and eTOF calibrations
-- Need SL21d for FXT production
- Submit embedding request for pi/k/p 

Conclusions: LFSUPC PWG will submit the embedding request for pi/k/p today, and mark it as high priority.

2) Independent checks for key BES-II results
- What should be classified as key results: net-p fluctuation, light nuclei ratio?
- Proposed procedure for independent checks: two independent groups (self-nominated or management-identified), who are interested in those topics, should carry out the analysis from the beginning to the end, and cross check data points and uncertainties at all energies 

Conclusions
- An excerpt of PAC report this year: "Given that STAR is the only experiment taking this important data, the PAC recommends that the STAR collaboration does everything possible to ensure that the analysis of critical observables in the BESII, such as proton number cumulants, are carried out by at least two independent groups within STAR."
- Agreement from last year's discussion which we will follow: "It was agreed not to release preliminary results for two measurements, i.e. net-proton kurtosis and light nuclei ratio NtNp/Nd2 vs. collision energy, from BES-II data. These measurements should also be analyzed by at least two groups with independent codes." (link)

3) Reminder
- collect variables for determining common bad runs
- QA board meeting at 12 pm (BNL time) Oct. 15th: Yu or Prithwish will present QA algorithm
-- https://bnl.zoomgov.com/j/1618435669?pwd=L3B6M3JKcjRFMVFxQTNhaEdBdkZ5UT09

Conclusions: in addition to QA variables, supplying histograms of QA variables vs. run index would be even better for the QA analyzers. Otherwise, they need to run through the data to generate such histograms.
 

1) Express stream data 
- Frankfurt group requested to carry out following measurements using BES-II express stream data for preliminary status
-- Observation of He4L, He5L, H4L->tppi
-- Probing hypernuclei structure with Dalitz plot
-- Binding energy vs mass of hypernuclei

- Management's proposal: 
-- The express stream data can only be used for the requested analyses, which could be labeled as STAR preliminary. The preliminary figures should be clearly labeled as from the express stream and with non-final calibration.
-- Custom embedding based on the express stream data can be used to derive the preliminary results
-- These results should go through the usual approval procedure in the relevant PWG

PA: Samuel Heppelmann, Yu Zhang, Daniel Cebra, Xin Dong, Xiaofeng Luo, Toshihiro Nonaka, Sooraj Radhakrishnan, Nu Xu 
Target journal: PRC

NOTES

3) Common bad run list for BES-II
- Collect variables from each PWG that should be QA'ed for physics analyses
- Group them based on sub-systems: TPC, dE/dx, bTOF, eTOF, EPD, etc, and generate bad run lists for each sub-system. 
- Create a new maker to check bad runs, which should be used by all analyses
- Proposal for additional variables and bad runs should be discussed in relevant PWG and QA board
- QA board meeting
-- Mailing list: https://lists.bnl.gov/mailman/listinfo/star-qaboard-l
-- Zoom: https://bnl.zoomgov.com/j/1618435669?pwd=L3B6M3JKcjRFMVFxQTNhaEdBdkZ5UT09
-- Time: Fridays 12 pm BNL time

Conclusions: will follow it up in the QA board. The highest priority is to identify bad runs for centrality work

4) Dedicated mailing list for each GPC starting from GPC #326
- Link to the mailing list can be found on the GPC information page: https://www.star.bnl.gov/protected/common/GPCs/gpc-committees.xml
- Current proposal: 
-- Subscribe all GPC members by default
-- PAs and PWG conveners can request to be subscribed anytime during the GPC process
-- Subscription is only open to general collaborators during the two week period of collaboration review in order to gain access to the archived discussion
-- Everyone is free to subscribe after the paper is published

Conclusions: suggested to subscribe all the PAs by default. No objections to other aspects.

PA: Aswini Sahoo, Subhash Singha, Md Nasim 
Target journal: PRC

NOTES

2) eTOF development
- eTOF software coordinator is working on adding flags for each eTOF counter to PicoDst to indicate whether the counter is good for analysis. Such information is only available for 2020+ though.
- For people who want to use eTOF in 2019 (19.6 GeV, 14.6 GeV), they should discuss with eTOF group about how to study acceptance fluctuation and its impact on efficiency 

3) Disk space needs for distributed disk in the future
- Are PicoDst and Jet tree sufficient for Cold QCD group in 2022 and 2024?

Conclusions: the combination of PicoDst and jet tree are sufficient for current analyses in Cold QCD PWG. Conveners will confirm this at the PWG meeting next week.

4) Common bad run list, pileup rejection and centrality for BES-II
- Will use the tools developed for Isobar blind analysis
- We already have volunteers who started working on 19.6 GeV data
- Discussions and approval will mainly happen in QA board and centrality focus meetings
- A bad run list will be determined for centrality determination. How about analysis specific bad runs? Shall we collect inputs from each PWG and pass them onto the volunteers?

Conclusions: 
- A dedicated mailing list is created for centrality work (https://lists.bnl.gov/mailman/listinfo/star-centrality-l)
- Conveners will collect lists of variables for QA in the next couple of weeks. The final combined list will be discussed and passed onto people who are working on identifying bad runs. The goal is to create common bad run lists for different sub-systems, such as TPC. EPD, TOF, etc. This does not preclude people from checking more variables and possibly identifying more bad runs in the future. Should that happens, the findings need to be communicated to the collaboration. This needs to be done quickly as BES-II data are being produced.

- It was also brought up that centrality distributions should be checked if additional bad runs, on top of what's used for centrality determination, are rejected.

5) Need to identify one more volunteer for TPC related work (LIST)

Conclusions: volunteers are welcome