Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. result of analysis of SL09b production
    1. Jan (Drupal blog )
      1. presentation of W-algo ver 4.0 using BTOW & TPC, for 1M input events
      2. Run 9 results as of September 1 Slides
        1. histogram-based dump of selected events
        2. Larger collections of events: di-jets , W-candidates , Z-candidates
        3. Matt's 3 interactive events in skechup or just one view , at Scott's angle
        4. sequential histograms from pass through 1M events (LT=~8/pb)
      3. M-C simulation analysis histograms for Pythia W-events (LT=320/pb) , filtered QCD-events LT=6.3/pb, Z-events LT=4200/pb
      4. Suggestions: count # of track pointing to cluster; compare ET vs. PT for electron
    2. Joe adopted his algo developed on M-C to work with Run 9 data
    3. * removed BSMD, changed to tower-based center of gravity, relaxed cuts: PT>5 GeV/c, delEta & delPhi<0.5, isoFraction of 0.8
      1. Uber-preliminary result for 1M input events showing W peak and a hint of a Z peak plots
  2. Run 9 data publication strategy has been discussed and in general agreed up. Use of BSMD for PRL paper 1 was discussed - it is worth trying. Effici
  3. Questions/comments
    1. from former prominent STAR collaborator:
      • Could the Z-candidates be di-jets? cosmic rays? Do you try to do any charge sign discrimination on the electrons (i.e., opposite sign on the 2 sides for "Z-candidates")? Phi distribution does not appear indicative of cosmics.
      • Most importantly, is "Jacobian peak" absent when you look at 200 GeV data with the same algo and cuts?
      • Lots of questions, but this does look really promising, seems to give you NN W candidates NN Z candidates in the barrel region. It's a bit surprising that such a crude isolation cut, with no away-side ET upper threshold or SMD criterion, would suppress jet background so effectively. We always thought we would have to work much harder than this to unveil a signal above background.
    2. Jan: Mike B. just confirmed we could Lets plan to use BFC filter to get rid of not-BHT3 events from pp200 data. This makes another mini-production request of pp200 data a viable option (there is a small issue thou).. Process LT~10/pb. Needs: adopted filtering code, run selection, 1mm accuracy of TPC calibration (within month), supported production request
    3. Joe: estimate TPC tracking efficiency difference for e+ vs. e-
  4. Ross - vernier scan analysis
    1. lots of detail about how I do the fit - Ross is looking for explanation why his calculations are off by ~4 orders of magnitude. knows
    2. Comparison of Vernier scan from 2 pp500 runs - background visible in both
    3. Comments/suggestions:
      • post study with eliminated TP affected the most by the beam background
      • post input data from Angelika
      • exercise the code on mock data to verify it reconstructs width correctly
  5. Joe - BTOW relative gains, not yet
  6. new phone meeting time moved to : Tuesday 5-6 pm EDT
  7. low TPC tracking efficiency at eta~0. How can we address this issue?
    Below is suggestion from Jerome. In short he offers a welcome at BNL.
    • The convoluted hit issue brought during Jan's presentation: Yuri will show Jan how to access/recognize those. It was generally understood that using those in tracking would require
      • a study of effect in real data
      • a response simulator simulating those convoluted hits so embedding would be properly handled (right, it is not handled in embedding not tracking so goes into a reco inefficiency).
      • We welcome Jan coming at BNL and working with Yuri on characterizing the effect on tracking. A month work would bring a pretty good study (still the embedding is questionably achievable within the workload and timeframe)
    AOBGene: may by better T0 suffice to correct it - lets wait for the outcome. How can we address this issue?

August 27, 2009

Present: Willie, Matt, Jan, Hal, Rosi, Justin
Minutes

...