(r27) EUTelescopeAndIBLTestbeam < DetDev

DetDev Web>EUTelescopeAndIBLTestbeam (revision 27) (raw view)~~EditAttach~~
---+!! %MAKETEXT{"EUTelescope And ITK Testbeam pages" args="<nop>%WEB%"}%

<img alt="eutel-strategy.png" height="400" src="/twiki/pub/DetDev/EUTelescopeAndIBLTestbeam/eutel-strategy.png" width="600" />

<br /> Glasgow work on ATLAS EUTelescope, Pixel and ITK 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 test files can be found: =/data/detdev01/FEI4_testbeam_construction=. -->
Some tips on [[#PostAnchor][post-analysis analysis]] are also noted.

Also,
      * Information on finding data is given [[#DataAnchor][below]].
      * EUDAQ pages are also available [[DataAcquisition][here]]. 
      * UK activites are documented on Kate's pages on [[ATLAS.PUUKA.Reconstruction][PUUKA]]
      * Find the working group meetings on [[https://indico.cern.ch/category/1390/][indico]]
      * Instruction for simulating telescope data with <nop>AllPix</nop> [[TelescopeSimulation][here]]
      * Instruction for custominsing [[CustomReconstruction][reconstruction]] and [[CustomAnalysis][analysis]] are also available

Link to the [[TestBeamAnalysisMarch2012][DESY March 2012 analysis]] (from 2013!).


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

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

<!-- A working version of the reconstruction code can be found: =/data/detdev01/FEI4_testbeam_construction/reconstruction=. -->

To install your own code then follow the instructions [[http://eutelescope.web.cern.ch/content/installation][here]].

This is a short recipe for running.

* First, check the environment has been set correctly by echoing the =EUTELESCOPE= parameter: <code> &gt;<cite> echo $EUTELESCOPE</cite><br /> </code> This should be something like =/PATH_TO_SOFTWARE/VERSION/Eutelescope/trunk=

* Next, go to the =jobsub= directory:

<code> &gt;<cite> cd $EUTELESCOPE/jobsub</cite><br /> </code>

There are five basic steps to run the reconstruction chain (i.e. to transform raw data into analysis ready data): converter, clustering, hitmaker, alignment and filter. Each task is performed using the =jobsub= command (exported when the build environment is set) and requires a configuration file to set basic steering parameters such as input file, output directories and beam energy. The basic execution format is

<code> &gt;<cite> ./jobsub.py --config=CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER</cite><br /> </code>

* Now you can proceed to run the reconstruction. Here is an example reconstruction chain:

<code> &gt;<cite> ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELESCOPE/jobsub/examples/datura-noDUT/runlist.csv converter 97</cite><br /> &gt;<cite> ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELESCOPE/jobsub/examples/datura-noDUT/runlist.csv clustering 97</cite><br /> &gt;<cite> ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELESCOPE/jobsub/examples/datura-noDUT/runlist.csv hitmaker 97</cite><br /> &gt;<cite> ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELESCOPE/jobsub/examples/datura-noDUT/runlist.csv align 97</cite><br /> &gt;<cite> ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELESCOPE/jobsub/examples/datura-noDUT/runlist.csv fitter 97</cite><br /> </code> For ease of running a bash script called =run_file.sh= is in =/data/detdev01/FEI4_testbeam_construction/reconstruction= 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 =root= file (only the first three are inspectable) and =lcio= files. The final output, _"SOMERUN-tracking.root"_ is used as the input for analysis.

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

Link to CustomReconstruction.

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

The testbeam analysis software is called *tbmon* and can be found =/data/detdev01/FEI4_testbeam_construction/analysis/tbmon= and the tbmon source code is available on svn: [[https://svnweb.cern.ch/cern/wsvn/atlasibltbsw/tbmon/#a97ba5b7aa1e4e720087ca69f960596cc?][svn address]].

The software has three main configuration files: =siteconfig.h=, =configs.cc= and =driver.cc=, which are all found in the trunk directory. The =siteconfig.h= 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 =make= command must be rerun.

*NB* Be sure the version of root you are using includes libraries for _TFitResult_ and _TFitResultPtr_ i.e. version &gt;=5.26. If needed do

<code> &gt;<cite> source /data/ppe01/sl5x/x86_64/root/5.34.00/setup.sh</cite><br /> </code>

The basic execution format is

<code> &gt;<cite> ./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -a ANALYSIS_TASK -c CONFIGURATION_SET</cite><br /> </code>

Other options can be added, for example  =-o OUTPUT_PATH= and  =-d INPUT_PATH= .

Here is an example analysis chain:

<code> &gt;<cite> cd PATH_TO_ANALYSIS/tbmon/trunk</cite><br /> &gt;<cite> make</cite><br /> &gt;<cite> ./tbmon -s 61527 -a hotpixelfinder -c eudetIBLsep2011</cite><br /> &gt;<cite> cp OUTPUT_PATH/run61527-hotpixelfinder-*txt IBLcalibs/</cite><br /> </code> edit =driver.cc= to set =bool masknoisyanddeadpixels = true= in relevant subroutine (e.g. here eudetIBLsep2011)

<code> &gt;<cite> make</cite><br /> &gt;<cite> ./tbmon -s 61527 -a checkalign -c eudetIBLsep2011</cite><br /> &gt;<cite> cp OUTPUT_PATH/run61527-checkalign-*txt IBLcalibs/</cite><br /> </code> no need to edit or make here

<code> &gt;<cite> ./tbmon -s 61527 -a getetacorr -c eudetIBLsep2011</cite><br /> &gt;<cite> cp OUTPUT_PATH/run61527-getetacorr-*txt IBLcalibs/</cite><br /> </code> edit =driver.cc= to set =bool applyetacorr = true= and =bool applytranslation = false=

<code> &gt;<cite> make</cite><br /> &gt;<cite> ./tbmon -s 61527 -a checkalign -c eudetIBLsep2011</cite><br /> </code> edit =driver.cc= to set =bool applytranslation = true= and comment out =hotpixelfinder=, =getetacorr= and =checkalign= analysis objects from the =allAnalyses= function at the top of the file.

<code> &gt;<cite> make</cite><br /> </code>

for ease of use these steps are combined in the =basic_analysis.sh= file. In it the common =tbmon= command without a specified task (i.e. =./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -c CONFIGURATION_SET=) is set at the top to the =basicCommand= variable. This should be editted to refer to the correct and run set and =siteconfig= file. Also an *uneditted* =driver.cc= file should be copied to =defaultdriver.cc= to avoid any uneccessary file changes to the original =driver.cc= file. Once this is done the previous steps can be run in serial using the sole command =&gt; source basic_analysis.sh=.

At this point any additional analyses can be run without further =make= commands. E.g. to perform residuals analysis:

<code> &gt;<cite> ./tbmon -s 61527 -a residuals -c eudetIBLsep2011</cite><br /> </code> All standard analysis code resides in =trunk/analysis/src=. If no analysis is specified on the commandline then all analyses in the =allAnalyses= function of =driver.cc= are run.

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

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

Link to CustomAnalysis.

#PostAnchor
---++ %MAKETEXT{"Tips on post-analysis analysis"}%

To check the orientation of DUTs, use the =clusterchecker_DUT_matchClusterSizeX= and =clusterchecker_DUT_matchClusterSizeX=, with =DUT= appropriately substituted. One or other should relatively increase with any orthogonal tilt of the device. This can be compared to the recorded orientation of the device with respect to the beam.

Use =maxcellres_DUT_chi2= and =maxcellres_DUT_lv1= (with =DUT= appropriately substituted) to check the best <code>chi<sup>2</sup></code> and =lv1= cuts in analysis.

#DataAnchor
---++ %MAKETEXT{"Testbeam Data"}%

Data can be found at Dortmund, DESY and CERN.

*DESY*

Test data can be run directly over AFS from DESY. The address is =/afs/desy.de/group/telescopes/EutelTestData/=.

*Dortmund*

Data at Dortmund must be copied locally and can only be accessed once an account has been set up on the Dortmund server. To do this you will need to contact =andre.rummler@tu-dortmund.de= .

Here is a [[%ATTACHURLPATH%/PPS_March2012_BatchSummary.xlsx][spreadsheet]] on data sample and important parameters such as bias, theta and threshold.

Here is a [[https://twiki.cern.ch/twiki/bin/viewauth/Atlas/IBL][link]] to ATLAS twiki. In the Testbeams there are links to the pages of each testbeam. Then on each page there is a link to a spreadsheet with run information hosted on google docs. You may need to ask for permission to view the data (just log-in to google, click to ask permission and wait for someone to add you, no questions asked).

*CERN*

Data can be found at CERN by first logging on to lxplus then sourcing the necessary EOS build: =source /afs/cern.ch/project/eos/installation/atlas/etc/setup.sh=

EOS can then be launched vai the =eos= command.

A list of testbeam data can be found: =/eos/atlas/atlascerngroupdisk/pixel-upgrade/pps/BeamTest/= .

*GRID*

Requires a VO for ilc (done by DESY)

source /afs/cern.ch/project/gd/LCG-share/current/etc/profile.d/grid_env.sh

lcg-infosites --vo ilc lfc

export LFC_HOST=grid-lfc.desy.de

voms-proxy-init --voms ilc

Data can be found at:

lfc-ls -l /grid/ilc/aida-wp9

copy files (example)

lcg-cp --vo ilc lfn:/grid/ilc/aida-wp9/2012/tb-desy-spring/pps/joboutput/fitter/tbtrack999.root ./tbtrack999.root

-- Main.KennyWraight - 2013-05-24
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
xlsx	PPS_March2012_BatchSummary.xlsx	r1	manage	90.4 K	2013-06-18 - 11:36	KennyWraight	Spreadsheet with description of testbeam runs
xlsx	PPS_March2012_BatchSummary_extradetail.xlsx	r1	manage	91.1 K	2013-06-27 - 15:38	KennyWraight	Spreadsheet with description of testbeam runs
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: r27 - 2015-04-20 - KennyWraight
DetDev