Load("icepack"); –Reader:"> Load("icepack"); –Reader:">
Download presentation
Presentation is loading. Please wait.
Published byMarybeth Shelton Modified over 8 years ago
1
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 1 IceCube Collaboration Meeting March 19-23, 2005 Berkeley Oladipo O. Fadiran Clark Atlanta University Atlanta, Georgia. dipo@ctsps.cau.edu
2
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 2 IceCube Collaboration 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.
3
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 :cvs@alisoft.cern.ch /soft/cvsroot logincvs@alisoft.cern.ch cvs -d :pserver: cvs@alisoft.cern.ch /soft/cvsroot AliRoot/RALICE cvs@alisoft.cern.ch –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 http://www3.tsl.uu.se/~bouchta/ralice.html
4
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 4 IceCube Collaboration 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 data Tree* data=(TTree*)f→Get("T"); IceEvent* evt=0; // Define a pointer for an event data→SetBranchAddress("Events",&evt); // Couple it to the branch in the tree data→GetEntry(100); // Load a particular event (e.g. 100) into memory evt→Data(); // show overview of event data IceAOM* 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 function AliSignal* s=OM→GetSignal(1); //Access corresponding MUON DAQ data e.g. pADC Float_t adc=s→GetSignal("ADC");......}
5
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 5 IceCube Collaboration Meeting March 19-23, 2005 Berkeley Typical TWR Histogram (Flipped) Peak Time over Threshold (TOT) Threshold Baseline Charge Counts(mV/1.22) Bin No. Baseline: minimum of all histograms for the same OM Threshold: (www.ps.uci.edu/~silvestri/TWR) Electrical-100mv, Optical – 20mvwww.ps.uci.edu/~silvestri/TWR
6
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 6 IceCube Collaboration Meeting March 19-23, 2005 Berkeley where Sig( · ) represents Standard Deviation Correlation Coefficient (CC) –Definition: normalized measure of linear relationship between variables.
7
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 7 IceCube Collaboration 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.
8
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 8 IceCube Collaboration 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
9
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 9 IceCube Collaboration Meeting March 19-23, 2005 Berkeley TOT Plots
10
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 10 IceCube Collaboration 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.
11
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 11 IceCube Collaboration Meeting March 19-23, 2005 Berkeley Charge Plots Charge is computed as area under waveform between TOT
12
Evaluation of the Ralice/IcePack Data Analysis Functionality - TWR Feature Extraction as a Test case 12 IceCube Collaboration 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
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.