Sort by:[Date]

BTOW pedestal comparison -- emcOnline vs. L2ped

I wrote a script that compares each Run 7 BTOW pedestal table with a corresponding L2ped printout. The script queries the RunLog_onl database for the runnumber immediately preceding the table timestamp, then it looks for a log file corresponding to that runnumber in the L2ped directory on online.star.bnl.gov. If it can’t find the precise runnumber, it compares the online pedestals to the next closest L2ped runnumbers both before and after, and then prints the comparison for the better match.

Here’s a summary log printing the number of channels per table where

  1. the difference in pedestal value is greater than 4, or
  2. the difference in pedestal sigma is greater than 1.5

There are a handful of channels per run with drastic differences. For example, emcOnline will declare a zero pedestal, but l2ped will say there’s a peak at 3500 ADCs. Channels like these are obviously bad. Of greater concern are the runnumbers where several hundred channels do not match. Most of the time it’s because the widths are different, but occasionally there are runs where a few hundred towers will have pedestals that differ by more than 4 ADCs. The full verbose output (listing every tower that fails the cut) can be found here.

.

.

Kaon-pion correlations in d+Au: varying the momentum cut + historic summary

In
this update
a set of results with Adam's suggested momentum cut is added to the pool of analysis results for d+Au.

First Look at Electron Jets

I've been working with Priscilla on adding her electron candidates to the spin trees.  spinTrees with electrons are now available, and we went ahead and made these plots investigating the properties of jets with identified electrons.  We analyzed BJP1 and L2Gamma triggers and plotted the p_T spectra, track multiplicity, and neutral energy fraction for all jets and for jets associated with an electron candidate (deltaR < 0.7).  Full-size plots available by clicking on each image.

Electron Cuts

  • Global dE/dx cut changing with momentum
  • nFitPoints >= 15
  • nDedxPoints >= 10
  • nHits / nPoss >= 0.52
  • track Chi2 < 4
  • DCAGlobal < 2
  • NEtaStrips > 1 && NPhiStrips > 1
  • Primary dE/dx cut changing with momentum
  • 0.3 < P/E < 1.5
  • -0.01287 < PhiDist < 0.01345
  • ZDist in [-5.47,1.796] (West) or [-2.706,5.322] (East)

Jet Cuts

  • 0 < R_T < 0.99
  • -0.7 < detEta < 0.9
  • Jet points at fired jet patch (BJP1 only)

l2gamma_rt bjp1_rt l2gamma_track_mult bjp1_track_mult l2gamma_ptComp bjp1_ptComp

Conclusions

  • The neutral energy fraction for L2gamma electron jets peaks at the same point as the ridge in the inclusive jet plot.
  • There are a significant number of 1-track jets in the L2gamma sample
  • In the plot of jet p_T vs. electron p_T we see the maximum of the distribution occurring at a electron pT of ~5.5 GeV and a jet pT of ~11 GeV.  This is in stark contrast to the BJP1 distribution. 

Average Partonic Pt Carried by Charged Pions

Here's a fragmentation study looking at the ratio of reconstructed charged pion p_{T} and the event partonic p_{T} in PYTHIA.  Cuts are

  • fabs(mcVertexZ()) < 60
  • fabs(vertexZ()) < 60
  • geantId() == 8 or 9 (charged pions)
  • fabs(etaPr()) < 1
  • fabs(dcaGl()) < 1
  • fitPts() > 25

fragmentation_parton_reco

Error bars are just the errors on the mean partonic p_{T} in each reconstructed pion p_{T} bin.  Next step is to look at the jet simulations to come up with a plot that is more directly comparable to a real data measurement.

Effect of Triggers on Relative Subprocess Contributions

These histograms plot the fraction of reconstructed charged pions in each pion pT bin arising from gg, qg, and qq scattering.  I use the following cuts:

  • fabs(mcVertexZ()) < 60
  • fabs(vertexZ()) < 60
  • geantId() == 8 or 9 (charged pions)
  • fabs(etaPr()) < 1
  • fabs(dcaGl()) < 1
  • fitPts() > 25

I analyzed Pythia samples from the P05ih production in partonic pT bins 3_4 through 55_65 (excluded minbias and 2_3).  The samples were weighted according to partonic x-sections and numbers of events seen and then combined.  StEmcTriggerMaker provided simulations of the HT1 (96201), HT2 (96211), JP1 (96221), and JP2 (96233) triggers.  Here are the results.  The solid lines are MB and are identical in each plot, while the dashed lines are the yields from events passing a particular software trigger.  Each image is linked to a full-resolution copy:

HT1HT2
JP1JP2

Conclusions

  1. Imposing an EMC trigger suppresses gg events and enhances qq, particularly for transverse momenta < 6 GeV/c.  The effect on qg events changes with pT.  The explanation is that the ratio (pion pT / partonic pT) is lower for EMC triggered events than for minimum bias.
  2. High threshold triggers change the subprocess composition more than low-threshold triggers.
  3. JP1 is the least-biased trigger according to this metric.  There aren't many JP1 triggers in the real data, though, as it was typically prescaled by ~30 during the 2005 pp run.  Most of the stats in the real data are in JP2.

Checklist for Run 6 preliminary result

  1. QA for BJP0 trigger and runlist generation
  2. Confirm vertex and nSigma cuts with systematic studies
  3. Run over new PYTHIA simulation, make basic data/simu comparisons
  4. Trigger Bias studies
  5. Extract A_TT from transverse data
  6. Randomized spin pattern studies
  7. PID background estimation

Notes

  • Adding the L2gamma trigger would improve statistics but we don't have an officially sanctioned simulation of that trigger available yet.
  • This checklist assumes the preliminary result is an inclusive measurement using only Run 6 data; other possibilities are to combine Runs 5 and 6 or to pursue the jet+pion measurement.

gt test

some text

test->me

more text to go

Single-Spin Asymmetries

Here’s a quick summary of various single-spin asymmetry sanity checks (yellow, blue, like-sign, unlike-sign) calculated for both types of charged pions in the Run 6 data.

pi^{-}

Pi Minus elb Fill Pi Minus elb pt Pi Minus els Fill Pi Minus els pt Pi Minus eus Fill Pi Minus eus pt

pi^{+}

pi<em>plus</em>ely<em>fillpi</em>plus<em>ely</em>pt Pi Plus elb FillPi Plus elb pt Pi Plus els Fill Pi Plus els pt Pi Plus eus Fill Pi Plus eus pt Every measurement is absolutely consistent with zero, and I don't see a single problematic fill in this list.

Cuts Summary

Here's a list of the cuts applied to the data in the common spin trees.

Run 5

Event
  • standard spinDB requirements
  • production triggers only
ConeJets
  • 0.2 < detEta < 0.8
  • 0.1 < E_neu / E_tot < 0.9
chargedPions
  • pt > 2
  • -1 < eta < 1
  • nFitPoints > 25
  • |DCA_global| < 1
  • -1 < nSigmaPion < 2
bemcPions
  • pt > 3.0
  • photon energies > 0.1
  • asymmetry < 0.8
  • 0.08 < mass < 0.25
  • charged track veto
  • BBC timebin in {7,8,9}

Run 6

Event
  • standard spinDB requirements
  • production triggers + trigId 5 (L2gamma early runs)
ConeJets, ConeJetEMC -- no cuts applied

chargedPions
  • pt > 2
  • -1 < eta < 1
  • nFitPoints > 25
  • |DCA_global| < 1
  • -1 < nSigmaPion < 2
bemcPions
  • pt > 5.2
  • photon energies > 0.1
  • asymmetry < 0.8
  • 0.08 < mass < 0.25
  • charged track veto
  • BBC timebin in {7,8,9} update:  timebin 6 added in 2007-07-18 production
  • both SMD planes good
bemcElectrons added as of 2007-07-18 production
  • hardware or software trigger in (117001, 137213, 137221, 5, 137222, 137585, 137611, 137622)
  • Global dE/dx cut changing with momentum
  • nFitPoints >= 15
  • nDedxPoints >= 10
  • nHits / nPoss >= 0.52
  • track Chi2 < 4
  • DCAGlobal < 2
  • NEtaStrips > 1 && NPhiStrips > 1
  • Primary dE/dx cut changing with momentum
  • 0.3 < P/E < 1.5
  • -0.01287 < PhiDist < 0.01345
  • ZDist in [-5.47,1.796] (West) or [-2.706,5.322] (East)