MINOS - CalDetTracker Muon Tracking Package


UCL MINOS Homepage
Back to my MINOS


This is a guide to using Chris' Muon Tracking Code.

The latest version can be found at: pcminos01:/home/cbs/NewOffline/ You need CalDetTracker, PreFilter and macros/tracker.C

I strongly recommend you copy these files to one of your directories on pcminos01. If you want to run it on your laptop or somewhere else, you have to make sure you have all the right versions of root, gcc, the database etc. Good luck. It's all already done for you on pcminos01.

Don't forget to 'include' to CalDetTracker and PreFilter with ln -s ../CalDetTracker CalDetTracker in /include.

Its a good idea to initialise with Ryan's setup file. In a shell, type: source ~rjn/.bash_profile
You can now build the code. On pcminos01, type minossoftsetup to initialise the latest root and framework requirements. If you want to track beam or cosmic muons, it's best to set the parameters first before building.

Setting the PreFilter
Setting parameters for beam/cosmic muons

To build, simply type make clean all at a shell prompt the top directory. If you see an error like 'rootcint: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory' then you have not typed 'minossoftsetup' or your root is out of date. If it doesn't seem to work the first time, it's worth just typing 'make clean all' again. Sometimes a build is successful on the second attempt.

Once built, the program is run from the top directory with loon macros/tracker.C /path/C000xxxxx_0000.tdaq.root where xxxxx is the number of the muon file to be tracked and 'path' is the location of the file, normally in /data/0/ - /data/6/

If you're looking for certain muon files to run over, there is a searchable webpage of CalDet runlogs at: http://pc68.hep.ucl.ac.uk/~gjc/minos/calDet/runlog/
You can search for the run numbers of specific energies, positives/negatives, T7/T11 etc
You do still have to find it in /data/ though...

If the file you wish to run over is an mdaq.root and not a tdaq.root, it needs to be triggered first. Tell Phil A. (pa@hep.ucl.ac.uk)

If you see:

loon [0]
Processing macros/tracker.C...
TPath(0 in 0 out 0 filt.)
1) +DigitListModule::Get n=0 ( 0/ 0) t=( 0.00/ 0.00)
2) +DigitListModule::Reco n=0 ( 0/ 0) t=( 0.00/ 0.00)
3) +TrackerModule::Ana n=0 ( 0/ 0) t=( 0.00/ 0.00)

it is most likely that loon has not found the input file. Check the path again.

The output is: Trackerxxxxx_beam/cosmic.root. Type .q to close loon and write out this file. One possible way to view this file is to load it into ROOT and then type TrackerTree->MakeClass() This will generate a .h file which defines and loads all the data fields available and a .C file which contains a loop skeleton for analysis. This method works through ROOT and not the framework and does not compile so is slow but useful for a fast, non-complex analysis. To simply view the data, 'new TBrowser' can be used with the file loaded into ROOT.

Making Calibration constants

Putting the calibration constants into the database




Back Muon Tracker Top Page