STAR Protected

scp jump through gateways

Dmitry A.

Update 08.24.2018 -- Run 9 pp: analysis flow

Just for reference, below is an overview of the neutral-triggered jet analysis flow.

  1. Tag pp events with either pi0 or gamma-rich triggers.

Update 08.24.2018 -- Run 9 pp: measured vs. unfolded data, pi0 and gamma-rich triggers (R = 0.2)

To get an idea of how big the corrections are due to the unfolding procedure and if any odd features appear in the unfolding procedure, I've plotted the raw data and unfolded distributions on top of e

Baldin ISHEPP XXIV

Improving Pion pT and M Cuts for Run 15

Update 08.22.2018 -- Run 9 pp: unfolding with a different response, pi0 and gamma triggers (R = 0.2)

Following up from earlier today:

Update 08.22.2018 -- Run 9 pp: purity, zT systematic

Previously, I tried averaging the purity between 2 adjacent bins of zTtrk:

Update 08.22.2018 -- Run 9 pp: unfolding, pi0 and gamma triggers (R = 0.2, eTtrg = 9 - 20)

After examining how the Run 9 gamma-rich purity varies with zTtrk, I attempted to unfold both pi0 and gamma-rich triggers in all 3 bins of eTtrg for R = 0.2.  The response matrix I used to unfold

Update 08.20.2018 -- Run 9 pp: purity, testing zTtrk cuts

Earlier today, I looked at the zTtrk dependence of the Run9 purity:

Update 08.20.2018 -- Run 9 pp: a few checks on the gamma-rich purity

Following up on the previous study of the Run9 gamma-rich purity:

Updated spectra with new version of fastsim

 Dpm spectra for centralities 0-10, 10-40, 40-80 and 0-80 with new binning (to match Guannan's D0) and new version of fast simulator. There is still a difference in pT dependence...

Hot Spot Masking in Run 15 pp transverse

attachments: presentation for FMS meeting and list of hot spots for each runset

Update 08.15.2018 -- Run 9 pp: purity as a function of zTtrk (in bins of eTtrg)

Previously, I reported on the Run9 gamma-rich purity as a function of both zTtrk and eTtrg:

Presentation at LBNL meeting 8/13/18

 

Presentation at LBNL meeting 8/13/18

 

Update 08.14.2018 - Run 9 embedding: varying tracking efficiency, jet matching efficiency (TEST)

Following up on yesterday's test of adjusting the tracking efficiency:

Quick BEMC check with Dev PicoDst

Update 08.13.2018 -- Run 9 embedding: Updated Jet Matching Efficiency and Jet Energy Resolution (R = 0.2, 0.3, 0.4, and 0.5)

The last time I calculated the JER for R = 0.4, I noticed the matching efficiency was abnormally low.  In the post below, I checked if it was due to my matching algorithm.  It wasn't.

Update 08.13.2018 -- Run 9 embedding: varying tracking efficiency (TEST)

As part of the systematics for the analysis, we would like to vary the tracking efficiency by 5% or so.  Since I'm working with the Run 9 dijet embedding, the tracking efficiency is set by the Ge

Update 08.10.2018 -- Run 9 embedding: Jet Matching Efficiency (R = 0.2, 0.3, 0.4, and 0.5)

Previously, I took a look at the JER for a variety of R's: