1 / 7

RENO Event Data Model and Analysis Framework Overview

This document provides an overview of the RENO (REactor Experiment for Neutrino Oscillation) Event Data Model and the accompanying analysis framework developed by Jaison Lee. It describes the systematic scheme for handling real and Monte Carlo (MC) data, featuring the ability to interact with the RENO Analysis Control (RAC) framework. Critical functionalities include access to event data via the AbsEvent class, database configurations, and user-defined modules for data input and output. The framework supports sequential execution and easy module integration, ensuring effective data analysis.

inge
Download Presentation

RENO Event Data Model and Analysis Framework Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RENO Analysis Control&Event Data Model Jaison Lee 2008/Oct/11 RENO 9th Collaboration Meeting

  2. Event Data Model • For systematic scheme for real data and MC data • Interactivity (with RAC framework) • Data model may be not setup completely during production or reconstruction. Parts of data model can be created at a later stage during the analysis. • Access to the event data is through the event header, i.e. the AbsEvent class. From the header one can navigate to the various parts of event data, even run information.

  3. Event Data Model AbsEvent AbsRun Run Number Event Number Trigger Name Pmts Data production Detector Parameters Total Charge Arrival Time Raw data (FACD) • Database access for run configuration and calibration with run number and trigger name • All data will be stored in reno cluster (reno00.snu.ac.kr) Physics Data reconstruction Vertices Energy Vertices position Reconstructed Muon

  4. RENO Analysis Control RACFramework Raw / MC Data User’s Analysis Module Production Module Recon. Module Uers Ntp/His • Has default modules for data input and output, database access for run configuration and calibration • Has talk-to functionfor changing input parameters without recompiling • Can be added any modules by user, which are inherited from RACModule • Modules can be set as filter modulefor selecting events • Easy to use and build in RENO software environment

  5. RENO Analysis Control • In a framework, each module has a Job, Run and Event functions which are executed in sequence. • BeginJob • Executed once when a module start • Booking Histograms and Ntuples • BeginRun • Executed every new run • Get run configuration and calibration data from database • Event • Executed every new event • Something calculated • Filling histograms and ntuples • EndJob • Executed one when a module end • Writing histograms and ntuples into root file BeginJob BeginRun Event EndJob

  6. Example of Event in a Module boolAMod::Event(AbsEvent * anEvent) { intrunId = anEvent->GetCurrentRun()->GetRunId(); intevtId = anEvent->GetEventId(); //Get PMT Collection from AbsEvent TClonesArray * pmtColl = anEvent->GetPmtColl(); intnPmt = pmtColl->GetEntries(); //Iterating PMTs for(inti = 0; i < nPmt; i++){ Pmt * aPmt = (Pmt*)pmtColl->At(i); double charge = aPmt->GetCharge() ; double time = aPmt->GetTime() ; TVector3 pos = aPmt->GetPosition(); } }

  7. Example of Macro mod enable RACStdInputModule mod talk RACStdInputModule input set /users/jslee/devel/RenoSoft/FrameworkDevel/test.root nreport set 100 exit mod enable AMod mod talk AMod energy set 100 momentum set $MOMENTUM_VALUE exit mod disable BMod begin nev 1000

More Related