STAR PWGC meeting
Updated on Thu, 2021-01-28 09:26. Originally created by marr on 2021-01-28 09:26.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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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.
- 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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
STAR PWGC meeting
Updated on Fri, 2021-06-04 10:24. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
- DAQ production
- Run17 pp 510 st_physics (94%, finish by the end of June), st_rp (52%)
- Run19 19.6 GeV
- Need to fix memory leak in SL21b
- eTOF calibration expected to finish by the end of the week
- Should be ready for production by mid-June if not earlier
- 2.5 months production time with 50% of farm
- MuDst -> PicoDst
- 2012 pp 200 GeV production waiting for SL21c
- Data restoration
- 2016 AuAu200 P16ij.SL20c and P16ij.SL19c (almost done)
2) Discussion of data production priority (Current priority list, Dan's slides)
Initial draft by Dan Cebra
-
Run19 19.6 COL
➔ Most mature calibrations, Top Energy BES-II, papers are ready to go -
(Run19+20) 31.2 FXT (7.7) > Run 19 4.59 FXT (3.2)
➔Overlapping coverages needed to understand iTPC/eTOF performance -
Run21 7.7 COL
➔Needed to compare to FXT, has always been a top physics priority (Long run) -
Run 19 200 COL
➔Short run, unique trigger, can help us prepare for Run23-25 -
Run20 5.75 FXT (3.5) > (Run19+20) 7.3 FXT (3.9) > Run20 9.8 FXT (4.5) > Run20 13.5 FXT (5.2) > Run20 19.5 FXT (6.2)
➔ Should run FXT first, new energies, short runs
-
Run19 14.6 COL > Run20 11.5 COL > Run20 9.2 COL
➔The remaining BES-II collider systems
-
Run 21 Opportunities: 3.85 FXT I (3.0) > 44.5 FXT (9.2) > 70 FXT (11.5) > 100 FXT (13.7) > 200 GeV O+O > 17.3 COL > 3.85 FXT II (3.0) > (Run20+21) 26.5 FXT (7.2) > (200 GeV d+Au ?)
➔ This priorities ordering was worked out in the BUR and approved by the NPP PAC
- Reverse priority 3) and 4), since 4) is important for next year's BUR and takes much less time to produce than 3)
- For opportunistic datasets taken in 2021, people can analyze fast offline or express production data to see if there are strong physics motivation to bump up production priority
- Conveners suggested to bring this up for discussion at weekly meetings in the next 1-2 weeks
3) Analysis meeting (June 28th-30th, DRAFT AGENDA)
Conclusions: agenda modified taking into account conveners' comments
No PWGC meeting next week due to 2021 RHIC&AGS AUM
STAR PWGC meeting
Updated on Thu, 2021-01-28 09:26. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
STAR PWGC meeting
Updated on Fri, 2021-06-18 13:37. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
NOTES
2) Discussion of data production priority (Current priority list, Dan's slides)
-
Run19 19.6 COL
-
(Run19+20) 31.2 FXT (7.7) > Run 19 4.59 FXT (3.2)
-
Run 19 200 COL
-
Run21 7.7 COL
-
Run20 5.75 FXT (3.5) > (Run19+20) 7.3 FXT (3.9) > Run20 9.8 FXT (4.5) > Run20 13.5 FXT (5.2) > Run20 19.5 FXT (6.2)
-
Run19 14.6 COL > Run20 11.5 COL > Run20 9.2 COL
-
Run 21 Opportunities: 3.85 FXT I (3.0) > 44.5 FXT (9.2) > 70 FXT (11.5) > 100 FXT (13.7) > 200 GeV O+O > 17.3 COL > 3.85 FXT II (3.0) > (Run20+21) 26.5 FXT (7.2) > (200 GeV d+Au ?)
3) dN/dx for BES-II production (CPU time increases by about 15%)
Conclusions:
- no immediate interests from PWGs for including dN/dx in BES-II production. 19.6 GeV data production will proceed without dN/dx.
- PWG can check the performance of dN/dx once a data sample is ready for analysis. We will then come back to the discussion whether it is worth including dN/dx given the increase in CPU time
4) Analysis meeting: PWG report or analysis highlight (Agenda)
5) Clean up obsolete presentation submission (Presentations)
6) Conferences/Workshops
- DNP 2021, Oct. 11-14, abstract due Jul. 1st, Boston, in person, http://web.mit.edu/dnp2021/
STAR PWGC meeting
Updated on Mon, 2021-03-22 12:22. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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:
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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)
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
Proposal page: https://drupal.star.bnl.gov/STAR/blog/slhuang/measurements-v2-v3-pau-dau-and-3heau-collisions-%C2%AD200-gev-star-collaboration
NOTES
- 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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
Proposal page: https://drupal.star.bnl.gov/STAR/blog/chunjian/probing-quadrupole-deformation-uranium-relativistic-nuclear-collisions
NOTES
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.
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
- 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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
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.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
- 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
STAR PWGC meeting
Updated on Fri, 2021-05-07 13:51. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
Conclusions: the trigger system upgrade is solely for DSM and QT boards. Will collect more information to facilitate the discussion.
3) Status of Run19 19.6 GeV calibration: remaining m2 splitting between proton and anti-proton, which depends on momentum, TPC east/west, phi. (Detailed study: SLIDES). What is the precision needed for fluctuation analysis?
- TPC group continues investigating this
Conclusions: influence of the observed momentum distortion on proton fluctuation measurements will be checked using UrQMD. Analyzers could also check possible m2 splitting vs. (p, phi, eta) in other data sets, as all the information is available in PicoDst.
4) Is repairing damaged eTOF electronics (~20% reduction in efficiency) critical for 2023-25? If so, for which analyses?
Conclusions: conveners will bring this up for discussion in PWGs. Will come back to this discussion in the near future.
5) Any physics motivation for running BSMD in 2022? Or save it for later years?
Conclusions: since there are no parts available for repair, the consensus is not to run BSMD in 2022 and save it for 2023+.
STAR PWGC meeting
Updated on Fri, 2021-05-14 15:14. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
Proposal page: https://drupal.star.bnl.gov/STAR/blog/lkosarz/upsilon-production-pp-500-gev
NOTES
2) BES-II data production
- Strategy 1: start the production now with the current calibration parameters (small m2 splitting: SLIDES). Reproduce when/if the calibration is improved
- Strategy 2: wait for improved calibration before production
Conclusions: PWGs are in favor of starting data production with the current TPC parameters, but wait for eTOF calibration to finish. The remaining issue of m2 splitting should be made clear to analyzers, and impacts on analyses need to be evaluated.
- Prepare for 2022 QM
- New data from 2021: 7.7 COL, 3.85 FXT, 44.5 FXT, 70 FXT, 100 FXT, 200 O+O
Conclusions: Dan will compose a preliminary priority list, and we will discuss later.
STAR PWGC meeting
Updated on Fri, 2021-05-28 16:08. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 13:30 (GMT), duration : 00:00
Proposal page: https://www.star.bnl.gov/protected/lfsupc/nasim/webpage_54gev/
NOTES
2) Data production for low energy FXT data: use proton hypothesis in the tracking?
- What are potential benefits and drawbacks (Lambda mass)? What is the metric to make the decision? What is the switching energy?
- What about trying different mass hypotheses and pick the best one? Will increase CPU time though
Conclusions: there is no desire from PWG to switch to proton hypothesis for FXT data. It was pointed out that even at lowest FXT energy, there are still more pions (both charges) than protons. In terms of trying different mass hypotheses for tracking, some R&D effort from PWG, in collaboration with S&C, would be needed to check the impact on CPU time and performance.
3) Use improved start-less T0 calculation for TOF PID in BES-II data production
- Improved algorithm: SLIDES
- Run19 19.6 GeV performance: SLIDES
Conclusions: PWGs agree that this improvement is desired for BES-II data.
4) Analysis meeting (June 28th-30th, DRAFT AGENDA)
Conclusions: PWGs agree with the proposed dates. One possible topic is the status report on net-proton fluctuation analysis using express production of 7.7 GeV COL data. CF PWG will follow up on the status of the analysis.
5) Proposal: when releasing new figures with theory curves, suggest to confirm with theorists that their calculations are plotted and labelled properly.
Conclusions: conveners will keep an eye on this
6) Feedback to conference speakers, especially juniors
Conclusions: it will be good if we can follow up with speakers in case there were difficult questions, to make sure they understand the questions and answers. This is especially needed for online meetings.
STAR PWGC meeting
Updated on Mon, 2021-03-15 09:39. Originally created by marr on 2021-01-28 09:26.https://bnl.zoomgov.com/j/1619294511?pwd=TkRhZzFjOWZSQnpvUVdGUGFVMmlHdz09, at 14:30 (GMT), duration : 00:00
Proposal page: https://drupal.star.bnl.gov/STAR/blog/starkong/upc-jpsi-dau-200-gev-paper-proposal-1
NOTES
2) CPOD merges (MERGE LIST)
Conclusions: PAs, conveners and PAC will follow up this.
3) Upcoming conferences
- Collaboration meeting: move management-convener meeting to Thursday (Mar. 11th) 1-3 pm, to avoid conflicts with EIC IP6 kick-off meeting
- sQM: abstract due Mar. 8th: FCV (8), CF (7), HF (1), LFSUPC (4)
4) Discussion: should be small restoration requests treated differently? If so, how we do define "small"?
Conclusions: for fast restoration requests (< 2 days), they could be expedited after discussion within the convener panel. Each such request will be treated on a case-by-case basis.
5) Is it necessary to have a list of items that should be included in an analysis note?
Conclusions: conveners agree that such a list would be useful for PAs preparing analysis note. An old such list already exists (https://www.star.bnl.gov/protected/common/GPCs/TechnicalNote.html), and conveners will take a look at it and suggest modifications if needed.