Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | EUTelescope And IBL Testbeam pages | |||||||
> > | EUTelescope And ITK Testbeam pages | |||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() | |||||||
Changed: | ||||||||
< < | Glasgow work on ATLAS Inner B-Layer (IBL) testbeam data. Both Reconstruction and Analysis aspects of the work involve EUTelescope ![]() /data/detdev01/FEI4_testbeam_construction . | |||||||
> > | Glasgow work on ATLAS EUTelescope, Pixel and ITK testbeam data. Both Reconstruction and Analysis aspects of the work involve EUTelescope ![]() /data/detdev01/FEI4_testbeam_construction . | |||||||
Some tips on post-analysis analysis are also noted. Information on finding data is given below. Here is a link to the DESY March 2012 analysis. | ||||||||
Changed: | ||||||||
< < | Also, UK activites are documented on Kate's pages on PUUKA. | |||||||
> > | Also, UK activites are documented on Kate's pages on PUUKA. | |||||||
NB This page is a work in progress. | ||||||||
Line: 51 to 51 | ||||||||
Testbeam Analysis | ||||||||
Changed: | ||||||||
< < | 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![]() | |||||||
> > | 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![]() | |||||||
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. | ||||||||
Line: 63 to 63 | ||||||||
> ./tbmon -s/r/l RUN_NUMBER(s)/RUN_LIST -a ANALYSIS_TASK -c CONFIGURATION_SET | ||||||||
Changed: | ||||||||
< < | Other options can be added, for example -o OUTPUT_PATH and -d INPUT_PATH . | |||||||
> > | Other options can be added, for example -o OUTPUT_PATH and -d INPUT_PATH . | |||||||
Here is an example analysis chain: | ||||||||
Line: 92 to 92 | ||||||||
Tips on post-analysis analysis | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | 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. | |||||||
Changed: | ||||||||
< < | Use maxcellres_DUT_chi2 and maxcellres_DUT_lv1 (with DUT appropriately substituted) to check the best chi2 and lv1 cuts in analysis. | |||||||
> > | Use maxcellres_DUT_chi2 and maxcellres_DUT_lv1 (with DUT appropriately substituted) to check the best chi2 and lv1 cuts in analysis. | |||||||
Testbeam Data |