star-gpc-355-l AT lists.bnl.gov
Subject: STAR GPC #355
List archive
Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT
- From: Ankita Nain <nainankita55555 AT gmail.com>
- To: "Feng, Yicheng" <feng216 AT purdue.edu>, "STAR GPC #355" <star-gpc-355-l AT lists.bnl.gov>
- Subject: Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT
- Date: Mon, 12 Jun 2023 00:50:57 +0530
Hello,
For code QA I was able to run the code and reproduce the plots. I am attaching the file showing some of them.
Best regards,
Ankita
On Sat, 10 Jun 2023 at 22:45, Feng, Yicheng via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov> wrote:
_______________________________________________Hi All,
We modified the drafts according to the comments we have received so far.We followed Jamie's comment and modified the money plot to include all data points as the STAR blind analysis. (long: Fig13; short: Fig3)We also added some discussions in the text for Sevil's and Yu's comments.
The detailed response can be found through the link belowwhich has been uploaded to the drupal webpage together with other related files:→revised long paper: https://drupal.star.bnl.gov/STAR/system/files/IsobarNfBkg_L_v10.pdf→revised short paper: https://drupal.star.bnl.gov/STAR/system/files/IsobarNfBkg_S_v8.pdf
Please let me know if you have any further comments.
Sincerely,Yicheng for the PAs
From: Star-gpc-355-l <star-gpc-355-l-bounces AT lists.bnl.gov> on behalf of James Dunlop via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov>
Sent: Tuesday, June 6, 2023 11:19 AM
To: STAR GPC #355 <star-gpc-355-l AT lists.bnl.gov>
Subject: Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT
---- External Email: Use caution with attachments, links, or sharing data ----
Dear All,This was a lightly attended meeting (Yicheng, Ankita, and me). Please let me know privatelyif we need to find a different time next week. On this email list I encourage people to lookat Yicheng's responses, and to send out further comments focusing on:
i) Basic physics and technical questionsii) Suggestions on how to target the PRLiii) Detailed suggestions on the PRL and PRC
Ankita did report that the Code seems to be in good shape and willsend a message to this list on the Code QA reproducibility status.
On Yicheng's response:I reiterated my preference that the figure should either show onlythe 4 values for which the baseline is found or the full 12, with a preferencefor the 4 values.
We should try to have some more back and forth on the correlationquestion on this mailing list, and if there are any other technicalquestions. But, we should also get started on some of the moredetailed line by line comments to push this GPC's work forward.Thanks,Jamie
On Jun 5, 2023, at 9:30 AM, James Dunlop <dunlop AT bnl.gov> wrote:
Dear All,Let's meet tomorrow at 11 again. Please look at the responses andsend others. Unfortunately I didn't set the last zoom meeting as recurringso this is a different one (this time I made it recurring).Thank you,Jamie
Dunlop, James C is inviting you to a scheduled ZoomGov meeting.
Topic: GPC 355Time: This is a recurring meeting Meet anytime
Join ZoomGov Meeting
Meeting ID: 160 487 7838Passcode: 856388One tap mobile+16692545252,,1604877838#,,,,*856388# US (San Jose)+16468287666,,1604877838#,,,,*856388# US (New York)
Dial by your location+1 669 254 5252 US (San Jose)+1 646 828 7666 US (New York)+1 646 964 1167 US (US Spanish Line)+1 669 216 1590 US (San Jose)+1 415 449 4000 US (US Spanish Line)+1 551 285 1373 USMeeting ID: 160 487 7838Passcode: 856388Find your local number: https://bnl.zoomgov.com/u/ac50KJOpAh
Join by SIP
Join by H.323161.199.138.10 (US West)161.199.136.10 (US East)Meeting ID: 160 487 7838Passcode: 856388
On Jun 4, 2023, at 11:40 AM, Feng, Yicheng via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov> wrote:
Hi All,
I collected the comments I have got since the last GPC meeting,which include the meeting minutes from Jamie's email and the follow-up comments from Sevil's email [line 35-61].
After discussions among PAs, we wrote down our responses,which has been uploaded to the paper webpage on drupal:or directly through this link:
I had a zoom meeting with Ankita last Friday for code QA [line 29-34],and we will continue working on this.
Please let me know if you have any new comments.
Sincerely,Yicheng for the PAs
From: Star-gpc-355-l <star-gpc-355-l-bounces AT lists.bnl.gov> on behalf of Sevil Salur via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov>
Sent: Wednesday, May 24, 2023 7:26 AM
To: Wang, Fuqiang <fqwang AT purdue.edu>
Cc: STAR GPC #355 <star-gpc-355-l AT lists.bnl.gov>
Subject: Re: [Star-gpc-355-l] First meeting next Tues May 23 at 11_______________________________________________
---- External Email: Use caution with attachments, links, or sharing data ----
Dear FuqiangThank you for clarifying. Are you referring to the discussion in Sec 3.2 in the paper for the data driven assessment? Is there a particular subsection in the AN that I should look at for the sys study etc?Best regards
Sevil Salur
Associate Professor,-----------------------------------------------Rutgers, The State University of NJDepartment of Physics & Astronomy,
136 Frelinghuysen Rd,
Piscataway, NJ 08854
Phone: 1 (848) 445 8784------------------------------------------------she/her/hers
On May 23, 2023, at 9:26 PM, Wang, Fuqiang <fqwang AT purdue.edu> wrote:
Hi Sevil,
Those will also be a background source (any known physics that contributes to the OS-SS difference will be background). The physics nature of the background isn’t important to the analysis. One doesn’t need/want to quantify each possible individual background source; that wouldn’t be robust. We try to use data wherever possible to assess nonflow effect, and where we cannot, we try to assess a conservative syst uncertainty.
Best regards,Fuqiang
On May 24, 2023, at 2:38 AM, Sevil Salur via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov> wrote:
---- External Email: Use caution with attachments, links, or sharing data ----
Thank you Jamie,_______________________________________________Also to follow up on the 3p correlation vs 2p correlations estimate, is there any study that you can point to the effect of 3 particle decay of a resonance of which only 2 same sign are measured due to in efficiency/acceptance of the detector (ex: sigma(1385)—> lambda+pi—>proton+pi(-)+pi but only proton and pi) and repeat the same for the positive charge. It can be that there is no correlation remaining for the 2 of the 3 particles, but do we know that?BestSevil
On May 23, 2023, at 12:45 PM, James Dunlop via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov> wrote:
Notes from first meeting:_______________________________________________May 23, 2023
Prithwish gave a background on history in PWG.
Sevil: as a bit of an outside observer of the CME world questioning why the PRL is necessary
Answer (Prithwish, Yicheng)is that the community is expecting a compact answerto the isobar data; no PRL yet. This would give that withan explainable upper limit.
Conclusion: the PRL needs to be crafted to make that clear.
Yu and Jamie:On the baseline plot: either show with all 12 datapoints of original PRC plot or only thefour datapoints for which the baseline is found. The currentmixture of showing 7 of the measurements of which 4 have a baselineis confusing.
Yu:Feels the short paper needs some work on the general audience sideGroup names: drop individual group names and stick to Group 1,2, etc.
Ankita:Started looking at the code and the analysis note.Read the analysis note. Yu and Ankita will discuss separately.
Sevil:Question about 2-particle correlation: OS-SS assumes all resonancesare neutral. What about the effect of charged resonances?(Yu stated that most 2 particle correlations are from neutrals likethe rho.But following up: Delta++? Are there model studies that show that thismethod gets all 2 particle correlations?)This needs a followup, maybe a model analysis.
Yu:Question about upper limit: very specifically on Ru.Slightly different for Zr. Needs to be a bit clearer in thepaper, which doesn't mention Zr at all.
Meet again in 2 weeks. In the meantime please send a full firstround of comments to the list.
--J
On May 16, 2023, at 11:38 AM, James Dunlop via Star-gpc-355-l <star-gpc-355-l AT lists.bnl.gov> wrote:
Trying again with just one recipient.<GPC 355 Meeting.ics>
Begin forwarded message:
From: James Dunlop <dunlop AT bnl.gov>
Subject: First meeting next Tues May 23 at 11
Date: May 16, 2023 at 11:36:54 AM EDT
Cc: James Dunlop <dunlop AT bnl.gov>, Sooraj Radhakrishnan <skradhakrishnan AT lbl.gov>, Sevil Salur <salur AT physics.rutgers.edu>, Ankita Nain <nainankita55555 AT gmail.com>, Prithwish Tribedy <ptribedy AT bnl.gov>, Prithwish Tribedy <prithwish2005 AT gmail.com>, "Feng, Yicheng" <feng216 AT purdue.edu>, Fuqiang Wang <fqwang AT purdue.edu>, subhash <subhash AT rcf.rhic.bnl.gov>, Zhenyu Chen <zhenyuchen AT sdu.edu.cn>, Barbara Trzeciak <barbara.trzeciak AT gmail.com>, Frank Geurts <geurts AT rice.edu>, Lijuan Ruan <ruan AT bnl.gov>, Yu Hu <yuhu AT lbl.gov>
Dear All,We will have our first meeting next Tues May 23 at 11.Zoom info below and an ICS invite. Please read through thepapers and analysis notes and come with first comments.Thanks,Jamie
Dunlop, James C is inviting you to a scheduled ZoomGov meeting.
Topic: GPC 355 MeetingTime: May 23, 2023 11:00 AM Eastern Time (US and Canada)
Join ZoomGov Meeting
Meeting ID: 161 475 3179Passcode: 560997One tap mobile+16692545252,,1614753179#,,,,*560997# US (San Jose)+16469641167,,1614753179#,,,,*560997# US (US Spanish Line)
Dial by your location+1 669 254 5252 US (San Jose)+1 646 964 1167 US (US Spanish Line)+1 646 828 7666 US (New York)+1 551 285 1373 US+1 669 216 1590 US (San Jose)+1 415 449 4000 US (US Spanish Line)Meeting ID: 161 475 3179Passcode: 560997Find your local number: https://bnl.zoomgov.com/u/aCyiCASz5
Join by SIP
Join by H.323161.199.138.10 (US West)161.199.136.10 (US East)Meeting ID: 161 475 3179Passcode: 560997_______________________________________________
On May 13, 2023, at 4:53 PM, Yu Hu <yuhu AT lbl.gov> wrote:
Dear Jamie, and All,
As you may know Yicheng and I are taking STAR shift for this and the next week. I'm on the day shift, he is on the night shift. And I will be on travel until 25th.I think since I followed most of his work in the CME group meeting, and it is the first GPC meeting, please feel free to hold the meeting next week if everyone else is available.I'll try to join if the shift is less busy, or if you can take a record, I can follow up after the meeting by the record video and email.
Thank you.Best,Yu
On Thu, May 11, 2023 at 3:25 PM James Dunlop <dunlop AT bnl.gov> wrote:
Dear All,Thank you all for agreeing to serve on this committee.
I've set up a when2meet atfor the next 2 weeks for an inaugural meeting. Please fill that outwhen you can. I'd prefer a first meeting next week if possible.
Thanks,Jamie
On May 11, 2023, at 3:14 PM, Sooraj Radhakrishnan <skradhakrishnan AT lbl.gov> wrote:
Dear Jamie, Yu, Sevil, Ankita, Prithwish, Yicheng,
Thank you for agreeing to serve on the God Parent Committee (GPC) for the new STAR paper. The committee members are:=========================Chairperson: James DunlopMember(s) at large: Yu HuMember for English/Grammar QA: Sevil SalurMember for Code QA: Ankita NainPWG representative: Prithwish TribedyPA representative: Yicheng Feng
Information on the STAR paper to be reviewed by the GPC :=========================Paper title: Estimate of Background Baseline and Upper Limit on the Chiral Magnetic Effect in Isobar Collisions at $sqrt{s_{NN}}$=200 GeV at the BNL Relativistic Heavy-Ion Collider
PAs: Yicheng Feng, Fuqiang Wang
Targeted journal: Phys. Rev. Lett (short version), Phys. Rev. C (long version)
Paper webpage: https://drupal.star.bnl.gov/STAR/blog/fengyich/Background-Baseline-CME-Isobar-Collisions-Webpage
Paper Manuscript:Short version: https://drupal.star.bnl.gov/STAR/system/files/IsobarNfBkg_S_v7.pdf
Long version: https://drupal.star.bnl.gov/STAR/system/files/IsobarNfBkg_L_v9.pdf
Analysis note: https://drupal.star.bnl.gov/STAR/starnotes/private/PSN0811
Code: $CVSROOT/offline/paper/psn0811
PWGC preview notes: https://drupal.star.bnl.gov/STAR/event/2023/02/17/STAR-PWGC-meeting#comment-2205
Charge to GPC:=========================The GPC is requested to review the new STAR paper indicated above, and let STAR Management know when it is considered ready for review by STAR. The GPC should ensure that the presentation of the physics message and data is clear and impactful. It should take into account the logical flow and construction as well as the technical accuracy and correctness of the analysis.
Please note that a dedicated mailing list (https://lists.bnl.gov/mailman/listinfo/star-gpc-355-l) has been created for this GPC, and all the PAs and GPC members have been subscribed. Please use this mailing list for all GPC communications, which will be archived automatically.
When the GPC Chair writes to the PAC/Spokespeople to ask for release to the collaboration review. The PAC/Spokespeople will download acknowledgements, and send to the PAs for inclusion into the paper draft. "The STAR Collaboration" will be used as the author. The PAs and GPC should not be using an author list up to that point.
It is highly recommended that PAs prepare YAML data tables to be uploaded to HepData before the paper is announced to RHIC. Instructions on preparing YAML tables can be found here: https://drupal.star.bnl.gov/STAR/blog/marr/instructions-hepdata-submission.
More information about the paper submission procedure can be found here: https://www.star.bnl.gov/central/collaboration/authors/
Guidance to GPC :=========================Guidance for the GPC process is described in the STAR publication policy item 14.
The Technical Notes and codes should be revised as necessary during the GPC process. The purpose of the STAR Technical note accompanying every paper is to describe the analysis, data and methods used, and all necessary background information. This would then allow each collaboration member, if desired, to repeat the analysis at a later time in the exact same fashion and reproduce the results published. A member in the GPC is assigned the responsibility to check, in discussion with PAs, if the analysis code compiles and processes the designated data set. When the paper is released by the GPC to the spokesperson for next steps towards publication, the PA's, in agreement with the GPC chair, are required to provide a note on the changes made to the Technical Note if any and the code check has been satisfactorily completed.
The manuscript recommended to the collaboration by the GPC should be a finished, sound, grammatically correct scientific publication ready for journal submission aside from final comments and tuning by the Collaboration at large. The GPC is requested to ensure that when the manuscript is released to management it should have the latest author list of STAR Collaboration, obtainable from the STAR web page and the latest acknowledgments.
It is presumed that most of your work can be carried out through email correspondence and also by phone/SeeVogh/BlueJeans conferences. If you require a meeting or direct discussion with the principal authors, then that should be also possible. Once you are satisfied with the manuscript, then STAR Management should be informed and it will be announced to STAR that the paper is available for review and comments by STAR for a two week period. At or near the end of those two weeks, the principal authors will be asked to prepare a modified version which addresses suggested changes with a statement about those changes that they feel are not warranted. This latter statement can take place in the form of email responses as the comments from STAR arrive and should be logged for reference if questions arise later. The God Parent Committee or GPC Chair may be asked for final review of the revised version before journal submission if deemed necessary.
Thanks and Best regards,Sooraj--
Ph: 510-495-2473Berkeley, CA 94720Sooraj Radhakrishnan
Research Scientist,Department of Physics
Kent State UniversityKent, OH 44243Nuclear Science Division
Physicist Postdoctoral Affiliate
Lawrence Berkeley National Lab
MS70R0319, One Cyclotron Road
--He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.James C Dunlop Ph.: (631) 344-7781Building 510A Cell: (631)316-8153P.O. Box 5000Brookhaven National LaboratoryUpton, NY 11973
--He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.James C Dunlop Ph.: (631) 344-7781Building 510A Cell: (631)316-8153P.O. Box 5000Brookhaven National LaboratoryUpton, NY 11973
--He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.James C Dunlop Ph.: (631) 344-7781Building 510A Cell: (631)316-8153P.O. Box 5000Brookhaven National LaboratoryUpton, NY 11973
Star-gpc-355-l mailing list
Star-gpc-355-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-gpc-355-l
--He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.James C Dunlop Ph.: (631) 344-7781Building 510A Cell: (631)316-8153P.O. Box 5000Brookhaven National LaboratoryUpton, NY 11973
Star-gpc-355-l mailing list
Star-gpc-355-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-gpc-355-l
Star-gpc-355-l mailing list
Star-gpc-355-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-gpc-355-l
Star-gpc-355-l mailing list
Star-gpc-355-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-gpc-355-l
--He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.James C Dunlop Ph.: (631) 344-7781Building 510A Cell: (631)316-8153P.O. Box 5000Brookhaven National LaboratoryUpton, NY 11973
--He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.James C Dunlop Ph.: (631) 344-7781Building 510A Cell: (631)316-8153P.O. Box 5000Brookhaven National LaboratoryUpton, NY 11973
Star-gpc-355-l mailing list
Star-gpc-355-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-gpc-355-l
Attachment:
CodeQA_plots.pdf
Description: Adobe PDF document
-
Re: [Star-gpc-355-l] First meeting next Tues May 23 at 11,
Feng, Yicheng, 06/04/2023
-
[Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT,
James Dunlop, 06/05/2023
-
Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT,
James Dunlop, 06/06/2023
-
Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT,
Feng, Yicheng, 06/10/2023
- Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT, Ankita Nain, 06/11/2023
-
Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT,
Feng, Yicheng, 06/10/2023
-
Re: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT,
James Dunlop, 06/06/2023
-
[Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT,
James Dunlop, 06/05/2023
Archive powered by MHonArc 2.6.24.