130 likes | 137 Vues
This project recap discusses the specifications of the pixel detector system, the electronics and scanning techniques used for calibration. It also explains the origins of the project and the components involved, such as DataAnalysis and MyAnalyse. The system allows for data analysis and visualization of module scans, with information displayed on a website.
E N D
An Online Organizational System for ATLAS Pixel Detector System Test Scan Information Devin Harper Supervisor: Andreas Korn, LBL 10 August 2006
A Final Recap… Pixel Detector Specs FE Chips Modules • Silicon Pixel Detector • Pixel size = 400µm x 50µm • ~80M channel readout • Electronics • Ionization of Depletion Zone • Pixel-to-Bump technology Barrel Endcaps
Electronics Review • Analog signal • Discriminator • Time Over Threshold • Measure of charge • Digital Signal Threshold Scan – performed on each pixel to calibrate tuning Illustration of Analog signal compared to Digital signal
Scans • Testing in SR1 • Digital Scans • Threshold Scans • BOC Scans • Information is stored • Directories • *.root files • *.txt logfiles
Origins of the Project… After becoming acquainted with the current status and functions happening in SR1, it was my turn to help… • Time to begin learning: • Perl • Learning capabilities • Analyzing text • Analyzing outputs • Incorporating with HTML • C++ • More in-depth look at entities • Classes, libraries, etc. • Working with ROOT
Locate ROOT files, run Data Analysis [Perl] Display this info [WWW ] On to the web [WWW] Links particular to module scan [Perl] Run ROOT, create histo, save file MyAnalyse Generate graphics [C++ ] Data Analysis gives info summary about module scans [C++ ] The Basic Concept
Explanation of Components • data_analysis.pl • Sorts through directories • Executes DataAnalysis on *.root files (see below) • Displays output of DataAnalysis on WWW • DataAnalysis • Joern Grosse-Knetter & Martin Schmitz • *.root file as input • Text output, summary information about scans for each module • Can be run with a GUI – not applicable for what we’re doing this summer • MyAnalyse • Executes ROOT • Particular to module scan, generates TCanvas • Draws histogram particular to that scan onto TCanvas • Saves this histogram in relevant directory • Histogram written, overwritten on the fly
URLs • Pixel collaborator goes to address: • http://atlpclbl01.cern.ch:8838/cgi-bin/testarea/data_analysis.pl • [http://atlpclbl01.cern.ch:8838/html/data_analysis.html] (cached version) • Clicking link directs to another URL, specific to scan • http://atlpclbl01.cern.ch:8838/cgi-bin/testarea/input.pl • Initially, worked with logfiles • Important, as are *.root files • Perl >> working with text >> output onto WWW
data_analysis.html Link particular to scan, showing summary information
Input.pl Histogram particular to scan, with summary information listed
Room For Improvement: • Quicker generation of initial link page • Perhaps as a cron-job, running once a day or so • Ability to pick the directory over which data_analysis.pl scans • Perhaps adding a link page displaying different directories • Perhaps having an input (e.g., field) to decide which directory is scanned
Acknowledgements • Pixel Group • Andreas Korn • Jens Weingarten • Mauro Donega • Daniel Dobos • CERN • Ingrid Schmid • Claudia Huber • University of Michigan • Homer Neal • Jean Krisch • Steve Goldfarb • Jeremy Herr • Ford Motor Company