subhash's blog

refmultCorrUtil = new StRefMultCorr();
refmultCorrUtil -> init(runnumber);
refmultCorrUtil->initEvent(refMult, VertexZPos, zdc_cons);
Bad run rejection from RefMultCorr: if(refmultCorrUtil->isBadRun(runnumber))

Event plane reconstruction: pt > 0.2 && pt < 2 GeV/c
|eta| < 1.0
|dca| < 2.0
NhitsFit > 15
NhitsFit/MaxHIts > 0.55
use pt-weight, re-centering and shifting

Single track cuts:
pt > 0.2, pt < 10 GeV/c
|eta| < 1.0
|dca| < 2.0
NhitsFit > 15
NhitsFit/MaxHIts > 0.55

IsPion=false; IsKaon=false;
PID: if (beta > 0 && pass mass-square cut) IsPion=true; IsKaon=true;
if(pass-TPC-Nsigma-cut) IsPion=true; IsKaon=true;

Before pair-loop, store track those passed quality cuts in PID cuts in array: pion and kaon array
Pair-loop:

Loops over pion and kaon arrays track pairs:
Apply |pair-rapidity| < 1.0
Fill histogram

Autocorrelation subtraction for TPC event plane ....
store an index for tracks participating in event plane reconstruction:
if(pt > 0.2 && pt< 2.0 && dca<2.0 && fabs(eta)<=1.0 && nHitsFit >= 15 && ratio>=0.55 && ratio < 1.05) trkin = 1; //flow track

Then in K*-loop (pair loop)
if the daughter participates in event plane, subtract the q-vector it from the Q-vector (full event flow Q vector)

if(flow_indx_kaon) /* trackin */
{
Q_eta_full_i = Q_eta_full_i - Q_Daughter1;
}

if(flow_indx_pion) /* trackin */
{
Q_eta_full_i = Q_eta_full_i - Q_Daughter2;

}

------------------------------------------------------------------------------------------------

Chensheng:

Trigger ID:
if(!((mEvent->isTrigger(350003))|| (mEvent->isTrigger(350013))|| (mEvent->isTrigger(350023))|| (mEvent->isTrigger(350033))|| (mEvent->isTrigger(350043)) )) return kTRUE;

|vz| < 30 cm, |vr|< 2.0 cm, Vz-VpdVz < 3 cm

Centrality condition:

mRefmultCorr = new StRefMultCorr();

mRefmultCorr->init(mEvent->runId());
if(mRefmultCorr->isBadRun(mEvent->runId()))

cut on no. of tof-matched tracks [REMOVED]
if(n_Tof_match < 3) return kStOK; [REMOVED]

Event plane reconstruction:

if(fabs(eta)<=1.0 && pt<=2.0 && pt>=0.2 && gdca<=2. && gdca>=0. && nHitsFit>15 && ratio>0.55)
use pt weight, re-centering and shifting

Single track cuts:
if(p_1<0.2 || p_1>10) continue;
if(nHitsFit_1<=15) continue;
if(ratio_1<0.55) continue;
if(fabs(eta_1)>1.0) continue;
if(gdca_1>2.0) continue;

PID:
if(beta > 0 && pass-tof-mass-square-cut) passTof = 1;
if(pass-TPC-sigma-cut) passTpc = 1
if(passTof==0 && passTof==0) continue;

Pair-loop:
Loops over all the possible track pairs:
If single tracks passed the above cuts && |pair-rapidity| < 1.0
Fill histogram

Autocorrelation subtraction for TPC event plane
Implemented for full event plane
------------------------------------------------------------------------------------------------

For Chensheng, next step is to get TPC event calibration files for run-11 data.

Jan-11, 2021

TPC calibration DONE.

------------------------------------------------------------------------------------------------
Jan-12, 2021

We found discrepancies in combinatorial background among us.

Histogram entries in same event and rotation background matched when integrated over cos (theta) bins.
For different cos(theta) bins, sig>>bg for cos(theta)~0, and sig<<bg for cos(theta)~1

Chensheng, found he didn't have EP autocorrelation subtraction for rotation-pairs. He will correct it and get invariant mass distribution for a sub-sample of events runnumber[]=12126101-12138024

Still see the same background behavior
------------------------------------------------------------------------------------------------
Jan 13, 2021

Next, we will choose a single file and then we will run over a single event (a particular event id).
Then check number of pions and kaons tracks, kstar candidates and so on ...

File:

root://xrdstar.rcf.bnl.gov:1095//home/starlib/home/starreco/reco/AuAu200_production_2011/ReversedFullField/P11id.SL19c/2011/126/12126101/st_physics_adc_12126101_raw_4510003.picoDst.root

Event ID: 622596

number of trakcs: 3018

From Subhash:

event id 622596

# of total tracks = 3018

# of quality = 658
# of pi+ = 262

# of pi- = 284

# of k+ = 73

# of k- = 62

n pair-loop

# of K+ = 73

# of pi- = 284

# of K- = 62

# of pi+ = 262

in rot-pair loop

# of K+ = 73

# of pi- = 284

# of K- = 62

# of pi+ = 262

# of kstar-pair = 20732

# of Akstar-pair = 16244

# of rotated kstar-pair = 20732

# of rotated Akstar-pair = 16244

Entries in cos(theta*) from 0 to 1
# no. of kstar-pairs (K+, pi-) bin theta = 4048, 3916, 3924, 4405, 4439 = 20732

# no. of Akstar-pairs (K-, pi+) bin theta = 2943, 2958, 3234, 3470, 3639 = 16244

# no. of rot kstar-pairs (K+, pi-) bin theta = 3954, 3907, 3901, 4390, 4580 = 20732

# no. of rot Akstar-pairs (K-, pi+) bin theta = 2908, 2984, 3125, 3467, 3760 = 16244

Chensheng made PID cut same as Subhash

From Chensheng:

event id 622596

# of total tracks = 3018

# of quality = 657

K+: 73

K-: 61

pi+: 262

pi-: 282

(K+, pi-): 20586=73*282

(K-, pi+): 15982=61*262

rotated (K+, pi-): 20586=73*282

rotated (K-, pi+): 15982=61*262

Entries in cos(theta*) from 0 to 1

(K+, pi-): 3966+3885+3885+4358+4492=20586

(K-, pi+): 2850+2888+3155+3397+3692=15982

rotated (K+, pi-): 3914+3842+3873+4360+4597=20586

rotated (K-, pi+): 2837+2906+3061+3429+3749=15982

In code, the event plane calculation part among us is different (independent EP calibration).

Comparison of our entries in cos (theta*) bins from Same and Rotation events:

Same Event pair:

image_2021_01_13T05_48_45_999Z.png

Rotated pair:
image_2021_01_13T05_49_17_874Z.png
------------------------------------------------------------------------------------------------

Distributions look reasonable.
Next Chensheng will get invariant mass and rho00 distributions from a larger data set.
------------------------------------------------------------------------------------------------
Jan 14, 2021

Chensheng ran a small sample of data, runnumber[]12126101-12138024

Kstar invariant mass distributions looks similar in cos (theta) bins
To calculate K* raw yield we follow:

choose 20-60% centrality.

Invariant mass fit range: 0.77, 1.06

residual background function: second order polynomial

fixed width of K* to PDG value = 0.048

during fitting, the mass parameter in cos (theta) bins same as from the cos (theta) integrated one.

for raw ield, I've integrated the residual background subtracted histogram within the range: mass +/- 2*0.048;

Chensheng calculated raw Rho00 from a small sample of data .
K* Rho00 seems > 1/3
rho00_Chensheng_small_sample.pdf

Next, he will run over full dataset of run-11
------------------------------------------------------------------------------------------------
Jan18, 2021

We will be using exactly same event plane for this cross-check.
Subhash's TPC event plane class is at:
/gpfs01/star/pwg/subhash/Public/Kstar_Comparison/Subhash_ep/StRoot/StTPCEventPlane

Subhash modified his track cut variables (DCA calculations) to be exact same as Chensheng.
We have exact same number of entries.

Subhash:

psi2 from class: 0.955075

# of total tracks = 3018

# of quality = 657

# of pi+ = 262

# of pi- = 282

# of k+ = 73

# of k- = 61

# of kstar-pair = 20586

# of Akstar-pair = 15982

# of rotated kstar-pair = 20586

# of rotated Akstar-pair = 15982

# no. of kstar-pairs (K+, pi-) bin theta = 4001, 3883, 3897, 4390, 4415,

# no. of Akstar-pairs (K-, pi+) bin theta = 2884, 2930, 3196, 3381, 3591,

# no. of rot kstar-pairs (K+, pi-) bin theta = 3901, 3888, 3904, 4317, 4576,

# no. of rot Akstar-pairs (K-, pi+) bin theta = 2859, 2970, 3059, 3412, 3682

Chensheng:
psi2: 0.955075

tracks: 3018

tracks pass quality cuts: 657

K+: 73

K-: 61

pi+: 262

pi-: 282

(K+, pi-): 20586

(K-, pi+): 15982

rotated (K+, pi-): 20586

rotated (K-, pi+): 15982

(K+, pi-): 4001+3883+3897+4390+4415

(K-, pi+): 2884+2930+3196+3381+3591

rotated (K+, pi-): 3901+3888+3904+4317+4576

rotated (K-, pi+): 2859+2970+3059+3412+3682

Update_Compare_small_sample.png
----------------------------------------------------------------

----------------------------------------------------------------
Jan 21, 2121

We compare raw rho00 by using same event plane information from a large sample of events:
Raw_rho00_comparison_cz_ss.pdf

Results compares well.
----------------------------------------------------------------
Jan 27:

We compare raw rho00 from independent event plane information. We found differences in the results when using different event plane:
Kstar_Rhho00_SS_CZ.pdf

Next, we will check the event plane part among us.

For event plane calibration:

Subhash: did re-centering run by run and centrality wise. While for shift correction it is integrated over all the runs.
[Subhash will implement run-by-run shift correction]

Chensheng: Make groups for every 10 runs. The recenter and shift are done group-by-group and cent-by-cent.

Testing event plane on a single file:
We both got 652 tracks for event plane reconstruction.

With our current code:

Subhash:

event id 622596

# of tracks for raw EP: 652

pt*cos (2*phi) cos term sum: -4.27473

pt*sin (2*phi) sin term sum: 29.8227

psi raw value: 0.862132

# no. of kstar-pairs (K+, pi-) bin theta = 4043, 3908, 3890, 4339, 4406,

# no. of Akstar-pairs (K-, pi+) bin theta = 2898, 2918, 3144, 3404, 3618,

# no. of rot kstar-pairs (K+, pi-) bin theta = 3939, 3890, 3928, 4302, 4527,

# no. of rot Akstar-pairs (K-, pi+) bin theta = 2861, 2928, 3086, 3399, 3708

Chensheng:

# of tracks for raw EP: 652

pt*cos (2*phi) cos term sum: -4.27506

pt*sin (2*phi) sin term sum: 29.822506

----------------------------------------------------------------

Groups:

STAR Protected

subhash's blog
Login or register to post comments

The STAR experiment

subhash's blog

STAR Protected

User login

Navigation

Group notifications

K* Rho00 results comparison 200 GeV Run-11