Top Banner
Data format Y. Horii 18th Nov. 2011
15

Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Dec 21, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Data formatData format

Y. Horii18th Nov. 2011

Page 2: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Introduction

• Good to have a common format between data and MC to analyze and compare them easily.

• Especially for the beam test, while it could also be useful also for the studies later.

Page 3: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Overview of the processes

Data (beam test 2011)

1) Raw waveform and trigger, timing, etc. (two binary files).

2) Pedestal-subtracted waveform and trigger, timing, etc. (single ROOT file).

3) Calibrated but full waveform, trigger, timing, etc. (single ROOT file).

4) Reduced data: time/charge of each channel, etc. (single ROOT file).

MC 1

1) ?

2) ?

3) Reduced data: time/charge of each channel, etc. (single ROOT file).

MC 2

1) ?

2) Reduced data: time/charge of each channel, etc. (single ROOT file).

We would like to discuss about this part.

Page 4: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Overview of the formatData MC

Common part.

Additional part for MC.

Page 5: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Common part btw data/MC

0) event ID

1) time, charge of each channelTime[CH] and Charge[CH] orTime[PMT][CH] and Charge[PMT][CH]

2) time/charge of trigger counters.

3) time/charge of timing counters.

4) variables for trackers?

5) variables for veto counter?

Based on beam test in 2010.Better or not to change framework?

Type? Unit?

Page 6: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Additional part for MC

• Better to be common between different MC samples, e.g. Hawaii and Ljubljana?

• If we have common part, what kind variables?

Do we have common part between different MCs?

Additional part. Could be different between different MCs.

Page 7: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Data format

[Tree Event]Int_t eventNumber;Int_t flag;Int_t numTracks;Int_t numData;Int_t numPhotons;Int_t numCounters;Int_t numMCCounters;

[Tree Track]Float_t x, y, z;Float_t px, py, pz;Float_t tlen;Float_t charge;Int_t lund;Int_t QbarID;Float_t time;Float_t ltime;Float_t LLpi, LLK, LLMu;

[Tree Data]Int_t QbarID;Int_t pmtID, chID;Int_t GID;Float_t TDC;Float_t x, y, z;Float_t t;Float_t gx, gy, gz;Float_t E;Int_t flag;Float_t length;Float_t LLpi, LLK, LLMu;[Tree Photon]

Float_t x, y, zFloat_t t;Float_t kx, ky, kzFloat_t E;Float_t length;Int_t nAdhesive1, 2, 3;Int_t nPMTAdhesive1, 2;Int_t nQuartz1, 2, 3;Int_t nWedge;Int_t nSteps;

[Tree Counter]Int_t ID;Int_t ADC;Int_t TDC;

[Tree MCCounter]Int_t ID;Int_t ADC[n];Int_t TDC[n];Float_t x, y;

These trees are the branches of a single Tree named BT2011.

(Tentative)

[Tree Run]Int_t runNumber;Int_t data_type;Float_t beam_angle;Float_t seed;...

Page 8: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.
Page 9: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Backup slides

Page 10: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Current format of MC of Hawaii 1

Page 11: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Current format of MC of Hawaii 2

Page 12: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Current format of MC of Hawaii 3

Page 13: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Current format of MC of Hawaii 4

Page 14: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Current format of MC of Hawaii 5

Page 15: Data format Y. Horii 18th Nov. 2011. Introduction Good to have a common format between data and MC to analyze and compare them easily. Especially for.

Current format of MC of Hawaii 6