Revised embedding request needed for publication of W xSection form run 9.

The request consist of 2 parts. Part A aims to estimate efficiency for finding Ws. Part B to estimate contamination to reco Ws due to pileup and beam background events.

We are interested in mixing TPC, BTOW, and ETWO data. PPV vertex finder should be used.

Clarification:

1. production of .fzd events is NOT part of this embedding requests. A separate M-C production request will be made for 'signal MC' events once it is technically feasible.
2. BFC options, vertex distributions, etc. will be specified once STAR library is closed (Nov 15). For testing of embedding code make reasonable choices, assume beam-line at zero.
3. ZB DATA sub-event: apply 'do not touch' policy for ZB ADCs.  Whatever  comes in is passed 1:1 to the output event. No status  tables, no  pedestal status correction. Always 4800 output values are passed. ADC of towers for which M-C event has a non-zero ADC value will be incremented by this amount. If ADC sum exceeds 4096 it will be pegged at 4096.
4. Pythia sub-event should be converted to ADC using the particular set of gains determined by Matt & Joe as a product of:
   • ideal gains(60 GeV ET = 4076 ADC)  and
   • tower by tower slope ratio (pp500 data) and
   • scaled vs. pseudo rapidity to achieve E/P=1 for electrons  in pp500

Currently those gains are saved in DB w/ the flavor 'Wbose2'. For towers w/o gains the ADC contribution form M-C will be set to zero. For towers with bad peds or status table M-C ADC will be computed and added to ZB sub-event as long as gain exits. 

5. Steps described in item 3 & 4 apply for both BTOW & ETOW data.
6. The outgoing event time stamp will be identical to the ZB event time stamp
7. Beam line constrain needed by PPV will be common for the whole W-embedding request and stored in DB with non-default flavor (TBD)

Part A)  estimate efficiency for finding Ws

 Inputs:

• signal 1: 1000 W-Pythia events produced ~10 months  ago in dev w/ old 2009 geometry: /star/institutions/uky/balewski/2009-Walgo-simu/setD1-Wprod/fzd/ppWprod_job10.fzd
• signal 2: 40K  W-Pythia events, to be produced (Jan) with the final 2009 M-C geometry and beam offset comparable to the pp500 real data
• background 1: zero bias events form high lumi fill, run=10102033, has 1400 ZB events
• background 2: minB eve from the low lumi fill 10421, run 10083133
• background 3: zero bias events. Goal of the procedure described below is  to   assure  the sampling of ZB events according to the luminosity & STAR up-time.
  • Runs which passed pp500 run QA (ver 4) were sorted by the zdc rate in to 10 categories (ADD LINK).
  • The integral of ZDC counts  from the runs in given ZDC-rate range will define the weight of given ZDC-rate category (ADD TABLE). 
  • From all available in HPSS ZB-daq files we pooled files at random from 10 categories of ZDC-rate using weights described above. Once one of 10 categories is empty pooling was stopped and ZB-daq file list was closed.  
  • For embedding pick at random ZB-daq files  from  this list (ADD  LIST) with uniform distribution.   

Mixing tasks:

A1 ) signal 1 + background 1

Both using :

• BeamLine constrain : matched the offset used in M-C x=y=0 
• current code in dev with added new TpcRS (TPX slow simu) from Yuri 'as is'.
  

A3 ) signal 2 + background 3,  using :

• BeamLine constrain : matched the non-zero offset used in M-C signal 2
• official  new TpcRS (TPX slow simu)  

Part B)  estimate contamination to reco Ws due to pileup and beam background events

Inputs:

• signal 3: 145K  filtered QCD Pythia events produced ~10 months  ago in dev w/ old 2009 geometry:  /star/institutions/uky/balewski/2009-Walgo-simu/setD2-filterQCD2/fzd, 485 files, 145,000 events
• signal 4: filtered QCD Pythia events, to be produced (RCF farm) with the final 2009 M-C geometry and beam offset comparable to the pp500 real data. Number of events TBD depending on results of previous steps.
• background 3: as defined previously

Mixing tasks:

B1 ) signal 3 + background 3,  using :

• BeamLine constrain : matched the offset used in M-C x=y=0 
• current code in dev with added new TpcRS (TPX slow simu) from Yuri 'as is'.
  

B2) signal 4 + background 3, using :

• BeamLine constrain : matched the non-zero offset used in M-C signal 4
• official  new TpcRS (TPX slow simu)