UML aggregation

Under:
UML aggregation

UML association

Under:
UML association

UML generalization

Under:
UML generalization

UML class representation

Under:
UML class representation

Class Diagram using Umbrello

Under:
Class Diagram using Umbrello

UML Class Diagram

Under:

This tutorial was imported from KDE's Umbrello tutorial giving a nice overview of the UML elements.

Tips

What follows are miscellaneous tips and suggestions that will be irregularly maintained.

Direct connection, internal network

You can use direct connections to access them over the network.

  • Direct:  These printers accept direct TCP/IP connections, without any intermediate server. 

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.

PuTTY screen dump example

Under:
PuTTY screen dump example

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.

Fit to pi-Xi CF

Speaker : Petr Chaloupka


Talk time : 00:00, Duration : 00:30

http://www.star.bnl.gov/protected/hbt/petrchal/Fit3/main.html

Run 7 calibration meeting #1

2007-06-29 10:00
2007-06-29 11:00
Etc/GMT-5
Friday, 29 June 2007
1-189, [(631) 344] 8261, at 14:00 (GMT), duration : 01:00

The 2006 STAR analysis scenario

Under:

This page will describe in detail the STAR analysis scenario as it was in ~2006.  This scenario involves SUMS grid job submission at RCF through condor-g to PDSF using SRM's at both ends to trans

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.

MC production for the di-jet cross section measurements in pp collisions at 200 GeV

Under:

Introduction

How to run the patched PYTHIA 6 in starsim

The most of the MC production jobs that the spin PWG requested for the di-jet analysis didn't finish successfully
Patch for a bug in PYTHIA6
This page explains how to run the patched PYHIA 6 as the event generator for starsim. The starsim has a mechanism where a user can choose a specific version of Pythia to use at run time.This feature will be used.

Pions in Jets study

Jet Pion Study

Procedure

Patch for a bug in PYTHIA6

This patch is included in PYTHIA from PYTHIA 6.412. You don't need to apply this patch if you are using PYTHIA 6.412 or newer.

Download Patch

pythia-6.4.11-t.diff : patch for PYTHIA-6.4.11
pythia-6205-6205t.diff : patch for PYTHIA-6.205

If you need the patch for a different version of PYTHIA, email sakuma@bnl.gov.

Lambda/K0S ratio - Year 2 and Year 4 Au+Au @ 200 GeV

Under:
Lambda/K0S ratio - Year 2 and Year 4 Au+Au @ 200 GeV

Lambda/K0S ratio: The Lambda/K0S ratio in Year 2 and Year 4 Au+Au @ 200 GeV. The data to the left of the vertical line comes from Year 2, the data to the right from Year 4.