README 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113
  1. Maker: StFlowMaker
  2. Files: StFlowMaker.cxx
  3. StFlowMaker.h
  4. StFlowEvent.cxx
  5. StFlowEvent.h
  6. StFlowTrackCollection.cxx
  7. StFlowTrackCollection.h
  8. StFlowTrack.cxx
  9. StFlowTrack.h
  10. StFlowCutEvent.cxx
  11. StFlowCutEvent.h
  12. StFlowCutTrack.cxx
  13. StFlowCutTrack.h
  14. StFlowPicoEvent.h
  15. StFlowPicoEvent.cxx
  16. StFlowSelection.h
  17. StFlowSelection.cxx
  18. StFlowConstants.h
  19. StFlowConstants.cxx
  20. Authors Raimond Snellings, Art Poskanzer, and Sergei Voloshin
  21. with lots of help from Glenn Cooper
  22. Date: Dec 1999
  23. Description:
  24. ** StFlowMaker:
  25. StFlowMaker creates StFlowEvent from StEvent or from StFlowPicoEvent
  26. after event and track cuts. StFlowEvent contains a track collection
  27. (StFlowTrackCollection) which contains tracks (StFlowTrack).
  28. In Init, StFlowMaker reads the PhiWgt values for the TPCs and FTPCs from
  29. flowPhiWgt.hist.root . These are used for making the event plane
  30. isotropic in the lab.
  31. In Make, it stores in StFlowEvent the PhiWgt values, the RunID, the
  32. EventID, the CTB signal, the ZDC east and west signals, the beam
  33. energy, the beam mass for East and West, the trigger word, the
  34. original track multiplicities for negative and positive particles, the
  35. multiplicity within |eta| < 0.75, the centrality bin, and the primary
  36. vertex position. In each StFlowTrack it stores phi, global phi, eta,
  37. global eta, p_t, global p_t, charge, dE/dx, deviant pid for each
  38. particle, pid, dca, global dca, chi2, fit points, and max
  39. points. StFlowTrack can also calculate total p and rapidity.
  40. In Finish, it prints the lists of cuts and selections.
  41. ** StFlowEvent:
  42. StFlowEvent contains member functions which return PhiWeight, Mult,
  43. MeanPt, Q (the event plane vector), Psi (the event plane angle), and q
  44. (=Q/sqrt(Mult)). It contains the functions which make the random
  45. sub-events, the eta separated sub-events, and set the pid values. It
  46. also contains the function which sets the flags for each track saying
  47. whether it is used in the event plane determined for each harmonic,
  48. each selection, and each subevent. StFlowEvent is used in the flow
  49. analysis by StFlowTagMaker and StFlowAnalysisMaker.
  50. It now supports the StFlowCumulantMaker by calculating the generating
  51. functions for the old and new cumulant methods, and a Q vector
  52. normalized by the sum of the squares of the weights.
  53. ** Cut Classes:
  54. The StFlowCutEvent and StFlowCutTrack classes have all functions and
  55. data members static. Therefore, there is no need to instantiate. Just
  56. use StuCutEvent::func(); or StuCutTrack::func(); . The reason for
  57. making them static was to keep count of the number of events and
  58. tracks removed by each cut. Call the PrintCutList functions in Finish
  59. to print these counters.
  60. Right now the event cuts are on centrality, multiplicity and primary
  61. vertex position. The track cuts are on chi2, dca, pt, eta, fit points,
  62. and the ratio of fit point to max points. These can be applied to TPC
  63. tracks, FTPC tracks, or global tracks. It is set up so that other cuts
  64. can be easily added. If lo >= hi on a cut, the cut is not applied.
  65. In CheckEvent and CheckTrack the calling argument is a pointer to the
  66. event or track.
  67. CutTrack also stores the number of tracks with positive and negative
  68. pseudorapidity. In CheckEvent::CheckEtaSymmetry these counters are
  69. used to calculate (Pos - Neg) / (Pos + Neg). A cut is put on this
  70. ratio after correcting for an acceptance effect and normalizing with
  71. the square root of the multiplicity. The purpose is to eliminate
  72. beam-gas background where most of the particles would go one way or
  73. the other.
  74. Before run 4 trigger words were used to describe the triggers. After
  75. run 4 multiple triggers could be satisfied by one event and a trigger
  76. collection is used. The scheme for selecting triggers therefore changed
  77. with the user being forced to make a choice as to which triggers to look
  78. for.
  79. ** StFlowPicoEvent:
  80. This is a persistent sub-set of StFlowEvent which can be written out
  81. to disk.
  82. ** Selection Class:
  83. The StFlowSelection class is used to select events and tracks from
  84. StFlowEvent which have already passed the above cuts. If one calls the
  85. Select() member function with a pointer to StFlowTrack it selects
  86. tracks for the event plane determination which have the indicated
  87. harmonic, selection, subevent, and PID. The SelectPart() member
  88. function selects tracks for correlating with the event plane which
  89. have the indicated pid, pt, total p, rapidity, eta, fit points, ratio
  90. of fit points to max points, chi2, global dca, and dca.
  91. ** Constants:
  92. StFlowConstants contains constants which are used in more than one file.