Versions Compared

Key

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

August 27, 2009

Agenda

  1. Evaluation of SL09b production
    • Matt - electrons in BTOW
    • Gene - TPC accuracy
    • Rosi - vertex finder
    • Jan - misc plots
  2. W analysis: who is working on it? What is your strategy? Do you need help?
    • Ross
    • Jan : wants to use default jet finder (for isolation and away side veto cuts) and has 0 experience.
    • anyone else ?
    1. jet finder tasks
      • decide on jet finding params, detectors: TPC, BTOW, ETOW
      • decide on data massage: TPC track PT saturated at 10 GeV/c, identify/reject hot unmasked towers, temporary BTOW abs calibration
      • run jet finder over 600 runs, QA performance, uniformity per run, per fill
        #TPC calibration, Gene: Could you describe realistic timeline for complete TPC calibration: PadrowT0, Twist, ShortedRing
        Next production should include all of the above
  3. ETOW - Scott/Justin
    • uploading 2009 gains to DB
    • do we see pi0 peak with those gains (smile) ?
  4. ESMD - Willie
  5. Vernier scan - Ross, all 6 pp500 runs have been produced.
    • understanding background
    • Is BHT3 x-section consistent ?
  6. AOB
  7. Anouncements
    #*Jan: the following runs will be tagged as Xx because there is 0 or <100 events with found vertex :
    R10084013
    R10088103
    R10081024
    R10095032
    R10085022
    R10088060
    R10085103
    R10087007
    R10093049
    R10085118

    August 20, 2009

    Present: Rosi,Hal,Jan,Justin,Gene,Ross
  8. Production status
    • pilot production has been QAed . No major problems were found and Lidia is most likely executing production now.
    • expect St-W muDst to be ready in few days.
    • identified problems to be fixed before next production
      • explain why PPV sees no tracks crossing TPC CM
      • why 7-bit bXing has no abort gap for the fill on page 19 top plot ?
  9. ETOW absolute calibration to compensate for incorrect TCD phase used during data taking. Two alternative methods are used:
    • Justin is comparing ratio of slopes for correct & incorrect TCD phase from regular minB events from pp200 data: http://drupal.star.bnl.gov/STAR/blog/stevens4/2009/aug/05/run-9-eemc-tcd-phase-and-effective-gains
      Fig 1.1 show example for 1 tower
      Link http://drupal.star.bnl.gov/STAR/system/files/ETOW_SlopeSet0vSet1234.pdf
      shows slopes (top) and the deduced gain correction (bottom) for all towers and all crates.
    • Scott is analyzing slopes from calibration pp500 data taken and various TCD phases and predicts similar gain correction for the TCD phase value used during W-data taking. The comparison is here
      PDF
      namescott-08-20-2009-all_ETOW-crates.pdf
      In particular pages 4-6 show error bars. Both methods lead to the same gain correction.
    • The plan is to compute weighted average gain correction and upload it to DB with a different flavor. So user will get non-sense gains for the default 'ofl' and needs to request those. (Very good plan, Jan)
  10. Status of Vernier scan was presented by Ross: http://drupal.star.bnl.gov/STAR/blog/rcorliss/2009/aug/20/absolute-cross-section-notes-5
    The rate of STAR events vs. time (fig 1) is described by the product of 2D gauss functions representing X,Y spread of ions in both (identical?) beams. We know from Angelika the relative displacement of both beams for every time period of Vernier scan. Ross fits 2 params: sigX, sigY - the width of gauss.
    Fig 3 ('counts vs. steps') shows anticipated result. The value of 'skfNN' is absolute cross section of STAR BHT3 trigger in units TBD and assuming no hot tower correction is needed.
    Ross add constant background to better describe the observed rate , yet still peaks are under-predicted.
    He will continue to try to model vernier scan better and is awaiting for muDst from 6 Vernier scan runs from ongoing production to be able to assess how stable is the value of skfNN.
  11. run QA : Hal will do QA of the first week of pp500 data within next 30 days, backward in time. (Thanks^2, Hal)

...