Full set cuts applied to W-algo ver 4.1

(this list is consistent with common set of cuts)

  1. Run selection: setABCD.runList, available # of events: input=1.55e6, L2wET=1.17e6
    • RHIC fill range: F10383 - F10536
    • STAR run range: R10076134 - R10103046
      • skip runs w/ badly functioning TPC (~no vertices found) : R10084013, R10088103, R10081024, R10095032, R10085022, R10088060, R10085103, R10087007, R10093049, R10085118
  2. run analysis on muDst's
    1. access TRG,TPC,BTOW,BSMD directly from muDst containers
    2. apply calibrations from DB 'by hand' in analysis code
  3. Trigger bits requirement
    1. BHT3 trig ID: 23054[01] or small IDs for some runs
    2. L2W trig ID: 23060[01] or small IDs
    3. L2-bit1 (on line value was ET>13 GeV)
    4. count L2-bit0 (random accept of BHT3) for absolute 'seen' cross section
  4. Reco prim vertex requirements
    1. rank>0
    2. | z-vertex | <100 cm
  5. Reco TPC track requirements
    1. prim tracks belong to selected prim vertex
    2. (flag=301 for primary) or (flag=101 for global) component
    3. if primary is valid but its global pointer is NULL skip the primary track, but keep the rest of the event
    4. nFit/nPoss>0.51
    5. glob PT>1 GeV/c
      1. if track PT>10 GeV/c assume it is 10 GeV/c
    6. for high energy electron candidate require additional
      1. nFitPoints>=15
      2. 1st hit Rin<90 cm
      3. last hit Rout>170 cm
    7. do not use TPC dEdX information for SL09b events
  6. BTOW: use ideal gains, actual status tables & pedestals , 'ofl' flavor for all, no time stamp set in the user code
    1. assume tower is dead if status!=1
    2. assume tower ADC=0 if (rawADC-ped)< [3*sigPed or 8 counts]
    3. drop event if max tower ADC <200
    4. 2x2 cluster ET > 15 GeV, cluster must contain tower pointed by the track
    5. 2x2/4x4 ET >0.95
    6. 2x2/near-cone ET(BTOW+TPC) >0.90, near-cone has delR=0.7 around track
    7. away-cone ET(BTOW+TPC) <8 GeV , away-cone has only delPhi=0.7 around (-track), no eta cut,
  • No labels