]>
Commit | Line | Data |
---|---|---|
db1bbbe1 | 1 | Questions to ruben.shahoyan@cern.ch |
2 | ||
3 | ------------------------------------------------------------ | |
4 | PbPb dN/dEta analysis can be done in 2 ways: | |
a9a39f46 | 5 | |
6 | 1) For single centrality bin: | |
7 | Using AliTrackletTaskUni.{h,cxx} steered by the | |
8 | runAAF.C and MyAnalysisMacro.C | |
9 | ||
10 | It will produce a file with 3D (sparse) histos "delta" vs Zv vs eta | |
11 | where delta is either "weigted distance" and/or "dphi - bend", which is used | |
12 | both the match the tails and to define the signal cut. | |
13 | The exact value of cut can be decided at the stage of processing the histos, | |
14 | so different signal and tail matching thresholds can be tested | |
15 | ||
16 | Note that wide Zv eta range can be processed and then restricted at | |
17 | the correction stage. | |
18 | ||
19 | One has to run runAAF.C for over the data and MC datasets and then analyse them | |
20 | using the CorrectSpectra.C macro (the cuts/variables use... must be set | |
21 | beforehand) | |
22 | ||
23 | ||
db1bbbe1 | 24 | 2) For multiple centrality bins at once: |
a9a39f46 | 25 | AliTrackletTaskMulti.{h,cxx} steered by the |
26 | runAAFMulti.C and MyAnalysisMacroTrackletMulti.C | |
27 | ||
db1bbbe1 | 28 | One should set the in the AliTrackletTaskMulti the |
29 | const Float_t AliTrackletTaskMulti::fgkCentPerc[] ... aray with definition of selected | |
30 | centrality bins, i.e. {0.,5.,10.,100} will creat bin0 for 0-5% centrality, bin1 for 5-10% etc. | |
31 | ||
32 | The variable on which centrality is defined is selected via runAAFMulti useCentVar parameter, | |
33 | should correspond to one of AliTrackletMultTask | |
34 | enum {kCentV0M,kCentFMD,kCentTRK,kCentTKL,kCentCL0,kCentCL1,kCentV0MvsFMD,kCentTKLvsV0,kCentZEMvsZDC,kNCentTypes}; | |
35 | ||
36 | The produces for each centrality bin a set of histos, particularly 2D histos for | |
a9a39f46 | 37 | Zv vs eta with the signal cut on "distance" already applied (by defaults one for |
38 | "w.dist" another for "dphi-bend" + 1D histo of "distance" for selected Zv,eta | |
39 | range (to be used for the bg matching the tails of data" | |
40 | ||
41 | Note: Zv, eta ranges must be defined at data processing stage, as well as the | |
42 | signal cut (cutSigNStd in the runAAFMulti) and number of st.dev to keep (nStdDev) | |
43 | ||
44 | One has to runAAFMulti.C for over the data and MC datasets and then analyse them | |
45 | using the CorrectSpectraMulti.C macro | |
46 | ||
db1bbbe1 | 47 | The typical use of runAAFMulti is (used for PbPb analysis in 2010) |
48 | root -q 'runAAFMulti.C( | |
49 | "/alice/data/LHC10h_000137366_p2", // input | |
50 | "resMultiWide_LHC10h_000137366_p2_eta_m08_p08_zv_m7_p7_zdczem.root", // output | |
51 | -1, // N events to process (-1 : all events) | |
52 | -0.5,0.5, // eta selection | |
53 | -7,7, // Zv selection | |
54 | 8, // centrality variable | |
55 | 0.7520, // rescale MC V0 to match data | |
56 | 1.5, // cut on weighed distance used to extract signal | |
57 | -1, // cut on dPhi-phiBent used to extract signal (if negative -> dphi*sqrt(cutSigNStd), recommended!) | |
58 | kTRUE, // fill MC info (macro detects automatically that MC is analysed from ../sim/.. in the input dataset name | |
59 | kTRUE, // redo tracklets reconstruction and use new AliMuliplicity to fill histos | |
60 | kTRUE // generate injected bg | |
61 | ... the rest is better to not touch.. | |
62 | )' | |
63 | ||
a9a39f46 | 64 | -------------------------------- |
65 | Both methods can use 3 types of generated bg: injection, rotation and mixing. | |
66 | Simultaneous eployment of all these methods is also possible, but may create | |
67 | a memory problem. | |
68 | ||
69 | The corresponding CorrectSpectra... macros must be tuned for the bg.type used. | |
70 | ||
db1bbbe1 | 71 | ----------------------------------------------------- |
72 | Update: Wed Apr 20 16:23:55 CEST 2011 | |
73 | Addapted AliTrackletTaskMulti for pp data analysis w/o bg generation. In this case | |
74 | the recpoints and the connection to OCDB (alien libs) are not needed. | |
75 | One should set the | |
76 | const Float_t AliTrackletTaskMulti::fgkCentPerc[] = {0,100}; | |
77 | and chose a centrality variable availabe in pp, like V0. | |
78 | Note that in this mode the AliMultiplicity object from the input dataset is used. | |
79 | ||
80 | The typical call of runAAFMulti is: | |
81 | ||
82 | root -q 'runAAFMulti.C("/alice/data/LHC10e_000130844_p2","resppWide_LHC10e_130844_p2_eta_m26_p26_zv_m20_p20a.root", | |
83 | -1, | |
84 | -2.6,2.6, | |
85 | -20,20,0, | |
86 | 0.7520, | |
87 | 2., // put it to large value to not affect the tracklet selection from existing AliMultiplicity object | |
88 | -1, | |
89 | kTRUE, | |
90 | kFALSE, // DO NOT do new reco of tracklets | |
91 | kFALSE, // DO NOT do bg. generation by injection | |
92 | kFALSE, // DO NOT do bg.generation by rotation | |
93 | kFALSE, // DO NOT do bg.generation by mixing | |
94 | 3.14159e+00, // irrelevant | |
95 | 1., // irrelevant | |
96 | kFALSE, // NO scaling of dtheta by sin^2(theta) (that's how pp data was reconstructed so far...) | |
97 | 2, // irrelevant | |
98 | 0.08, // dphi tolerance | |
99 | 0.025 // dtheta tolerance | |
100 | )' | |
101 | ||
102 | The sample macro ppcor.C shows how to extract dNdEta from the outputs of data and MC. | |
103 | ||
104 | ------------------------------------------------------------ |