1 / 7

Investigating 9 GeV Au+Au Collisions in March 2008

Analyzing 9 GeV Au+Au collisions from ~200k events, focusing on vertices, beam-pipe events, and physics insights. Run details: http://nuclear.ucdavis.edu/~ddas/9GeV_runs.html. Contact: rjreed@ucdavis.edu.

garrisonj
Download Presentation

Investigating 9 GeV Au+Au Collisions in March 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 9 GeV Au+Au Collisions • Run on March 11th, 2008 • Out of ~200k Events • 11000 had Vertices • 6700 had Vertices within 2 cm of the beamline • 4150 appeared to be beam-pipe events • Run details can be found at: http://nuclear.ucdavis.edu/~ddas/9GeV_runs.html • Combinations of bbc,vpd,ctb triggers used Rosi Reed rjreed@ucdavis.edu

  2. 9 GeV Au+Au Collisions

  3. 9 GeV Au+Au Collisions Be beam pipe extends from -75 cm to 75 cm

  4. Beam-Pipe Collisions and Low Energy Considerations • Why did we trigger on “empty” events? • Why did we trigger on beam-pipe events • Are the events labeled as beam-pipe events actually collisions between Au and the beam pipe? • We looked at the physics in these events to determine whether this was the case

  5. Au-Al HBT Analysis (root SNN = 3.2) • Event quality cuts: • |Vz| > 75 cm • Vr > 2 cm • Vz*TotalEventPz < 0 • Track Quality cuts: • Assumed all negatively charged tracks were pions • nHits/nPossHits > 0.5 for either TPC or FTPC

  6. Au-Al HBT Analysis – dE/dx

  7. Au-Al HBT Analysis Fit does not use lowest 3 points due to track merging

More Related