Skip to Content.
Sympa Menu

star-fcv-l - Re: [Star-fcv-l] Inputs for run-by-run QA variables for new data sets

star-fcv-l AT lists.bnl.gov

Subject: STAR Flow, Chirality and Vorticity PWG

List archive

Chronological Thread  
  • From: ShinIchi Esumi <esumi.shinichi.gn AT u.tsukuba.ac.jp>
  • To: "STAR Flow, Chirality and Vorticity PWG" <star-fcv-l AT lists.bnl.gov>
  • Subject: Re: [Star-fcv-l] Inputs for run-by-run QA variables for new data sets
  • Date: Mon, 18 Oct 2021 02:32:06 +0900

Dear Ashik and all
Thanks for the initiation. I have a few comments and questions.
I was wondering why you have chosen to use Q-vectors in stead of more direct
average <phi> at least for TPC, since you do have also average <eta> and
<pT>.
But maybe Q-vector would be directly used by the analysis, and could be more
sensitive to the location of dead azimuthal sector than <phi>, so it might be
more
reasonable as well, though. Another question is about the vertex qualities,
such
as run-by-run average vertex position in radial/xy and z direction? The
“average
DCAxy/z in each event” was also found to be a good indicator for removing bad
events in BES1 especially for central events in fluctuation analysis, so I
was also
wondering if run-by-run selection based on such DCA related information as
well,
but this might be too much for the current initial QA studies especially for
the
general centrality. Thanks again.
Best regards, ShinIchi

> On Oct 18, 2021, at 1:49, Prithwish Tribedy via Star-fcv-l
> <star-fcv-l AT lists.bnl.gov> wrote:
>
> Hi Ashik and all,
> During our isobar analysis we compiled a list of observables. This may
> give us some clue about which quantities are important:
> https://drupal.star.bnl.gov/STAR/system/files/summary_qa_step2.html
>
> I would still encourage people to provide input before Friday.
> Best,
> Prithwish
>
>
> On 2021-10-17 12:36, ASHIK IKBAL via Star-fcv-l wrote:
>> Hi FCV folks,
>> We had a discussion on the QA variables for new and upcoming data sets
>> in the last week QA board meeting. So far we (the QA team) are using
>> the following variables for 19.6 GeV run-by-run QA analysis:
>> 1 runidvsrefmult
>> 2 runidvstofmatched
>> 3 runidvsavgpt
>> 4 runidvsavgeta
>> 5 runidvsavgQ1x
>> 6 runidvsavgQ1y
>> 7 runidvsavgQ2x
>> 8 runidvsavgQ2y
>> 9 runidvsavgEpdQ1x
>> 10 runidvsavgEpdQ1y
>> 11 runidvsavgEpdQ2x
>> 12 runidvsavgEpdQ2y
>> 13. runidvsbemcmatched
>> The list of badruns (identified based on the QA variables using
>> automated run-by-run QA algorithm) is really necessary for the
>> centrality team. The QA board has set a deadline of next Friday (Oct.
>> 22) to finalize the variables.
>> Please speak up if anyone wants to look at any other variables for the
>> run-by-run QA analysis.
>> Thanks,
>> Ashik
>> --
>> Ashik Ikbal
>> Research Associate
>> Kent State University
>> Department Of Physics
>> Kent, OH 44242, USA
>> Contact no.s: +1 631-504-7647 (USA)
>> +91 8250216234 (India)
>> Alternate e-mails: asheikh2 AT kent.edu
>> ashik AT rcf.rhic.bnl.gov
>> ashik.ikbal.sheikh AT cern.ch
>> _______________________________________________
>> Star-fcv-l mailing list
>> Star-fcv-l AT lists.bnl.gov
>> https://lists.bnl.gov/mailman/listinfo/star-fcv-l
> _______________________________________________
> Star-fcv-l mailing list
> Star-fcv-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/star-fcv-l





Archive powered by MHonArc 2.6.24.

Top of Page