evaluation of the ralice/icepack data analysis functionality - twr feature extraction as a test...
DESCRIPTION
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 3 IceCube Collaboration Meeting March 19-23, 2005 Berkeley Getting Ralice/IcePack –Ralice: checkout from CERN repository cvs -d :pserver /soft/cvsroot cvs -d :pserver: /soft/cvsroot AliRoot/RALICE –IcePack: Run install scripts in $RaliceHome/scripts/ and $RaliceHome/Icepack/scripts/ directories –Root setup: create ROOT startup script e.g. rootlogon.C containing the following lines gSystem->Load("ralice"); gSystem->Load("icepack"); –Reader:TRANSCRIPT
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case
1
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
Oladipo O. Fadiran
Clark Atlanta UniversityAtlanta, [email protected]
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
2
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Introduction– What is Ralice ?
• Lightweight and flexible analysis package based on existing Alice software
• Generic – can be used in other environments/experiments.• Easy to use and runs on all ROOT supported platforms.
– IcePack: Interfaces between Ralice and elements/structures specific to IceCube
– Objective: Test Ralice/IcePack functionality for TWR data access and analysis
– Reader(rdmc) : standard AMANDA package. Accesses F2k files and stores them in ROOT format.
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
3
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Getting Ralice/IcePack – Ralice: checkout from CERN repository
cvs -d :pserver:[email protected]/soft/cvsroot logincvs -d :pserver:[email protected]/soft/cvsroot AliRoot/RALICE– IcePack: Run install scripts in $RaliceHome/scripts/ and
$RaliceHome/Icepack/scripts/ directories
– Root setup: create ROOT startup script e.g. rootlogon.C containing the following lines
gSystem->Load("ralice");gSystem->Load("icepack");– Reader: http://www3.tsl.uu.se/~bouchta/ralice.html
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
4
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Example Macro // Macro to attach and open an IceCube event file for interactive investigation. // To run this file test Macro, do $root f_name.C {TFile* f=new TFile("run_data.root"); // Access to the input dataTree* data=(TTree*)f→Get("T");IceEvent* evt=0; // Define a pointer for an eventdata→SetBranchAddress("Events",&evt); // Couple it to the branch in the tree data→GetEntry(100); // Load a particular event (e.g. 100) into memoryevt→Data(); // show overview of event dataIceAOM* OM=(IceAOM*)evt→GetIdDevice(97); // Get data from individual (e.g. 97) Device (OM)TH1F* wave=OM→GetWaveform(2); // Access specific waveform from OM wave→Draw(); // Draw waveform or perform other analysis functionAliSignal* s=OM→GetSignal(1); //Access corresponding MUON DAQ data e.g.
pADCFloat_t adc=s→GetSignal("ADC"); ... ...}
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
5
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Typical TWR Histogram (Flipped)Peak
Time over Threshold
(TOT)
Threshold
Baseline
ChargeC
ount
s(m
V/1
.22)
Bin No.
Baseline: minimum of all histograms for the same OMThreshold: (www.ps.uci.edu/~silvestri/TWR) Electrical-100mv, Optical – 20mv
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
6
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
11;
CC
ysigxsigyxxy
CC
"",0)(,1)(Noccabs
iprelationshlinearstrongccabs
where Sig(·) represents Standard Deviation
• Correlation Coefficient (CC)
– Definition: normalized measure of linear relationship between variables.
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
7
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Correlation Plots for pADC– Dataset from run No.8084, Oct. 2004., 500 events. Not
calibrated.– Same dataset used for results shown in this presentation.
Plotted values for instances when particular OM is activated for all recorded events in dataset.
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
8
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Correlation Plots for pADC Contd.
Plotted values for computed CC values for all activated OMs for all recorded events in the dataset
7% of activated OMs have CC < 0.7
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
9
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• TOT Plots
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
10
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Correlation Plots for TOT
Plotted values for instances when particular OM is activated for all recorded events in dataset.
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
11
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Charge Plots
Charge is computed as area under waveformbetween
TOT
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test
case
12
IceCube Collaborati
on Meeting
March 19-23, 2005
Berkeley
• Summary– Usability:
• Easy data access and analysis with existing and evolving Ralice/IcePack Routines
– Extracted TWR data:• Good comparison with MuonDAQ data.• Confirmed existing conditions (dead OMs on string 17)
– Time: • Data with 500 events took Approx. 30secs for file access, data
analysis and result display on Pentium IV 3.2GHz PC. The Macro was run interactively in the ROOT framework by using the CINT C++ interpreter.
• Time increase is Approx. linear