Difference: EUTelescopeAndIBLTestbeam (12 vs. 13)
Revision 132013-06-18 - KennyWraight
| Line: 1 to 1 | |||||||||
|---|---|---|---|---|---|---|---|---|---|
EUTelescope And IBL Testbeam pages | |||||||||
| Changed: | |||||||||
| < < | Glasgow work on ATLAS Inner B-Layer (IBL) testbeam data. Both Reconstruction and Analysis aspects of the work involve EUTelescope  software. Please see the official pages pages for more details.
A communal area with installed software and testfiles can be found: /data/detdev01/FEI4_testbeam_construction. | ||||||||
| > > | Glasgow work on ATLAS Inner B-Layer (IBL) testbeam data. Both Reconstruction and Analysis aspects of the work involve EUTelescope software. Please see the official pages pages for more details. A communal area with installed software and testfiles can be found: /data/detdev01/FEI4_testbeam_construction. | ||||||||
| Information on finding data is given below. | |||||||||
| Changed: | |||||||||
| < < | NB This page is a work in progress. | ||||||||
| > > | NB This page is a work in progress. | ||||||||
Testbeam Reconstruction | |||||||||
| Changed: | |||||||||
| < < | A working version of the reconstruction code can be found: /data/detdev01/FEI4_testbeam_construction/reconstruction. | ||||||||
| > > | A working version of the reconstruction code can be found: /data/detdev01/FEI4_testbeam_construction/reconstruction. | ||||||||
|
If you want to install your own code then follow the instructions here. | |||||||||
| Line: 22 to 21 | |||||||||
| * First set the environment. | |||||||||
| Changed: | |||||||||
| < < |
> ILCSOFT=/data/detdev01/FEI4_testbeam_construction/reconstruction/v01-17-01/Eutelescope/v00-08-02
To check the environment has been set correctly check the EUTELESCOPE parameter has been set:
> echo $EUTELESCOPE
This should be something like /PATH_TO_SOFTWARE/v01-16-02/Eutelescope/v00-08-02
* Next, go to the jobsub directory:
> cd $EUTELESCOPE/jobsub | ||||||||
| > > | > ILCSOFT=/data/detdev01/FEI4_testbeam_construction/reconstruction/v01-17-01/Eutelescope/v00-08-02 | ||||||||
| Changed: | |||||||||
| < < | 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 jobsub.py script and requires a configuration file to set basic steering parameters such as input file, output directories and beam energy.
The basic execution format is | ||||||||
| > > | To check the environment has been set correctly check the EUTELESCOPE parameter has been set: > echo $EUTELESCOPE This should be something like /PATH_TO_SOFTWARE/v01-16-02/Eutelescope/v00-08-02
* Next, go to the jobsub directory:
> cd $EUTELESCOPE/jobsub | ||||||||
| Changed: | |||||||||
| < < |
> ./jobsub.py --config=CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER | ||||||||
| > > | 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 jobsub.py script and requires a configuration file to set basic steering parameters such as input file, output directories and beam energy. The basic execution format is
> ./jobsub.py --config=CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER | ||||||||
| * Now you can proceed to run the reconstruction. Here is an example reconstruction chain: | |||||||||
| Changed: | |||||||||
| < < |
> ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv converter 97
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. | ||||||||
| > > | > ./jobsub.py --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELECOPE/jobsub/examples/datura-noDUT/runlist.csv converter 97 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. | ||||||||
| Changed: | |||||||||
| < < | 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. | ||||||||
| > > | 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 here. | |||||||||
| Line: 67 to 46 | |||||||||
Testbeam Analysis | |||||||||
| Changed: | |||||||||
| < < | The testbeam analysis software is called tbmon and can be found /data/detdev01/FEI4_testbeam_construction/analysis/tbmon. | ||||||||
| > > | The testbeam analysis software is called tbmon and can be found /data/detdev01/FEI4_testbeam_construction/analysis/tbmon. | ||||||||
| Changed: | |||||||||
| < < | 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. | ||||||||
| > > | 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. | ||||||||
| Changed: | |||||||||
| < < | NB Be sure the version of root you are using includes libraries for TFitResult and TFitResultPtr i.e. version >=5.26. If needed do | ||||||||
| > > | NB Be sure the version of root you are using includes libraries for TFitResult and TFitResultPtr i.e. version >=5.26. If needed do | ||||||||
| Changed: | |||||||||
| < < |
> source /data/ppe01/sl5x/x86_64/root/5.34.00/setup.sh | ||||||||
| > > | > source /data/ppe01/sl5x/x86_64/root/5.34.00/setup.sh | ||||||||
| The basic execution format is | |||||||||
| Changed: | |||||||||
| < < |
> ./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -a ANALYSIS_TASK -c CONFIGURATION_SET | ||||||||
| > > | > ./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -a ANALYSIS_TASK -c CONFIGURATION_SET | ||||||||
| Here is an example analysis chain: | |||||||||
| Changed: | |||||||||
| < < |
> cd PATH_TO_ANALYSIS/tbmon/trunk
edit driver.cc to set bool masknoisyanddeadpixels = true in relevant subroutine (e.g. here eudetIBLsep2011)
> make
no need to edit or make here
> ./tbmon -s 61527 -a getetacorr -c eudetIBLsep2011
edit driver.cc to set bool applyetacorr = true and bool applytranslation = false
> make
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.
> make
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 > source basic_analysis.sh.
At this point any additional analyses can be run without further make commands.
E.g. to perform residuals analysis:
> ./tbmon -s 61527 -a residuals -c eudetIBLsep2011
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. | ||||||||
| > > | > cd PATH_TO_ANALYSIS/tbmon/trunk edit driver.cc to set bool masknoisyanddeadpixels = true in relevant subroutine (e.g. here eudetIBLsep2011)
> make no need to edit or make here
> ./tbmon -s 61527 -a getetacorr -c eudetIBLsep2011 edit driver.cc to set bool applyetacorr = true and bool applytranslation = false
> make 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.
> make
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 > source basic_analysis.sh. | ||||||||
| Changed: | |||||||||
| < < | 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). | ||||||||
| > > | At this point any additional analyses can be run without further make commands. E.g. to perform residuals analysis:
> ./tbmon -s 61527 -a residuals -c eudetIBLsep2011 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 tbmon commands and software. | |||||||||
| Line: 137 to 87 | |||||||||
| Data can be found at Dortmund, DESY and CERN. | |||||||||
| Added: | |||||||||
| > > | DESY | ||||||||
Test data can be run directly over AFS from DESY. The address is /afs/desy.de/group/telescopes/EutelTestData/. | |||||||||
| Added: | |||||||||
| > > | 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 spreadsheet on data sample and important parameters such as bias, theta and threshold.
Here is a 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). | |||||||||
| Added: | |||||||||
| > > | 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/ . | ||||||||
-- KennyWraight - 2013-05-24
| |||||||||
| Changed: | |||||||||
| < < |
| ||||||||
| > > |
| ||||||||
View topic | History: r30 < r29 < r28 < r27 | More topic actions...
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback