The stntuple TALK_TO variables: 1/ jet_filter : bit-packed word: bit 0 set: remove jets with |eta| > 2 from R=0.4 jet list 1 remove jets associated with isolated tight electrons 2 " " " " loose CEM in dilepton analysis 3 " " " " loose PEM in dilepton analysis 4 " " tightly isolated tight photons (status>5000) 5 " " tightly isolated loose photons (status>4000) 6 " " loosely isolated loose photons (status>3000) BY DEFAULT, JET_FILTER IS SET TO 0. 2/ big_cone = 3 J1 jets have radius 1.0 1 0.7 (default) 3/ jtc_version = 0 JTC90S is used for jet correction factors 1 JTC96S (default) 4/ no_jt, no_j1, no_met, no_el, no_mu, no_tau, no_dil, no_pho, no_tag, no_vtx, no_genp, no_trk: logicals intended to exclude parts of the stntuple so as to reduce its size when some variables are unnecessary. For instance, the talk_to line NO_PHO eliminates the photon variables from the stntuple. 5/ TRIGGER uic command. Example for use of uic commands: trigger CEM_50 ! -> turns on bit 0 of stntuple variable TRIGBITS ! if CEM_50 is on trigger CEM_50* ! -> turns on bit 1 if CEM_50 anything is on trigger CEM_16_MET_20 ! -> turns on bit 2 if CEM_16_MET_20 is on (etc) 6/ vertexing : determines the method used to obtain the "event z-vertex," i.e., the z-vertex coordinate used to construct the JETS and METS banks, as well as photon 4-vector calculation. 0 production method (use 1st VTVZ bank) 1 sumpt method (choose class 12 VTVZ bank with the highest scalar sum of transverse momenta of 3d tracks pointing within 5 cm of the vertex. if no class 12 VTVZ bank exists, choose the class 11 VTVZ bank with the highest scalar sum of transverse momenta of 3d tracks pointing within 5 cm of the vertex. if no class 11 nor class 12 VTVZ bank exists, event z vertex = 0.0). 2 leptocentric method (method used by STNTUPLE$UIC. If a good electron or muon is found, then the event z vertex is chosen to be the same as that of the (highest Et) electron or muon. If no such lepton exists, we revert to the sumpt method.) 3 VXPRIM method (the event z-vertex is chosen to be that returned by the VXPRIM module. Appropriate for b-tag based analyses.) 7/ GENP bank information (description by Ray Culbertson) The standard ntuple now has the capability to store GENP information in the DEVELOPMENT version. The particles that will be saved in the GENP ntuple block are indicated by the talk-to; an example is below. The first selection criteria is the particle ID - this always has to be specified. The second criteria is the particle's parent's ID - 0 means no requirement. The particles may also be selected by the minimum Pt and maximum eta. ID's refer to the GENP code which can be found as the "P-CDF" and "A-CDF" columns in PYTHIA$LIBRARY:CVTABLE.DBT (e-=203, e+=204 etc). Or ISAJET$LIBRARY:CVTABLE.DBT (last two columnms). One might think that GENP codes are universal but they actually have a slight generator dependence. The code will assume that PYTHIA is being used unless you tell it to use the ISAJET table in the talk-to. The differences we know about are in the Higgs sector. You now need to SETUP ISAJET or PYTHIA in the job com file, but only if you intend to use this feature by requesting particles in the talk-to. If a particle ID is specified, the antiparticle is treated in the same way. For example if you request a b from a C1+, you will also get any b from C1-, bbar from C1+, and bbar from C1-. You can sort it out with the information saved in the block. Example talk-to ! Save all techniomega's (6009) ! Save all technipi's (6002) ! Save all b's (and bbar's automatically) that come from technipions (6002) ! Save all gamma's that come from techniomegas (6009) ! Save all gamma's that have GENP Et>15 and eta<2 talk stntuple ! genp menu genp ! chose generator: pythia (default) or isajet mcgen pythia ! ID parent ID Et> |eta|< particle 6009 0 0.0 999.0 particle 6002 0 0.0 999.0 particle 310 6002 0.0 999.0 particle 101 6009 0.0 999.0 particle 101 0 15.0 2.0 exit exit Example results: The N's are the GENP index. I have removed duplicate entries in the list if they have the same ID and same P as an earlier entry. These occur when GENP records showering results and, I think, other effects. NGENP=6 ID N N PARENT ID PARENT PX PY PZ MASS NGID(I) NGN(I) NGNP(I) NGPID(I) (GNP4(J,I),J=1,4) 6009 7 0 0 -0.92711 1.95948-313.21970 209.95438 101 8 7 6009 -5.14876 64.70074-187.78862 0.00000 6002 9 7 6009 4.22165 -62.74126-125.43107 110.17023 310 10 9 6002 53.27228 -32.23621 -92.79580 5.00000 311 11 9 6002 -49.05062 -30.50505 -32.63527 5.00000 101 197 162 508 18.89203 -11.84755 -32.16876 0.00000 Here's the result of running on a SUSY ISAJET file looking for all SUSY particles. You can see the 4601 (gluino) and 4614 (squark) have two entries with themselves as parents. This is probably due to showering records. However the 4801 (N1) also has two entries and they shouldn't be showering. You can see also that the charm quarks (308,309) had only one entry so there aren't alot of quark showering entries. ID N N PARENT ID PARENT PX PY PZ MASS NGID(I) NGN(I) NGNP(I) NGPID(I) (GNP4(J,I),J=1,4) 4601 21 0 0 -107.48696 -10.02831 107.72220 100.00000 4614 22 0 0 80.36237 103.59958 398.65247 200.00000 4601 87 21 4601 -109.59992 -10.84123 107.91925 100.00000 4614 88 22 4614 75.22867 101.61950 398.43945 200.00000 4801 192 87 4601 -86.22926 -29.27555 89.45397 14.11905 308 193 87 4601 -23.24701 -8.61134 11.53314 1.60000 309 194 87 4601 -0.12390 27.04564 6.93238 1.60000 4801 195 192 4801 -87.15360 -29.60426 90.17530 14.11905 4601 209 88 4614 55.14354 -2.05090 122.28098 100.00000 4601 212 209 4601 51.36697 -2.18380 122.93558 100.00000 4801 305 212 4601 7.91604 24.61632 27.04169 14.11905 4801 308 305 4801 8.57335 24.77186 27.35831 14.11905