Skip to Content.
Sympa Menu

star-gpc-355-l - [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT

star-gpc-355-l AT lists.bnl.gov

Subject: STAR GPC #355

List archive

[Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT

Chronological Thread  
    < Chronological >       < Thread >
  • From: James Dunlop <dunlop AT bnl.gov>
  • To: "Feng, Yicheng" <feng216 AT purdue.edu>, STAR GPC #355 <star-gpc-355-l AT lists.bnl.gov>
  • Subject: [Star-gpc-355-l] Next meeting GPC 355 Tues Jun 6 11 am EDT
  • Date: Mon, 5 Jun 2023 09:30:08 -0400
Dear All,
  Let's meet tomorrow at 11 again.  Please look at the responses and
send others.  Unfortunately I didn't set the last zoom meeting as recurring
so 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 355
Time: This is a recurring meeting Meet anytime

Join ZoomGov Meeting
https://bnl.zoomgov.com/j/1604877838?pwd=WndoZmNQQkhaYnFiSTUvd09PMDVUZz09

Meeting ID: 160 487 7838
Passcode: 856388
One 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 US
Meeting ID: 160 487 7838
Passcode: 856388
Find your local number: https://bnl.zoomgov.com/u/ac50KJOpAh

Join by SIP
1604877838 AT sip.zoomgov.com

Join by H.323
161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 487 7838
Passcode: 856388

BEGIN:VCALENDAR
METHOD:PUBLISH
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:tzone://Microsoft/Utc
BEGIN:STANDARD
DTSTART:16010101T000000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T000000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Dunlop, James C":mailto:dunlop AT bnl.gov
DESCRIPTION:Dunlop\, James C is inviting you to a scheduled ZoomGov meeting
 .\n\n\n\nTopic: GPC 355\n\nTime: This is a recurring meeting Meet anytime\
 n\n\n\nJoin ZoomGov Meeting\n\nhttps://bnl.zoomgov.com/j/1604877838?pwd=Wn
 doZmNQQkhaYnFiSTUvd09PMDVUZz09\n\n\n\nMeeting ID: 160 487 7838\n\nPasscode
 : 856388\n\nOne tap mobile\n\n+16692545252\,\,1604877838#\,\,\,\,*856388# 
 US (San Jose)\n\n+16468287666\,\,1604877838#\,\,\,\,*856388# US (New York)
 \n\n\n\nDial by your location\n\n        +1 669 254 5252 US (San Jose)\n\n
         +1 646 828 7666 US (New York)\n\n        +1 646 964 1167 US (US Sp
 anish Line)\n\n        +1 669 216 1590 US (San Jose)\n\n        +1 415 449
  4000 US (US Spanish Line)\n\n        +1 551 285 1373 US\n\nMeeting ID: 16
 0 487 7838\n\nPasscode: 856388\n\nFind your local number: https://bnl.zoom
 gov.com/u/ac50KJOpAh\n\n\n\nJoin by SIP\n\n1604877838 AT sip.zoomgov.com<mail
 to:1604877838 AT sip.zoomgov.com>\n\n\n\nJoin by H.323\n\n161.199.138.10 (US 
 West)\n\n161.199.136.10 (US East)\n\nMeeting ID: 160 487 7838\n\nPasscode:
  856388\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20231206T050000Z;INTERVAL=1;BYDAY=TU;WKST=SU
UID:040000008200E00074C5B7101A82E00800000000F9C0B6D5B097D901000000000000000
 0100000008B1070F25D76AC4493B818B7EE517D68
SUMMARY:GPC 355 Meeting
DTSTART:20230606T150000Z
DTEND:20230606T160000Z
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20230605T132735Z
TRANSP:OPAQUE
STATUS:CONFIRMED
LOCATION:
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:P
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR


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 Fuqiang 
Thank 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 NJ
Department 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?  
Best
Sevil 







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 answer
to the isobar data; no PRL yet.  This would give that with
an 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 the
    four datapoints for which the baseline is found.  The current
    mixture of showing 7 of the measurements of which 4 have a baseline
    is confusing.

Yu:
    Feels the short paper needs some work on the general audience side
   
    Group 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 resonances
    are neutral.  What about the effect of charged resonances?
    (Yu stated that most 2 particle correlations are from neutrals like
     the rho.
     But following up: Delta++?  Are there model studies that show that this
     method 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 the
    paper, which doesn't mention Zr at all.

Meet again in 2 weeks.  In the meantime please send a full first
round 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.

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 the
papers and analysis notes and come with first comments.
Thanks,
 Jamie

Dunlop, James C is inviting you to a scheduled ZoomGov meeting.

Topic: GPC 355 Meeting
Time: May 23, 2023 11:00 AM Eastern Time (US and Canada)

Join ZoomGov Meeting

Meeting ID: 161 475 3179
Passcode: 560997
One 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 3179
Passcode: 560997
Find your local number: https://bnl.zoomgov.com/u/aCyiCASz5

Join by SIP

Join by H.323
161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 161 475 3179
Passcode: 560997
<GPC 355 Meeting.ics>


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 at 
for the next 2 weeks for an inaugural meeting.  Please fill that out
when 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 Dunlop
Member(s) at large: Yu Hu
Member for English/Grammar QA: Sevil Salur
Member for Code QA: Ankita Nain
PWG representative: Prithwish Tribedy
PA 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 Manuscript: 
 
 
Code: $CVSROOT/offline/paper/psn0811
 
 
 
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

-- 
Sooraj Radhakrishnan
Research Scientist,
Department of Physics
Kent State University
Kent, OH 44243

Physicist Postdoctoral Affiliate
Nuclear Science Division
Lawrence Berkeley National Lab
MS70R0319, One Cyclotron Road
Berkeley, CA 94720
Ph:  510-495-2473

--
He/Him/His
Please do not feel obligated to respond to this message outside of your work hours.
James C Dunlop Ph.: (631) 344-7781                       
Building 510A         Cell: (631)316-8153
P.O. Box 5000                      
Brookhaven National Laboratory
Upton, 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-7781                       
Building 510A         Cell: (631)316-8153
P.O. Box 5000                      
Brookhaven National Laboratory
Upton, 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-7781                       
Building 510A         Cell: (631)316-8153
P.O. Box 5000                      
Brookhaven National Laboratory
Upton, 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-7781                       
Building 510A         Cell: (631)316-8153
P.O. Box 5000                      
Brookhaven National Laboratory
Upton, 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-7781                       
Building 510A         Cell: (631)316-8153
P.O. Box 5000                      
Brookhaven National Laboratory
Upton, NY 11973
dunlop AT bnl.gov










Archive powered by MHonArc 2.6.24.

Top of Page