STAR PWGC meeting
Updated on Fri, 2021-06-25 14:38. Originally created by marr on 2021-01-28 09:26. 2021-06-25 09:30
America/New York
Friday, 25 June 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Energy Dependence of Intermittency for Charged Particles in Au + Au collisions at RHIC
- Brief introduction from the PWG conveners (5’) [Hanna Zbroszczyk]
- Paper proposal (15') [Presentation by Jin Wu]
- Open discussions (35')
- Summary from the conveners' panel (5’)
NOTES
2) Reshape of RCF farm for CME analysis for the next month or so
- A special queue is created for CME analysis
- Nodes owned by STAR (~12k) are moved to the shared pool to be used by CME analysis
- Data production is paused
- Allocation of nodes
- CME ~28.5k
- fast offline & nightly test ~ 1k
- Other analyzers ~ 0.5k (Expect long waiting time)
3) Data production and restoration (Priority list)
- Data Production
- Working on assembling library
- Data production paused to re-allocate CPU resources to CME analyses
- Data restoration
- (1) Isobar production, P20ic_SL20c, st_physics - done
(2) pp500_production_2013, P14ia, st_physics and st_physics_adc, MuDst, - done
- Run list: /star/u/agibson/2013Pi0s/2020-December-Run13PeriodWishList.txt
(3) cuProductionMinBias P17ii SL18b - done
(4) AuAu_200_production_2016, st_physics, P16ij_SL20c - done
(5) AuAu200_production2_2016, st_sst, st_nosst, P16ij_SL19c - done
(6) production_pp200long_2015, production_pp200long2_2015, production_pp200trans_2015, st_mtd, P16id_SL19c - done
(7) AuAu_200_production_2014, AuAu_200_producti on_low/mid/high_2014, AuAu_200_producti on_2016, AuAu200_productio n2_2016, st_upc, P16id (2014) and P17if (2016) MuDst - done
(8) dAu200_production_2016, st_physics, st_fms, P17id, 17133066-17141005, MuDst - done
(9) production_pp200trans_2015, st_ssdmb, P16id_SL19c - done
(10) AuAu_200_production_2016, st_mtd, P16ij_SL16j - ongoing
- (1) Isobar production, P20ic_SL20c, st_physics - done
4) Analysis meeting: PWG report or analysis highlight (Agenda)
5) Helper needed for space charge correction for 3.85 GeV FXT
Conclusions: LFSUPC and CF conveners will reach out to potential candidates
6) Policy of promising isobar data in FCV abstracts: shall we continue not promise any results from Isobar data until the CME paper is accepted?
Conclusions: will gather inputs from CME focus group, and bring up for discussion within the management.
STAR PWGC meeting
Updated on Fri, 2021-07-02 13:08. Originally created by marr on 2021-01-28 09:26. 2021-07-02 09:30
America/New York
Friday, 2 July 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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
- 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
- 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
- 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
STAR PWGC meeting
Updated on Fri, 2021-07-09 13:01. Originally created by marr on 2021-01-28 09:26. 2021-07-09 09:30
America/New York
Friday, 9 July 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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
- 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
STAR PWGC meeting
Updated on Thu, 2021-01-28 09:26. Originally created by marr on 2021-01-28 09:26. 2021-07-16 09:30
America/New York
Friday, 16 July 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
STAR PWGC meeting
Updated on Fri, 2021-07-23 12:35. Originally created by marr on 2021-01-28 09:26. 2021-07-23 09:30
America/New York
Friday, 23 July 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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
- What physics can we do with 20B+ events?
Conclusions: conveners will continue bringing these for discussion in PWG meetings
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
- What physics can we do with 20B+ events?
Conclusions: conveners will continue bringing these for discussion in PWG meetings
STAR PWGC meeting
Updated on Thu, 2021-01-28 09:26. Originally created by marr on 2021-01-28 09:26. 2021-07-30 09:30
America/New York
Friday, 30 July 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
STAR PWGC meeting
Updated on Fri, 2021-08-06 13:46. Originally created by marr on 2021-01-28 09:26. 2021-08-06 09:30
America/New York
Friday, 6 August 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Data production news
- 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)
- 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
- 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?
- 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)
STAR PWGC meeting
Updated on Thu, 2021-01-28 09:26. Originally created by marr on 2021-01-28 09:26. 2021-08-13 09:30
America/New York
Friday, 13 August 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
STAR PWGC meeting
Updated on Fri, 2021-09-10 16:36. Originally created by marr on 2021-01-28 09:26. 2021-08-20 09:30
America/New York
Friday, 20 August 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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
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
STAR PWGC meeting
Updated on Fri, 2021-08-27 16:50. Originally created by marr on 2021-01-28 09:26. 2021-08-27 09:30
America/New York
Friday, 27 August 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Electric charge and strangeness dependent directed flow of produced quarks in $Au+Au$ collisions at RHIC
- Brief introduction from the PWG conveners (5’) [ShinIchi Esumi]
- Paper proposal (15') [Presentation by Ashik Ikbal]
- Open discussions (35')
- Summary from the conveners' panel (5’)
NOTES
2) MuDst->PicoDst production priority (Priority list)
- Run10 AuAu200: is st_physics sufficient or other streams are needed as well? (ALL STREAMS)
- Priority: Run12 pp200, Run17 pp510
- Start-less TOF needed?
Conclusions:
- Priority: Run10 AuAu200 > Run17 pp510 st_physics > Run12 pp200
- Run10 AuAu200: it is sufficient to process st_physics at this point. Conveners will discuss within PWGs and come back if more streams are needed. LFSUPC conveners will ask interested analyzers to produce UPC PicoDst while the MuDst files are still on tape.
- Run17 pp510: will check if everything is ready for including start-less TOF for both jet tree and picoDst production. A JetCorr member will work with Gene to test the chain option for including start-less TOF in PicoDst conversion
- Run12 pp200: JetCorr will discuss if start-less TOF is desired for this production. If so, need to prepare calibration tables.
- Run12 pp200: JetCorr will discuss if start-less TOF is desired for this production. If so, need to prepare calibration tables.
3) data production for Run19 19.6 GeV
- Fix for time-dependent dE/dx in DB
- m2 drops slightly with momentum when using start-less TOF
- TOF calibration parameters, after recent updates to TPC t0, in DB. A test sample will be produced with official library and chain option to check the performance.
Conclusions:
- The slight drop of m2 vs. p will need to be taken into account in data analysis
- Once a test sample becomes available, analyzers should provide quick feedback on the data quality
4) Look for PWG helpers for TPC-related tasks: LIST
Conclusions: volunteers are needed for two remaining tasks
STAR PWGC meeting
Updated on Fri, 2021-09-03 13:47. Originally created by marr on 2021-01-28 09:26. 2021-09-03 09:30
America/New York
Friday, 3 September 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Charged Hadron Production in Au+Au Fixed-Target Collisions at sqrt(snn)=3 GeV at STAR
- Brief introduction from the PWG conveners (5’) [Daniel Brandenburg]
- Paper proposal (15') [Presentation by Ben Kimelman]
- Open discussions (35')
- Summary from the conveners' panel (5’)
PA: Daniel Cebra, Xin Dong, Matthew Harasty, Benjamin Kimelman, Hui Liu, Xiaofeng Luo, Guannan Xie
Target journal: PRC
NOTES
2) Data production
- Run10 AuAu200: MuDst -> PicoDst (please provide feedback)
- Run19 AuAu19.6: DAQ -> MuDst, PicoDst (days 62-65)
-- dE/dx centered at 0
-- BTOF performance checked to be good
-- Production continues
Conclusions
- Production team is waiting from the green light from PWG to resume Run10 AuAu200 conversion. LFSUPC will follow up on this.
- The MuDst files for st_upc stream of Run10 AuAu200 data are being converted to custom PicoDst by analyzers. Need to keep them on tape until completed.
- PWGs should continue to QA Run19 19.6 GeV data, and report back any issues they find. LFSUPC will follow up on submitting an official embedding request for this dataset, such that we can quickly check the TPC/iTPC simulation, and compare corrected yields with BES-I
3) Collaboration meeting
- Speakers for PWG reports
- Convener-management meeting (Sep. 24th, 15 min after main agenda)
Target journal: PRC
NOTES
2) Data production
- Run10 AuAu200: MuDst -> PicoDst (please provide feedback)
- Run19 AuAu19.6: DAQ -> MuDst, PicoDst (days 62-65)
-- dE/dx centered at 0
-- BTOF performance checked to be good
-- Production continues
Conclusions
- Production team is waiting from the green light from PWG to resume Run10 AuAu200 conversion. LFSUPC will follow up on this.
- The MuDst files for st_upc stream of Run10 AuAu200 data are being converted to custom PicoDst by analyzers. Need to keep them on tape until completed.
- PWGs should continue to QA Run19 19.6 GeV data, and report back any issues they find. LFSUPC will follow up on submitting an official embedding request for this dataset, such that we can quickly check the TPC/iTPC simulation, and compare corrected yields with BES-I
3) Collaboration meeting
- Speakers for PWG reports
- Convener-management meeting (Sep. 24th, 15 min after main agenda)
STAR PWGC meeting
Updated on Fri, 2021-09-10 16:15. Originally created by marr on 2021-01-28 09:26. 2021-09-10 09:30
America/New York
Friday, 10 September 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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.
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.
STAR PWGC meeting
Updated on Thu, 2021-01-28 09:26. Originally created by marr on 2021-01-28 09:26. 2021-09-17 09:30
America/New York
Friday, 17 September 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
STAR PWGC meeting
Updated on Mon, 2021-03-22 12:22. Originally created by marr on 2021-01-28 09:26. 2021-03-19 09:30
America/New York
Friday, 19 March 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Longitudinal double-spin asymmetry for inclusive jet and dijet production in polarized proton collisions at $\sqrt{s}=510$ GeV
- Brief introduction from the PWG conveners (5’) [Maria Zurek]
- Paper proposal (15') [Presentation by Amilkar Quintero]
- Open discussions (35')
- Summary from the conveners' panel (5’)
Proposal page: https://drupal.star.bnl.gov/STAR/blog/aquinter/paper-proposal-jets-all-2013
NOTES
2) Data production (Priority list)
DAQ->MuDst
- BES-II: do we want to produce only "minbias-allvtx" trigger, i.e. events with HLT vertices within +/- 200 cm?
-- 19.6 GeV (not applicable), 14.6 GeV (68%), 11.5 GeV (37%), 7.7 GeV (22%)
-- What vertex selection algorithm should be used for PicoDst, Default or VpdOrDefault? One can study this with the recent 19.6 GeV calibration production.
Conclusions: PAC will collect more information about possible missing good offline events in minbias-allvtx triggers, especially as a function of multiplicity. Conveners will bring this topic for discussion in PWGs.
MuDst -> PicoDst
- Run12 Cu+Au: issue of missing half bTOF in matching. Is it sufficient to reproduce PicoDst including the fix in afterburner? Can we check this?
- Run 12 p+p 200 GeV:
-- Is chain option "PicoVtxMode:PicoVtxVpdOrDefault, TpcVpdVzDiffCut:6, PicoCovMtxMode:PicoCovMtxWrite" correct? Should one include PicoBEmcSmdMode:PicoBEmcSmdWrite?
-- Plan to assemble SL21b for this production, including nSigmaTof variables. Is it OK as these variables are directly copied from MuDst?
- BES-I: production should be fast since MuDst files are on DD
Conclusions:
- Run12 Cu+Au: LFSUPC will confirm whether running afterburner could fix the problem. If so, one will need to produce the standard PicoDst and restore MuDst for UPC PicoDst production
- Run 12 p+p 200 GeV: JetCorr conveners will communicate with the production team to add the chain option "PicoBEmcSmdMode:PicoBEmcSmdWrite"
- BES-I will be added to the PicoDst production list
3) pwg_tasks area is full (Disk lease)
- New request from tracking efficiency TF: 10T
- Propose to remove 19.6 GeV express production which takes 9T
Conclusions: conveners agree with the proposal, and PAC will discuss with TFG group to see if 19.6 GeV data is used
4) Computing resources for Isobar analysis
- Queue priority
- Disk space needed (2Tx5?). pwg area available for institutions:
-- BNL: 8.6T
-- Purdue: 11.2T
-- UIC: 4.6T
-- UCLA: 3.5T
-- Tsukuba: 4.4T
Conclusions: priority for job submission will be enhanced for five analyzers who will submit jobs for CME analyses. Institution space on PWG area should be sufficient.
5) BUR: due mid May
- Charge: running plan for 22-25
- 2025 was not mentioned for STAR running in last PAC report. Opportunity to make a stronger case this time
- Status of Run17 pp 510 GeV data analysis
Conclusions: the unpolarized W+/W- result using Run17 data is expected to be released as preliminary at upcoming DIS conference. Cold QCD PWG is aiming to have some W A_N results for PAC meeting. Conveners will bring up the topic of BUR for discussion at PWG meetings.
Conclusions: priority for job submission will be enhanced for five analyzers who will submit jobs for CME analyses. Institution space on PWG area should be sufficient.
5) BUR: due mid May
- Charge: running plan for 22-25
- 2025 was not mentioned for STAR running in last PAC report. Opportunity to make a stronger case this time
- Status of Run17 pp 510 GeV data analysis
Conclusions: the unpolarized W+/W- result using Run17 data is expected to be released as preliminary at upcoming DIS conference. Cold QCD PWG is aiming to have some W A_N results for PAC meeting. Conveners will bring up the topic of BUR for discussion at PWG meetings.
6) Interest in RP physics in 2022 and beyond
- Need help for commissioning and operating RP
AOB:
- Isobar embedding QA: SLIDES
- Volunteer for including bTOF in vertex ranking calculation for BES-II data: Guannan Xie
- PWGC group on Skype for fast communication?
- Clean up obsolete submission: https://drupal.star.bnl.gov/STAR/presentations/submitted
STAR PWGC meeting
Updated on Fri, 2021-03-26 14:10. Originally created by marr on 2021-01-28 09:26. 2021-03-26 09:30
America/New York
Friday, 26 March 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Discussion of PWGC previews more than 6 months ago, but no GPC (LIST)
Conclusions: see LIST for analysis status
Conclusions: see LIST for analysis status
2) Data production (Priority list)
- New restoration request: AuAu_200_production_2016, st_mtd, P16ij_SL16j
Conclusions:
- Conveners will follow upon vertex selection algorithm within PWG
- The new request is added to the end of the queue
3) Embedding request relevant for FCV and LFSUPC: H3L quasi-2-body embedding (H3L-> d+"Lambda" -> d+p+pi)
Conclusions: conveners support this embedding request
4) Volunteer for RP operation 2022
Conclusions: this topic was brought up at LFSUPC and ColdQCD weekly meetings earlier this week, but no volunteers have spoken up yet. Conveners will discuss and come up with a list of analyzers who might be interested in RP physics, and we will directly approach them to see if they are willing to help.
4) Volunteer for RP operation 2022
Conclusions: this topic was brought up at LFSUPC and ColdQCD weekly meetings earlier this week, but no volunteers have spoken up yet. Conveners will discuss and come up with a list of analyzers who might be interested in RP physics, and we will directly approach them to see if they are willing to help.
AOB:
- PWGC group on Skype for fast communication? How about MatterMost?
Conclusions: there were concerns that conveners could miss some information on these chat platforms. For now, we will continue using email as the main communication channel.
- Clean up obsolete submission: https://drupal.star.bnl.gov/STAR/presentations/submitted
STAR PWGC meeting
Updated on Fri, 2021-04-02 14:16. Originally created by marr on 2021-01-28 09:26. 2021-04-02 09:30
America/New York
Friday, 2 April 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Measurements of v2, v3 in central p+Au, d+Au and 3He+Au collisions at 200 GeV from STAR collaboration
- Brief introduction from the PWG conveners (5’) [Prithwish Tribedy]
- Paper proposal (15') [Presentation by Shengli Huang]
- Open discussions (35')
- Summary from the conveners' panel (5’)
Proposal page: https://drupal.star.bnl.gov/STAR/blog/slhuang/measurements-v2-v3-pau-dau-and-3heau-collisions-%C2%AD200-gev-star-collaboration
NOTES
2) PWG review procedure
Proposal:
- PAs finish all aspects of the analysis, present analysis details in PWG meetings and address all comments raised
- PAs send final paper draft and analysis note to PWG mailing list for comments for at least two weeks
- Once all the PWG comments are addressed, conveners officially sign off and request GPC formation
Conclusions: conveners agree with the proposal, and some PWGs are already doing this. Other PWGs will also follow this.
- PAs finish all aspects of the analysis, present analysis details in PWG meetings and address all comments raised
- PAs send final paper draft and analysis note to PWG mailing list for comments for at least two weeks
- Once all the PWG comments are addressed, conveners officially sign off and request GPC formation
Conclusions: conveners agree with the proposal, and some PWGs are already doing this. Other PWGs will also follow this.
STAR PWGC meeting
Updated on Fri, 2021-04-09 13:55. Originally created by marr on 2021-01-28 09:26. 2021-04-09 09:30
America/New York
Friday, 9 April 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Probing quadrupole deformation of uranium in relativistic nuclei collisions
- Brief introduction from the PWG conveners (5’) [ShinIchi Esumi]
- Paper proposal (15') [Presentation by Chunjian Zhang]
- Open discussions (35')
- Summary from the conveners' panel (5’)
Proposal page: https://drupal.star.bnl.gov/STAR/blog/chunjian/probing-quadrupole-deformation-uranium-relativistic-nuclear-collisions
NOTES
2) Study of Run19 14.5 GeV for hlt-allvtx trigger: https://drupal.star.bnl.gov/STAR/blog/kehw/minibias-allvtx-test-production-qa-0
Conclusions: conveners will discuss the study within PWGs
3) eTOF status in 14.5 GeV. Is it worth calibration effort?
Phillip "For 14.5 GeV, there is a short period in the beginning (before day 118) when the HV was still at the 19.6GeV-Setting and before pre-amp channels died in masses.
These data are probably usable, but might still be significant effort to calibrate. There are is also already a significant number of channels dead.
Afterwards, high voltage was raised again and more and more channels started dying of in beam loss events.
>50% of all channels died or have high threshold and they are basically randomly distributed about the eTOF surface.
For this period afterwards, i don't see a reliable way to determine any efficiency."
Conclusions: it was brought up that data after day 118 could be useful for flow analysis, for which efficiency correction does not play a significant role. Will discuss with eTOF group to see how much efforts are needed for calibration.
Conclusions: conveners will discuss the study within PWGs
3) eTOF status in 14.5 GeV. Is it worth calibration effort?
Phillip "For 14.5 GeV, there is a short period in the beginning (before day 118) when the HV was still at the 19.6GeV-Setting and before pre-amp channels died in masses.
These data are probably usable, but might still be significant effort to calibrate. There are is also already a significant number of channels dead.
Afterwards, high voltage was raised again and more and more channels started dying of in beam loss events.
>50% of all channels died or have high threshold and they are basically randomly distributed about the eTOF surface.
For this period afterwards, i don't see a reliable way to determine any efficiency."
Conclusions: it was brought up that data after day 118 could be useful for flow analysis, for which efficiency correction does not play a significant role. Will discuss with eTOF group to see how much efforts are needed for calibration.
4) Do we want to run eTOF in 2022 (pp 510 GeV)? What is the physics motivation?
Conclusions: conveners will bring this up for discussion at PWG meetings.
5) Status of proton feed-down correction: what is needed to complete the study?
Conclusions: Daniel Brandenburg showed a brief summary of current status (SLIDES). LFSUPC PWG will follow up and perform those agreed-upon studies and checks.
6) sQM abstracts: merging and speaker selection (ACCEPTANCE LIST)
Conclusions: Conveners will contact relevant PAs to produce merged abstracts (CF - 2, FCV - 1, HF - 1), and discuss with them whether they can decide on a speaker. If not, we will turn to STC. For those pre-merged abstracts, we will ask STC to select a speaker.
Conclusions: Daniel Brandenburg showed a brief summary of current status (SLIDES). LFSUPC PWG will follow up and perform those agreed-upon studies and checks.
6) sQM abstracts: merging and speaker selection (ACCEPTANCE LIST)
Conclusions: Conveners will contact relevant PAs to produce merged abstracts (CF - 2, FCV - 1, HF - 1), and discuss with them whether they can decide on a speaker. If not, we will turn to STC. For those pre-merged abstracts, we will ask STC to select a speaker.
| Time | Talk | Presenter |
|---|---|---|
| 08:30 | feeddown lfsupc status ( 00:20 ) 1 file |
STAR PWGC meeting
Updated on Fri, 2021-04-16 14:09. Originally created by marr on 2021-01-28 09:26. 2021-04-16 09:30
America/New York
Friday, 16 April 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Measurements of H3L and H4L Lifetime and Production Yield in sNN =3 GeV Au+Au Collisions at RHIC
- Brief introduction from the PWG conveners (5’) [Dan Cebra]
- Paper proposal (15') [Presentation by Yue-Hang Leung]
- Open discussions (35')
- Summary from the conveners' panel (5’)
- Please comment and approve presentations from PWG
- New preliminary results from JetCorr using Isobar data: SLIDES
Conclusion: there is no objection in releasing the new preliminary results based on combined Isobar data from JetCorr.
3) What to run if there is one week left this year? The chance is quite small though.
Conclusion: conveners will bring to PWG members' attention. Any proposal should be first discussed within the PWG.
4) Shall we save only hlt-allvtx triggers for BES-II production?
Conclusion: the suggested method is not supported by PWGs, given the potential bias for peripheral events and small gain in resources. All the recorded events should be produced.
5) Vertex selection for BES-II PicoDst
Conclusion: the default vertex should be selected for PicoDst.
6) eTOF calibration for 14.5 GeV: good performance up to day 118, and only one sector fully functional afterwards
Conclusion: PWGs are fine with having calibrated eTOF data up to day 118. Will not use eTOF data after day 118.
7) Do we want to run eTOF in 2022 (pp 510 GeV)? What is the physics motivation?
Conclusion: no physics motivation brought up so far. Cold QCD will discuss this item at the upcoming weekly meeting.
8) Acknowledgement of old STAR preliminary results in a STAR talk
Conclusion: for any STAR preliminary results presented in a STAR talk, it is required not to associate it with a particular name, either the main analyzer or the person who presented these results the first time. These are STAR resutls, and anyone can present and defend them. On the other hand, the conference information where these preliminary result were firstly shown can be added if desirable.
9) FCV: propose to produce Run19 200 GeV data
Conclusion: this dataset is already on the priority list, and we will revisit this once the TPC calibration is ready, and BES-II data production starts.
STAR PWGC meeting
Updated on Fri, 2021-04-23 13:03. Originally created by marr on 2021-01-28 09:26. 2021-04-23 09:30
America/New York
Friday, 23 April 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Jet-hadron correlations with respect to the event plane in \sNN = 200 GeV Au+Au collisions in STAR
- Brief introduction from the PWG conveners (5’) [Raghav]
- Paper proposal (15') [Presentation by Joel Mazer]
- Open discussions (35')
- Summary from the conveners' panel (5’)
Proposal page: https://drupal.star.bnl.gov/STAR/blog/jmazer19/run14-auau-jet-hadron-correlations-relative-event-plane-paper-page
NOTES
Conclusions: there are no strong physics interests in using eTOF in 510 GeV p+p data, and so PWGs suggest to turn eTOF off in 2022. However, there are interests in using eTOF in 2023 and beyond.
STAR PWGC meeting
Updated on Mon, 2021-05-03 08:51. Originally created by marr on 2021-01-28 09:26. 2021-04-30 09:30
America/New York
Friday, 30 April 2021
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
1) Paper preview: Measurement of D± meson production and total charm production yield at midrapidity in Au+Au collisions at √sNN = 200 GeV with the STAR experiment
- Brief introduction from the PWG conveners (5’) [Barbara Trzeciak]
- Paper proposal (15') [Presentation by Jan Vanek]
- Open discussions (35')
- Summary from the conveners' panel (5’)
- High-order off-diagonal cumulants in 27 GeV (ABSTRACT): what is its relation to the published results? What is the status of the erratum for the paper?
- Light nuclei at 3 and 27 GeV (ABSTRACT): what results will be released? How about the comparison to preliminary results where UrQMD is used for proton feed-down?
Conclusions:
- No cross-term cumulants, which was the part that are wrong in the paper, will be shown in the talk. For the erratum, an initial draft is at hand. Will need to polish it before sending to PWG.
- Better to take out 27 GeV results to avoid any comparison to preliminary results. The 3 GeV results have been shown at APS meeting. It is very important to understand the proton feed-down and get the paper published.
3) 64bit vs. 32bit
- Which test samples shall be used for physics evaluation, e.g. distributions for tracks, BEMC/TOF/MTD hits, etc? 200 GeV Au+Au, low energy Au+Au, 510 GeV p+p
- For each sample, data production and embedding will be done with 32bit and 64bit
Conclusions: suggest to take 2016 200 GeV Au+Au , 19.6 GeV Au+Au from BES-I and 2017 510 GeV p+p
4) Trigger system upgrade for 20kHz trigger rate. Is this needed for Run-22?
Conclusions: will bring this up for discussion at Cold QCD PWG and forward upgrade group