- seelej's home page
- Posts
- 2011
- 2010
- December (2)
- November (3)
- October (3)
- September (3)
- June (2)
- May (3)
- April (2)
- February (9)
- January (1)
- 2009
- December (1)
- October (3)
- September (4)
- August (1)
- July (1)
- June (6)
- May (1)
- April (4)
- March (5)
- February (1)
- January (4)
- 2008
- My blog
- Post new blog entry
- All blogs
Embedding Request for run9 W xsec analysis
Embedding request needed for publication of W Cross Section from run 9
We are asking for embedding that mixes TPC, BTOW, and ETOW data. PPV vertex finder should be used. We would further like to mix all the layers of the BEMC and EEMC (BSMD, BPRS, ESMD, EPRS) provided that it can be done with limited investment of manpower.
Clarifications:
- 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. It should be noted that some ZB events will be used multiple times.
- Pythia sub-event should be converted to ADC using the particular set of gains determined by Matt & Joe (the 'ofl' flavor). 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. The pythia events will be generated by using the kumac (+ associated file) developed by Jason Webb for the initial simulations that were done for the W analyses.
- Steps described in item 1 & 2 apply for both BTOW & ETOW data. All tables to be used are in the DB with 'ofl' flavor.
- The outgoing event time stamp will be identical to the ZB event time stamp
- We would like that signal 0 be produced first and then we would like that 10% of the embedding be produced first as a pilot production to make sure there are no bugs before the remainder of the full embedding request is completed.
Inputs
- Signal 0 : 1k single electrons and 1k single positrons for testing purposes. The electrons and positrons should sample the ZB data in the following list. (list1 link)
- Signal 1 : 24K W+ Pythia events
- Signal 2 : 24k W- Pythia events
- Signal 3 : 24k W(+,-) ->Tau pythia events
- Signal 4 : 24k Z->any events
- Signal 5 : 24k Z->e+e- with interference term events
- Background : zerobias events (to be used for Pythia signal samples 1-5)
- Details of how weighting for each run's ZB events was determined here to sample the data taking conditions (ZDC-rate, detector acceptance, etc) similar to the data. This second list (list2 link) provides the runs with ZB events to be used and the amount of times the events from that run should be re-used.
- The total number of ZB events (including the re-used events) is Ntot=13647. All the signal samples should have a requested number of events of ~ K*Ntot, where K is an integer so that each signal will sample the same data taking conditions from the ZB events.
Mixings
- Signal 1-5 + Background
- using the table in the blog entry determined BeamLine constraint. This is part of the pythia and geant simulation and will be done in the geant part of the simulation after the simulation of the event in pythia.
- official new TpcRS (TPX slow simu)
Details for simulation
- Vertex : z-width = 42cm, x,y-width = 150um (z-width determined from data). The vertex should also be displaced as is shown in the data (in z by -1.9 cm... any lateral shift is done with the beamline offset)
- STAR library SL11b
- Geometry y2009a
- BFC options: DbV20110310 pp2009c ITTF VFPPVnoCTB BEmcChkStat beamLine Corr4 OSpaceZ2 OGridLeak3D -dstout -evout
- Magnetic Field = Reversed Full-Field
Groups:
- seelej's blog
- Login or register to post comments