understanding the data - a first off-line look

25
Understanding the data - a first off-line look Sylvie Dagoret-Campagne EUSO-BALLOON Analysis Meeting, October 2-3 2014 1

Upload: fenella-peoples

Post on 01-Jan-2016

19 views

Category:

Documents


0 download

DESCRIPTION

Understanding the data - a first off-line look. Sylvie Dagoret-Campagne. Global look. All packets over all runs, Try to understand the meaning data in the ROOT file, Try to understand the distribution of these data (expected or strange) Try to identify bugs or good data. How it is done. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 1

Understanding the data - a first off-line

look Sylvie Dagoret-Campagne

Page 2: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 2

Global lookAll packets over all runs,

Try to understand the meaning data in the ROOT file,

Try to understand the distribution of these data (expected or strange)

Try to identify bugs or good data

Page 3: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 3

How it is done

Scurves

Acquisition

CPU-TRIGGER

ETOT

Scurves Merged

Acquisition

Merged

CPU-Trigger Merged

.DAT data

.ROOT data

ETOTAna

SCurves

Acquisition

SCurves

CPU Trigger

Page 4: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 4

ETOT data Structure4 Trees :

tevent : Event packet tree (physically oriented) One entry is one GTU

televent : Event packet tree (electronics oriented) One tree entry is one packet

texp : Experiment information tree (detector description)

tdataflow : Hardware data flow tree (CPU messages)

No information is lost from raw data to ROOT data !!!

Page 5: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 5

ETOT data : televent tree data structure

*Tree :televent : Event packet tree (electronics oriented) **Entries : 2000 : Total = 816822060 bytes File Size = 142746500 ** : : Tree compression factor = 5.72 ********************************************************************************Br 0 :cpu_packet_header : header/I **Entries : 2000 : Total Size= 8577 bytes File Size = 156 **Baskets : 1 : Basket Size= 32000 bytes Compression= 51.85 *............................................................................**Br 1 :cpu_packet_evt_number : evt_number/I **Entries : 2000 : Total Size= 8597 bytes File Size = 3013 **Baskets : 1 : Basket Size= 32000 bytes Compression= 2.69 *............................................................................**Br 2 :cpu_packet_time : time/I **Entries : 2000 : Total Size= 8567 bytes File Size = 460 **Baskets : 1 : Basket Size= 32000 bytes Compression= 17.58 *............................................................................**Br 3 :cpu_packet_pkt_type : pkt_type/s **Entries : 2000 : Total Size= 4583 bytes File Size = 142 **Baskets : 1 : Basket Size= 32000 bytes Compression= 28.80 *............................................................................**Br 4 :cpu_packet_datalength : datalength/i **Entries : 2000 : Total Size= 8597 bytes File Size = 169 **Baskets : 1 : Basket Size= 32000 bytes Compression= 47.88 *............................................................................**Br 5 :cpu_packet_crc : crc/i **Entries : 2000 : Total Size= 8562 bytes File Size = 8085 **Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 *............................................................................**Br 6 :clkb_event_pkt_number : pkt_number/i **Entries : 2000 : Total Size= 8597 bytes File Size = 167 **Baskets : 1 : Basket Size= 32000 bytes Compression= 48.46 *............................................................................**Br 7 :clkb_event_event_number : event_number/i **Entries : 2000 : Total Size= 8607 bytes File Size = 2924 **Baskets : 1 : Basket Size= 32000 bytes Compression= 2.77 *............................................................................**Br 8 :clkb_event_trigger_time : clkb_trigger_time/i **Entries : 2000 : Total Size= 8622 bytes File Size = 7352 **Baskets : 1 : Basket Size= 32000 bytes Compression= 1.10 *............................................................................**Br 9 :clkb_event_gps_data : gps_data[]/b **Entries : 2000 : Total Size= 2585 bytes File Size = 128 **Baskets : 1 : Basket Size= 32000 bytes Compression= 16.33 *............................................................................*

Br 10 :clkb_event_live_time : live_time/i **Entries : 2000 : Total Size= 8592 bytes File Size = 2581 **Baskets : 1 : Basket Size= 32000 bytes Compression= 3.13 *............................................................................**Br 11 :clkb_event_dead_time : dead_time[3]/b **Entries : 2000 : Total Size= 6592 bytes File Size = 2059 **Baskets : 1 : Basket Size= 32000 bytes Compression= 2.96

*Br 12 :clkb_event_status_register : status_register/s **Entries : 2000 : Total Size= 4618 bytes File Size = 150 **Baskets : 1 : Basket Size= 32000 bytes Compression= 27.31 *............................................................................**Br 13 :clkb_event_crc : clkb_crc/i **Entries : 2000 : Total Size= 8577 bytes File Size = 8085 **Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 Br 14 :ccb_event_msg_type : msg_type/b **Entries : 2000 : Total Size= 2579 bytes File Size = 127 **Baskets : 1 : Basket Size= 32000 bytes Compression= 16.45 **.......................................................................**Br 15 :ccb_event_device_id : device_id/b **Entries : 2000 : Total Size= 2584 bytes File Size = 128 **Baskets : 1 : Basket Size= 32000 bytes Compression= 16.33 **............................................................................**Br 16 :ccb_event_trigger_time : ccb_trigger_time/i **Entries : 2000 : Total Size= 8617 bytes File Size = 7337 **Baskets : 1 : Basket Size= 32000 bytes Compression= 1.10 **............................................................................**Br 17 :ccb_event_L2_trigger_counter : L2_trigger_counter/i

Entries : 2000 : Total Size= 8635 bytes File Size = 2934 *

*............................................................................*

Page 6: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 6

The ROOT Data from Etot (televent)............................................................................*

Br 22 :gain : gain[1][1][2304]/s **Entries : 2000 : Total Size= 19904040 bytes File Size = 77072 **Baskets : 334 : Basket Size= 32000 bytes Compression= 258.16 **............................................................................**Br 23 :pc_threshold : pc_threshold[1][1][36]/s **Entries : 2000 : Total Size= 272933 bytes File Size = 1213 **Baskets : 5 : Basket Size= 32000 bytes Compression= 224.58 **............................................................................**Br 24 :ki_threshold : ki_threshold[1][1][36]/s **Entries : 2000 : Total Size= 272933 bytes File Size = 1207 **Baskets : 5 : Basket Size= 32000 bytes Compression= 225.70 **............................................................................**Br 25 :frame_header : frame_header[1][1][34]/b **Entries : 2000 : Total Size= 132765 bytes File Size = 644 **Baskets : 3 : Basket Size= 32000 bytes Compression= 205.36 **............................................................................*Br 26 :photon_count_data : photon_count_data[1][1][128][2304]/b **Entries : 2000 : Total Size= 654040370 bytes File Size = 141544812 **Baskets : 2000 : Basket Size= 32000 bytes Compression= 4.62 **............................................................................**Br 27 :ki_data : ki_data[1][1][128][288]/b **Entries : 2000 : Total Size= 137924328 bytes File Size = 713607 **Baskets : 2000 : Basket Size= 32000 bytes Compression= 193.22 **............................................................................*

*Baskets : 1 : Basket Size= 32000 bytes Compression= 2.76 **............................................................................**Br 18 :ccb_event_crc : ccb_crc/i **Entries : 2000 : Total Size= 8572 bytes File Size = 8084 **Baskets : 1 : Basket Size= 32000 bytes Compression= 1.00 **Br 19 :pdm_event_event_header : event_header[36]/i **Entries : 2000 : Total Size= 577470 bytes File Size = 2504 **Baskets : 10 : Basket Size= 32000 bytes Compression= 230.40 **............................................................................**Br 20 :pdm_event_event_summary : event_summary[216]/i **Entries : 2000 : Total Size= 3494730 bytes File Size = 318037 **Baskets : 56 : Basket Size= 32000 bytes Compression= 10.98 **............................................................................**Br 21 :pdm_event_Errormap : Errormap[17]/B **Entries : 2000 : Total Size= 66676 bytes File Size = 390 **Baskets : 2 : Basket Size= 32000 bytes Compression= 169.69 **............................................................................**

Page 7: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 7

Packet time distribution

UTC time since 1970 January 1st 00:00:00

0:03 08:235:364:13 7:001:26 2:50UTC Times:

Helicopter

Page 8: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 8

Packet number

Not very usefull, several packets could have the same number

Page 9: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 9

Trigger time uniformity ?

S-Curve flat , probably OK, why peak on cputrigger

Why isThere thisBump inCpu trigger ?

Also smaller bumpIn acquisition

Unit inMicrosecond ?

Page 10: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 10

What is the exact definition ofAn event-life time,Can we understand why it is differentFor the various types of runs ?

Page 11: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 11

What is the definitionOf the dead time.

Why this two structure

How it intervene in the flux calculation ?

Page 12: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 12

CPU time vs CLKB time

• CPU time provides the CPU time in • UTC second !

• Clkb time unit is in what ?

• Clkb time is reset ? When ?

Page 13: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 13

ASIC Threshold vs CPU time

Page 14: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 14

ASIC Threshold vs Clkb time

Page 15: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 15

ASIC gain vs CPU time

Page 16: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 16

Photon count data histograms

Acquisition seams to be sensitive to high signal above count 170

Which so differents ?

counts

Page 17: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 17

PC data vs ASIC thresholds

Page 18: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 18

KI Data

KI see high signals on acquisition mode

I thought it wasSwitched off

Page 19: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 19

Correlation PC-KI data

KI data vs PC data

Use these plots to « trigger » on interesting GTU

What is wrong what is correct ?

Page 20: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 20

Quick analysis of the tree in a ROOT macro

Used in the plots used previously

Page 21: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 21

Data structure for a more refined analysis

See next

Page 22: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 22

Data structure in memory to get the data from the tree

To retrieve info like in standalone-event-dump Claudio code

struct cpu_packet packet_;struct payload_full_event payloadfullevent_;struct ccb_event ccbevent_;struct clkb_event clkbevent_;struct pdm_event pdmevent_;

UShort_t gain_[MAXCCBCOUNT][MAXPDMCOUNT][2304];UShort_t pc_threshold_[MAXCCBCOUNT][MAXPDMCOUNT][36];UShort_t ki_threshold_[MAXCCBCOUNT][MAXPDMCOUNT][36];UShort_t frame_header_[MAXCCBCOUNT][MAXPDMCOUNT][34];

To read tevent tree (one GTU per tree entry)UChar_t dataphys_[MAXCCBCOUNT][MAXPDMCOUNT][MAXPDMPIXNUMX][MAXPDMPIXNUMY];UChar_t ki_dataphys_[MAXCCBCOUNT][MAXPDMCOUNT][MAXKICOUNT];To read televent tree ( one packet per tree entry)

UChar_t datael_[MAXCCBCOUNT][MAXPDMCOUNT][MAXGTU][MAXPDMPIXNUMX*MAXPDMPIXNUMY];UChar_t ki_datael_[MAXCCBCOUNT][MAXPDMCOUNT][MAXGTU][MAXKICOUNT];

Page 23: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 23

Decoding run/event variables

Page 24: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 24

Decoding the data

Page 25: Understanding  the data - a first  off-line  look

EUSO-BALLOON Analysis Meeting, October 2-3 2014 25

Few PDM images (GTU snapshot) Need a software trigger