(r5) EUTelescopeAndIBLTestbeam < DetDev

DetDev Web>EUTelescopeAndIBLTestbeam (revision 5) (raw view)~~EditAttach~~

---+!! %MAKETEXT{"EUTelescope And IBL Testbeam pages" args="<nop>%WEB%"}%

 <img width="600" alt="eutel-strategy.png" src="%ATTACHURLPATH%/eutel-strategy.png" height="400" />

<br /> Glasgow work on ATLAS Inner B-Layer (IBL) testbeam data. Both [[#ReconstructionAnchor][Reconstruction]] and [[#AnalysisAnchor][Analysis]] aspects of the work involve [[http://eutelescope.web.cern.ch/][EUTelescope]] software. Please see the official pages pages for more details.
A communal area with installed software and testfiles can be found: <code>/data/detdev01/FEI4_testbeam_construction</code>.

<b>NB</b> This page is a work in progress.

#ReconstructionAnchor
---++ %MAKETEXT{"Testbeam Reconstruction"}%

Reconstruction code can be found: <code>/data/detdev01/FEI4_testbeam_construction/reconstruction</code>. 

This is a short recipe for running.

* First set the environment.

<code>
> ILCSOFT=/data/detdev01/FEI4_testbeam_construction/reconstruction/PATH_TO_SOFTWARE
> cd $ILCSOFT
> source build_env.sh
</code>

To check the environment has been set correctly check the <code>EUTELESCOPE</code> parameter has been set:
<code>
> echo $EUTELESCOPE
</code>
This should be something like <code>/PATH_TO_SOFTWARE/v01-16-02/Eutelescope/v00-08-02</code>

* Next, go to the <code>jobsub</code> directory:

<code>
> cd $EUTELESCOPE/jobsub
</code>

You are now ready to run the reconstruction chain. There are five steps or "tasks" to transform raw data into analysis ready data: converter, clustering, hitmaker, alignment and filter. Each task is performed using the <code>jobsub.py</code> script and requires a condifuration file to set basic steering parameters such as input file, output directories and beam energy.
The basic execution format is 

<code>
> ./jobsub.py --config=CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER
</code>

Here is an example analysis chain:

<code>
> ./jobsub.py --config=$EUTELECOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv converter 97
> ./jobsub.py --config=$EUTELECOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv clustering 97
> ./jobsub.py --config=$EUTELECOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv hitmaker 97
> ./jobsub.py --config=$EUTELECOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv align 97
> ./jobsub.py --config=$EUTELECOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv fitter 97
</code>
For ease of running a bash script called <code>run_file.sh</code> is supplied which will run the chain for you. Please edit the parameters at the top of the file.

The output of each step should include a <code>root</code> file (only the first three are inspectable) and <code>lcio</code> files. The final output, <i>"someRun-tracking.root"</i> is used as the input for analysis.

For more details see the official pages [[http://eutelescope.web.cern.ch/content/job-submission][here]].

#AnalysisAnchor
---++ %MAKETEXT{"Testbeam Analysis"}%

The testbeam analysis software is called <b>tbmon</b> and can be found <code>/data/detdev01/FEI4_testbeam_construction/analysis/tbmon</code>.

The software has three main configuration files: <code>siteconfig.h</code>, <code>configs.cc</code> and <code>driver.cc</code>, which are all found in the trunk directory. The <code>siteconfig.h</code> file is where default parameters such as run numbers and configuration settings can be defined, though these can be overwritten on the commandline. After any editting of the files the <code>make</code> command must be rerun.

<b>NB</b> Be sure the version of root you are using includes libraries for <i>TFitResult</i> and <i>TFitResultPtr</i> i.e. version >=5.26. If needed do 

<code>
> source /data/ppe01/sl5x/x86_64/root/5.34.00/setup.sh
</code> 

The basic execution format is

<code>
> ./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -a ANLYSIS_TASK -c CONFIURATION_SET
</code>

Here is an example analysis chain:

<code>
> make
> ./tbmon -s 61527 -a hotpixelfinder -c eudetIBLsep2011
</code>

The output of analyses are root files and pictures (in a format which anc be specified in <code>siteconfig.h</code> or on the commandline with <code>-e</code> option).

For more details see some useful slides on [[%ATTACHURLPATH%/howtoTBmon.pdf][tbmon commands]] and [[%ATTACHURLPATH%/TBmon_Introduction_CERN_2012.pdf][software]].

-- Main.KennyWraight - 2013-05-24

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
pdf	TBmon_Introduction_CERN_2012.pdf	r1	manage	146.3 K	2013-05-29 - 09:46	KennyWraight	Slides on tbmon analysis
png	eutel-strategy.png	r1	manage	106.6 K	2013-05-24 - 11:33	KennyWraight	Schematic of EUTelescope strategy
pdf	howtoTBmon.pdf	r1	manage	61.0 K	2013-05-29 - 10:00	KennyWraight	full list of analysis options
png	recon_chain.png	r1	manage	58.4 K	2013-05-28 - 11:00	KennyWraight	reconstruction chain flowchart

Topic revision: r5 - 2013-05-29 - KennyWraight

DetDev