Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
EUTelescope And ITK Testbeam pages![]() | |||||||||||||
Changed: | |||||||||||||
< < | Glasgow work on ATLAS EUTelescope, Pixel and ITK testbeam data. Both Reconstruction and Analysis aspects of the work involve EUTelescope ![]() <--A communal area with installed software and test files can be found:
Some tips on post-analysis analysis are also noted.
Also,
| ||||||||||||
> > | Glasgow work on ATLAS Pixel Upgrade Reconstruction and Analysis. | ||||||||||||
Changed: | |||||||||||||
< < | Link to the DESY March 2012 analysis (from 2013!). | ||||||||||||
> > | NB This page is a work in progress | ||||||||||||
Added: | |||||||||||||
> > | Some pages
| ||||||||||||
Changed: | |||||||||||||
< < | NB This page is a work in progress | ||||||||||||
> > | Link to the DESY March 2012 analysis (from 2013!).
<--A communal area with installed software and test files can be found: | ||||||||||||
Testbeam Reconstruction | |||||||||||||
Deleted: | |||||||||||||
< < | |||||||||||||
<-- A working version of the reconstruction code can be found: | |||||||||||||
Changed: | |||||||||||||
< < | To install your own code then follow the instructions here![]() | ||||||||||||
> > | There are five basic steps to run the reconstruction chain (i.e. to transform raw data into analysis ready data):
| ||||||||||||
Changed: | |||||||||||||
< < | This is a short recipe for running. | ||||||||||||
> > | Each task is performed using the job sub 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 example is $EUTELESCOPE/jobsub/examples/datura-noDUT. | ||||||||||||
Changed: | |||||||||||||
< < | * First, check the environment has been set correctly by echoing the EUTELESCOPE parameter: > echo $EUTELESCOPE This should be something like /PATH_TO_SOFTWARE/VERSION/Eutelescope/trunk | ||||||||||||
> > | For a more complete explanation see: ReconstructionDetails. Further official information on the software is available http://eutelescope.web.cern.ch/content/job-submission![]() ![]() | ||||||||||||
Changed: | |||||||||||||
< < | * Next, go to the jobsub directory: | ||||||||||||
> > | Simple Recipe | ||||||||||||
Changed: | |||||||||||||
< < | > cd $EUTELESCOPE/jobsub | ||||||||||||
> > | This is a short recipe for running, based on ~March 2015 version of code. After installing and sourcing environment main directory is $EUTELESCOPE (equivalent to /PATH_TO_SOFTWARE/VERSION/Eutelescope/trunk). | ||||||||||||
Changed: | |||||||||||||
< < | 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 | ||||||||||||
> > |
>echo $EUTELESCOPE | ||||||||||||
Changed: | |||||||||||||
< < | > jobsub --config=CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER | ||||||||||||
> > | This should be something like /PATH_TO_SOFTWARE/VERSION/Eutelescope/trunk. If not, then source $EUTELESCOPE/build_env.sh
> cd $EUTELESCOPE/jobsub/example/MYDIR | ||||||||||||
Changed: | |||||||||||||
< < | Alternatively the syntax can be:
> jobsub -c CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER
* Now you can proceed to run the reconstruction. Here is an example reconstruction chain:
> jobsub --config=$EUTELESCOPE/jobsub/examples/datura-noDUT/config.cfg -csv $EUTELESCOPE/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.
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 basic execution format is
> jobsub -c CONFIGURATION_FILE [-o PARAMETER_NAME=VALUE ] TASK_NAME FILE_NUMBER | ||||||||||||
Changed: | |||||||||||||
< < | For more details see the official pages here![]() | ||||||||||||
> > |
> jobsub -c config.cfg -csv runlist.csv converter 97
> jobsub -c config.cfg -csv runlist.csv clustering 97
> jobsub -c config.cfg -csv runlist.csv hitmaker 97
> jobsub -c config.cfg -csv runlist.csv align 97
> jobsub -c config.cfg -csv runlist.csv fitter 97
The output of each step should include a root file, in $MY_OUTPUT/histograms, and an lcio file, in $MY_OUTPUT/lcio. | ||||||||||||
Link to CustomReconstruction. | |||||||||||||
Changed: | |||||||||||||
< < | Testbeam Analysis | ||||||||||||
> > | 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: svn address![]() 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 >=5.26. If needed do
> source /data/ppe01/sl5x/x86_64/root/5.34.00/setup.sh
The basic execution format is
> ./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -a ANALYSIS_TASK -c CONFIGURATION_SET
Other options can be added, for example -o OUTPUT_PATH and -d INPUT_PATH .
Here is an example analysis chain:
> 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.
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.
Link to CustomAnalysis.
Tips on post-analysis analysisTo check the orientation of DUTs, use theclusterchecker_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 chi2 and lv1 cuts in analysis.
Testbeam DataData 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 spreadsheet on data sample and important parameters such as bias, theta and threshold.
Here is a link![]() 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
-- KennyWraight - 2013-05-24
|