======== Overview ======== It is designed to remove non-Neutrino oriented but has impulsive pulser event that can be identifiable by the reconstruction methods - Untagged calpulser: Interferometry (AraCorrelator) - Surface event: Interferometry and hit time (AraVertex) - Interferometry will be introduced at the event selection method All cuts are independant. Calculated analysis variables by Interferometry are also used to separate signal/background 3rd data cleaning is done by below command:: source ../setup.sh python3 arr_time_table_maker.py # calculates arrivaltime table by ray tracing python3 script_executor.py -k reco_ele_lite -s -r # performs vertex reconstruction based on AraCorrelator method python3 script_executor.py -k rpr -s -r # calculates Root Power Ratio for AraVertex based reconstruction python3 script_executor.py -k vertex -s -r # performs vertex reconstruction based on AraVertex method python3 script_executor.py -k qual_cut_3rd -s -r -b 1 -q 3 # performs 3rd data cleaning For the simulation side:: source ../setup.sh python3 sim_script_executor.py -k reco_ele -s -d # both signal and noise. finds c_max of all elevation angle python3 reco_ele_lite_merge_sim.py # both signal and noise. re-structure the vertex reconstruction results by chooing only one c_max python3 sim_script_executor.py -k rpr -s -d # both signal and noise python3 sim_script_executor.py -k vertex -s -d # both signal and noise python3 sim_script_executor.py -k qual_cut -s -d # both signal and noise It will use `filt_qual_cut_loader `_ class ============= Calpulser cut ============= Related doc. `DB2731 `_ This is done by `get_calpulser_surface_events `_ and `get_calpulser_cut `_ function User must run vertex reconstruction first by below command:: source ../setup.sh python3 arr_time_table_maker.py # calculates arrivaltime table by ray tracing python3 script_executor.py -k reco_ele_lite -s -r # performs vertex reconstruction based on AraCorrelator method python3 sim_script_executor.py -k reco_ele -s -d # both signal and noise. finds c_max of all elevation angle Due to ARA’s trigger algorithm, If DAQ has malfunction, Calpulser signal can have a unexpected timestamp value and will be mixed into RF triggered signal To remove untagged calibration signal, we reconstructed position of Calpulser signal by interferometry and use it by defining the cut region Any signal that reconstructed position is inside of Calpulser reco. region, it will be excluded from dataset .. _fig-cal_table: .. figure:: ../../figures/cal_table.png :align: center live time losses by calpulser cuts .. _fig-cal_hist: .. figure:: ../../figures/cal_hist.png :align: center knwon calpulser example ------------ A2 Calpulser ------------ From 2018, transmitter is switched to CP 5 string CP 5 mirror position on config 5 is gone on 2018 From 2020, Calpulser reco. results are spreaded out because string 1 is excluded by duplication By including 1st block into analysis, reco. results can be secured without string 1 1st block offset issue can be corrected by 1) excluding it from ZeroMean correction and 2) apply band-pass filter .. _fig-cal_hist2: .. figure:: ../../figures/cal_hist2.png :align: center A2 calpulser distribution .. _fig-cal_hist2: .. figure:: ../../figures/cal_hist3_11.png :align: center A2 calpulser reconstruction by including 1st block with band pass filter .. _fig-cal_hist3: .. figure:: ../../figures/cal_hist3.png :align: center A2 calpulser results .. _fig-cal_hist3_2: .. figure:: ../../figures/cal_hist3_2.png :align: center A2 calpulser distriution and cut results in elavation vs azimuth angle space ------------ A3 Calpulser ------------ From middle of 2019, transmitter is switched to CP 5 string On 2019, Due to loss of 2 strings (D1 : dead bit, D4: duplication), We losses azimuthal sensitivity. - two elevation/azimuth position for CP 6 - more wide distribution of CP 5 .. _fig-cal_hist4: .. figure:: ../../figures/cal_hist4.png :align: center A3 calpulser distribution .. _fig-cal_hist4: .. figure:: ../../figures/cal_hist4_1.png :align: center Expected A3 calpulser mirror position on 2019 data set .. _fig-cal_hist5: .. figure:: ../../figures/cal_hist5.png :align: center A3 calpulser results .. _fig-cal_hist5_1: .. figure:: ../../figures/cal_hist5_1.png :align: center A3 calpulser distriution and cut results in elavation vs azimuth angle space. Due to resolution of 1 degree, calpulser distribution in config7 is appeared to be outside of cut. =========== Surface cut =========== This is done by `get_calpulser_surface_events `_ function User must run 2 vertex reconstructions first by below command:: python3 arr_time_table_maker.py # calculates arrivaltime table by ray tracing python3 script_executor.py -k reco_ele_lite -s -r # performs vertex reconstruction based on AraCorrelator method python3 script_executor.py -k rpr -s -r # calculates Root Power Ratio for AraVertex based reconstruction python3 script_executor.py -k vertex -s -r # performs vertex reconstruction based on AraVertex method python3 sim_script_executor.py -k reco_ele -s -d # both signal and noise. finds c_max of all elevation angle python3 reco_ele_lite_merge_sim.py # both signal and noise. re-structure the vertex reconstruction results by chooing only one c_max python3 sim_script_executor.py -k rpr -s -d # both signal and noise python3 sim_script_executor.py -k vertex -s -d # both signal and noise ------------------------- AraCorrelator Surface cut ------------------------- This cut is set by reconstructed zenith (or elevation) angle and depth Any signal that reconstructed ele. angle is over 35 degree or depth is over 0 m, it will be excluded from dataset - Elevation angle 35 degree at the radius 300 m is close to 1) air/ice transition boundary and 2) beginning of shadow region - If reconstructed position is outside of 300 m, event is excluded by depth Zenith Cut: > 35 deg Z Cut: > 0 m (in A3, > -1.5 m) ------------------------- AraVertex Surface cut ------------------------- Reconstructed position is based on hit (arrival of ray) time identified by Root Power Ratio (RPR) value of each channel Any signal that reconstructed ele. angle is over 35 degree or depth is over 60 m, it will be excluded from dataset - RPR is calculated by partial region (25 ns) of WF. So, It is relatively free from noise interference than interferometry - Cons. is, it is not taking into account similarity between channels Zenith Cut: > 35 deg Z Cut: > 60 m .. _fig-sur_table: .. figure:: ../../figures/sur_table.png :align: center live time losses by 4 surface cuts .. _fig-sur_hist: .. figure:: ../../figures/sur_hist.png :align: center 4 surface cuts example .. _fig-sur_hist1: .. figure:: ../../figures/sur_hist1.png :align: center 4 surface cuts example in sequence