The STAR experiment

https://drupal.star.bnl.gov/STAR/public/star-run21-25-bur

BlueJeans:

Meeting URL
https://bluejeans.com/822956697?src=join_info

Meeting ID
822 956 697

Want to dial in from a phone?

Dial one of the following numbers:
+1.408.419.1715 (United States(San Jose))
+1.408.915.6290 (United States(San Jose))
(see all numbers - https://www.bluejeans.com/premium-numbers)

Enter the meeting ID and passcode followed by #

Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

https://drupal.star.bnl.gov/STAR/public/star-run21-25-bur

BlueJeans:

Meeting URL
https://bluejeans.com/822956697?src=join_info

Meeting ID
822 956 697

Want to dial in from a phone?

Dial one of the following numbers:
+1.408.419.1715 (United States(San Jose))
+1.408.915.6290 (United States(San Jose))
(see all numbers - https://www.bluejeans.com/premium-numbers)

Enter the meeting ID and passcode followed by #

Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

https://drupal.star.bnl.gov/STAR/public/star-run21-22-bur

Agenda:

• Cases for "Other" programs
  • Light Flavor (Daniel Cebra) 
  • ...
• Plots for Physics Highlight sections
  • ...
• AOB

BlueJeans:

Meeting URL
https://bluejeans.com/822956697?src=join_info

Meeting ID
822 956 697

Want to dial in from a phone?

Dial one of the following numbers:
+1.408.419.1715 (United States(San Jose))
+1.408.915.6290 (United States(San Jose))
(see all numbers - https://www.bluejeans.com/premium-numbers)

Enter the meeting ID and passcode followed by #

Connecting from a room system?
Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode

 https://drupal.star.bnl.gov/STAR/public/star-run21-22-bur

Please make your choices on doodle poll for a new/better meeting time:

https://doodle.com/poll/kzhicb9ctdz83x7r


To join the Meeting
https://bluejeans.com/934506067

To join via Room System:
Video Conferencing System: bjn.vc -or-199.48.152.152
Meeting ID : 934506067

To join via phone :
1)  Dial:
+1.408.740.7256 (US (San Jose))
+1.888.240.2560 (US Toll Free)
+1.408.317.9253 (US (Primary, San Jose))
(see all numbers - http://bluejeans.com/numbers)
2)  Enter Conference ID : 934506067

1) Organizational news
a. HF co-conveners rotation: Barbara Trzeciak (incoming), Zebo Tang (outgoing)
b. BulkCorr split into two PWGs
- Correlations and Fluctuations (CF): Xiaofeng Luo, Hanna Zbroszczyk
- Flow, Chirality and Vorticity (FCV): Jiangyong Jia, ShinIchi Esumi, Prithwish Tribedy

Conclusions: many thanks to Zebo for his dedicated work as a co-convener of HF PWG. Warm welcome to new co-conveners, Barbara, Hanna, Prithwish. 

2) Run13 Pythia+zero-bias embedding issue
- Both test sample and full production were done on RCF
- The cause was identified to be due to a change in the xml script, in which the DAQ files are copied to $SCRATCH/$INPUTFILES while the code expects $SCRATCH/
- This issue should exist also for the test sample. Why wasn't this caught?
- Need PWGs' help to setup standard QA macro for Pythia+zero-bias embedding samples to check both log files and MuDst. The current QA macro is designed for single particle embedding. 

Conclusions: SPIN PWG will follow up on why the issue was not caught in the test sample. Will coordinate between SPIN and JetCorr PWGs to develop standard QA macro for Pythia+zero-bias embedding samples to be run by the embedding team.

3) Data production progresses
- Data production: 35% done for Run17 pp 510 GeV; Isobar final production is expected to start within a week on Cori. ABC and GPC will determine whether data will be given to blinded analyzers in small chunks or one big chunk. 
- MuDst -> PicoDst: Run16 st_physics expected to finish in a couple of weeks. Will start to restage picoDst data to DD now, can free up the NFS disk space

4) New restoration request: priority list
- BulkCorr: AuAu200_production_2011, P11id_SL19c

Conclusions: the new request is to be restored as the next one in the queue. Once the picoDst files are restored to DD, corresponding MuDst files will be removed. 

5) Collaboration meeting: https://drupal.star.bnl.gov/STAR/conference/timetable/talk/51836
- Please start to populate parallel sessions. Even placeholders are helpful
- BulkCorr: please link this week's session to the page as well
- Management-convener lunch meeting: Friday (Sep. 25th) 1-3 pm BNL time

Conclusions: PWGs will add their parallel sessions to the drupal page either today or tomorrow. 

1) Data production status
- CME group has given green light to Isobar phase-III production, i.e. unblinded full data set. The production team is working on setting it up.
- Run19 19.6 GeV calibration
- Run17 pp 510 GeV st_physics: 31% completed as of Sep. 1st

Conclusions: the production team is working on setting up Isobar production on Cori. The list of runs that SPIN group needs for completing the BEMC calibration comprise about 40% of the total st_physics statistics. While these runs are close to be reconstructed, they will not be ready for the PAC meeting next week. 

2) Provisional production in light of 19.6 GeV calibration issue by Mike Lisa
- The m2 splitting issue is irrelevant for measurements of dN/deta in EPD region, v1 in EPD, and etc. 

Conclusions: conveners expressed several concerns on making provisional productions with non-final calibrations a general policy: i) could result in several provisional productions for one data set; ii) difficult to track which production is good for which analysis; iii) extra burden on the already stretched CPU and disk space resources. On the other hand, conveners suggested to reproduce the Run19 19.6 GeV calibration production with the latest calibration parameters such that users can analyze these close-to-final data. 

3) Issue with recent Run13 period 1 embedding produced on Cori: test sample on RCF was good, but production on Cori failed to pick up the correct data base information.  (slides)

Conclusions: the SPIN group found that correct database parameters were not picked up by the embedding jobs run on Cori, which was not the case for the test sample proudced on RCF. They will inform the embedding team about this inconsistency, and have the embedding dataset reproduced as soon as possible. To avoid this from happening again, it was suggested to produce a test sample on Cori before full production. One should pay extra attention to this issue if the Isobar data are to be produced on Cori given that all the work have been done on RCF so far. 

4) PWG feedback on whether MuDst.root, geant.root and pythia.root are sufficient for embedding data

Conclusions: SPIN and JetCorr PWGs confirm that these files are sufficient for their purposes. Other PWGs will bring this for discussion in the next 1-2 weeks. 

5) Collaboration meeting
- Junior's day: Sep. 14th
- Parellel session: Sep. 15th - 18th
- Plenary session: Sep. 21th - 25th

Conclusions: the BulkCorr PWG decided to dedicate the weekly PWG meetings in the next two weeks as a replacement of holding parallel sessions between Sep. 15th - 18th. 

1) Feedback on whether the current PicoDst (P11id_SL19c) for 2011 200 GeV Au+Au data satisfies PWG needs
- 2010 200 GeV Au+Au, 2012 193 GeV U+U picoDst production chain option: "picoDst PicoVtxMode:PicoVtxDefault PicoCovMtxMode:PicoCovMtxWrite PicoBEmcSmdMode:PicoBEmcSmdWrite"

Conclusions: no concerns raised from PWGs about the current PicoDst (P11id_SL19c) for 2011 200 GeV Au+Au data. Conveners will also discuss the proposed chain option for 2010 200 GeV Au+Au and 2012 193 GeV U+U picoDst production within each PWG.

2) PicoDst production request: priority list
- New request: Run14 AuAu 200 GeV st_physics, P18ih-MuDst using SL20a or beyond, requested by JetCorr

Conclusions: the new request is currently placed 4th on the priority list along with the other JetCorr request of Run12 p+p 200 GeV data. JetCorr will determine the relative order of the two requests within the PWG.

3) Template for preliminary plots request: template 

Conclusions: more comments are brought up by conveners, and we aim to converge within a week

4) STAR policy on Rivet analysis approval
- Proposal: the Rivet analysis code, implemented by PAs, will be approved within the current paper process. For people outside of STAR Collaboration who are interested in implementing Rivet analyses for STAR published results, we welcome any clarifying questions they may have, but do not officially approve these analyses. 

Conclusions: conveners agree with the proposed policy


Reminder
- Clean up old/obsolete submission