Analyzing the output of the MuCTPI simulation

Creating analizable ROOT NTuples

I assume, that you have now the POOL file with the output of the MuCTPI simulation ready. The easiest way to analyze it is to "translate" it to a standard ROOT file. I've been using the following two jobOption files to do this: and should generally be set up right to run the job, one should only modify There the input and output file names can be defined, together with the detector decription version. Still remember to use the same DD, as earlier!

Having copied the two job option files to your run directory, and set up CMT, the NTuple creation job can be run with the command: #> (Note: To use these jobOptions, you'll also need at least version TrigT1Muctpi-00-00-24 of the MuCTPI simulation.)

Analyzing the NTuples

I've written two classes usable from a ROOT macro, which give easy access to the data words of the output of the MuCTPI simulation. Detailed information on the format of these data words can be found in the MIROD manual. The two classes are MuonDataWordAnalyzer and MuonMultiplicityAnalyzer. Their source code can be found in this page's attachments.

Of course there can be very different things to analyze. To give an example, here is a simple macro, that prints out various informations of the muon candidates: double_muon_info.C

(I assume the reader has some experience with running ROOT macros, so I don't go into detail on how to use these.)

Modifying the look up tables of the MuCTPI simulation

The sector logics of the barrel and endcap trigger chambers are connected to 16 so called MIOCT modules. These modules are responsible for resolving overlapping muon candidates (probably coming from the same muon). More secription on how this is done can be found in the MIOCT manual.

As can be seen on the 3. page of the document, one MIOCT is responsible for resolving the overlaps between 4 Barrel and 6 Endcap sectors. It can also be seen from the figure, that there should be no overlaps between the "upper" and "lower" sectors. Note: The layout of the Forward sectors has changed since the writing of this document.

The LUT files should define, when two muon candidates should be considered as coming from the same physical muon. The structure of the LUT files is much the same as the tables found at the end of the MIOCT document. For each condition in which a muon candidate should be suppressed, there is a row in the LUT. (Lines beginning with a # are comments. Also, there should be no empty lines.) There is actually some description on the meaning of the various columns in the example file (~/data/

There can be 2 muon candidates coming from each of the sectors. For each candidate it's RoI and overlap flag should be defined. An RoI and overlap flag of 0 means that the given candidate is not considered. (Note: The code may change in this respect later on! This scheme was developed to handle barrel phi overlaps with overlap flags set. If we want to handle overlaps between the barrel and the endcap where the overlap flag in the barrel is not set, this might have to be changed!)

The last 16 numbers in the rows define which candidate should be discarded in case of an overlap. 1 means the candidate should be suppressed, and 0 means the candidate should be kept. The order is documented in the sample file.

About the layout of the sectors

The MIOCT modules get the input from the following barrel and endcap sectors (I really hope this is accurate...):

MIOCT number Name in LUT BA01 BA02 EC01 EC02 EC03
1 Sector Number upper 0 1 0 1 2
lower 30 31 45 46 47
2 Sector Number upper 4 5 6 7 8
lower 2 3 3 4 5
3 Sector Number upper 8 9 12 13 14
lower 6 7 9 10 11
4 Sector Number upper 12 13 18 19 20
lower 10 11 15 16 17
5 Sector Number upper 16 17 24 25 26
lower 14 15 21 22 23
6 Sector Number upper 20 21 30 31 32
lower 18 19 27 28 29
7 Sector Number upper 24 25 36 37 38
lower 22 23 33 34 35
8 Sector Number upper 28 29 42 43 44
lower 26 27 39 40 41

The other 8 MIOCTs have the same sector numbers, but for the sectors of the other rapidity region.

The current idea is, that the different MIOCTs handle the overlaps in the same way, ie. using the same look up tables. If the optimization requires, this could be changed later on.

About my first look at phi overlaps

I created the sample LUT, by shooting single muons in the eta=0.0 - 1.0, phi=0.18 - 0.22 region with a pt of 30 GeV. This is the overlap region of the barrel sectors 0 and 1. Hence the "upper" in the name of the file, if you look at the previous table.

If you look at the file, there are a lot of conditions defined, in which the first or second candidate of BA01 (sector 0 in this case) overlaps with the first or second candidate of BA02 (sector 1 in this case).

-- AttilaKrasznahorkay - 24 Oct 2005

Topic attachments
I Attachment History Action Size Date Who Comment
C source code filec MuonDataWordAnalyzer.C r1 manage 2.1 K 2005-10-24 - 16:21 AttilaKrasznahorkaySecondary analysis code
Header fileh MuonDataWordAnalyzer.h r1 manage 0.6 K 2005-10-24 - 16:21 AttilaKrasznahorkaySecondary analysis code
C source code filec MuonMultiplicityAnalyzer.C r1 manage 0.7 K 2005-10-24 - 16:22 AttilaKrasznahorkaySecondary analysis code
Header fileh MuonMultiplicityAnalyzer.h r1 manage 0.5 K 2005-10-24 - 16:22 AttilaKrasznahorkaySecondary analysis code
C source code filec double_muon_info.C r1 manage 4.3 K 2005-10-24 - 16:22 AttilaKrasznahorkaySecondary analysis code
Python source code filepy r1 manage 4.9 K 2005-10-24 - 15:48 AttilaKrasznahorkaySecondary Main jobO for NTuple creation.
Python source code filepy r1 manage 0.7 K 2005-10-24 - 15:48 AttilaKrasznahorkaySecondary Configuration for NTuple creation
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2005-10-24 - AttilaKrasznahorkaySecondary
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback