EUTelescope And IBL Testbeam pages

Notes on customising analysis of IBL testbeam data using tbmon.

Assuming you are in PATH_TO_ANALYSIS directory...

To add new code to analyses you'll need to create/edit files in PATH_TO_ANALYSIS/analysis/ part of the file structure. A header (i.e. .h file) must be in the analysis/include directory with all declarations (classes, member functions, variables etc.). The corresponding source (i.e. .cc file) file must be in the analysis/src directory with all the analysis functionality.

If you are creating a new anlysis you'll need to tell the rest of the software about it. Once you have created someAnalysis.h and files the code must be introduced in the file in the PATH_TO_ANALYSIS directory. The analysis must be added to the set of included files at the begining of the file (e.g. #include "someanalysis.h") and added to the list of possible analyses in the allAnalyses function (e.g. config.addAnalysis(new SomeAnalysis, "someanalysis", dut);).

The last thing to do is mention the new analysis in the Makefile so that it is compiled along with the rest of the software. You must add a .o mention (e.g. someanalysis.o to the ANALYSIS section of the Makefile.

After any changes the code must be recompiled:

> make

Then, supposing you have gone through all the steps required before running analysis algorithms* (here) you can run your custom analysis like any other task:


* Changes made only to analysis will not require rerunning of hotpixelfinder, checkalign, getetacorr, checkalign steps.

-- KennyWraight - 2013-06-11

Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2013-06-11 - KennyWraight
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