Project

General

Profile

Actions

Data analysis » History » Revision 20

« Previous | Revision 20/25 (diff) | Next »
Zhiwen Zhao, 03/03/2021 07:08 PM


Data analysis

general

"How to read FADC250 scalers" https://logbooks.jlab.org/entry/3808745

"scaler file of run 158" at large angle https://logbooks.jlab.org/entry/3808730

large angle run 160 analysis https://logbooks.jlab.org/entry/3853160

small angle run 302 data analysis https://logbooks.jlab.org/entry/3853129

small angle run 302 data taking https://logbooks.jlab.org/entry/3820300 https://logbooks.jlab.org/entry/3820256 https://logbooks.jlab.org/entry/3820280 https://logbooks.jlab.org/entry/3820241

SPE https://logbooks.jlab.org/entry/3807172

typical event https://logbooks.jlab.org/files/2020/09/3853122/mapmt_sums_event_78237.png

C4F8 gas change https://logbooks.jlab.org/entry/3848116

general log search with keyword "solid" to include content in hallC log https://logbooks.jlab.org/search/site/SoLID?f%5B0%5D=im_field_logbook%3A81

solid log search for year 2020 [https://logbooks.jlab.org/entries?start_date=2020-01-01%2000%3A00&end_date=2020-12-29%2000%3A00&logbooks%5B0%5D=560&search_str=&group_by=SHIFT&listing_format=table&entries_per_page=100&form_build_id=form-UCte5bWEoOS6iR2jTkFiL7v_38wBt4MQi2-5eyW1MYI&form_token=jrBS9-8RyHRLvMk-YIxHU2vWdIFbgfwWl4KKZ4O0K2o&form_id=elog_form_advanced_filters&op=Submit]

file

raw data /cache/halla/solid/subsystem/lgc/testrun2020/

analysis file location /work/halla/solid/cc_pro/beamtest

run 160: production run, 30uA on PolHe3 target, fadc mode 1 single every 4ns, large angle, CO2

event by event output have the entries as follows
ec_peak,ec_pos,ec_nhits,ec_sum,sc_peak,sc_pos,sc_nhits,sc_sum,Cer11_1_peak,Cer11_2_peak,Cer11_3_peak,Cer11_4_peak,Cer11_5_peak,......,,Cer11_2_pos,Cer11_3_pos,Cer11_4_pos,Cer11_5_pos,.......,ec_ch,sc_ch

........................................................................
run160_0_all.csv (entries 990243)

id: event id
ec_peak: the peak height of the channel with max peak height, but about 90% of the events have only one channel fired, so it is close to the sum.
ec_pos: the peak sample number in the unit of 4ns
ec_nhits: number of hits
ec_sum: sum of all channels of peak height
sc_* : similar things for SC2 which is the plane behind Cerenkov tube
Cer11_1_peak: peak height of Cer11 quad1
Cer11_5_peak: peak height of Cer11 sum
Cer11_1_pos: the peak sample number in the unit of 4ns of Cer11 quad1
Cer11_5_pos: the peak sample number in the unit of 4ns of Cer11 sum
ec_ch: the channel with max peak height
sc_ch: the channel with max peak height

Cer pos is relative to ec_pos, ec_pos and sc_pos are relative to trigger.

........................................................................
run160_1_all.csv (entries 12085327)

all entries have timing cut

Cerenkov peak is actually number of p.e. and all other entries are just like run160_0_all.csv
........................................................................

Updated by Zhiwen Zhao over 4 years ago · 20 revisions