search

SNEWS2 / snewpdag

SNEWS2 alert calculations
BSD 3-Clause "New" or "Revised" License
2 stars 13 forks source link

Dts plugin development #58

Closed dallaval5u closed 2 years ago

dallaval5u commented 2 years ago

  1. Created plugin for the dts calculation in order to have enough output to feed the DiffPointing calculation. It needs as input a data['neutrino_time'] field, which can be generated using the DetectorTime plugin. Following the suggestions, I tried to make it this time as easy as possible, using also a new specific git branch.

  2. For now just outputting dts, t1 and t2. So far, it is taking detectors names from data[gen][neutrino_times]. In the future, it should read everything (uncertainties, names, ecc.) using the DetectorDB method.

  3. I am still unsure about how the data[history] field when combining three or more nodes should look like. So far, it (the history) looks a bit messy (following history output example comes after taking dts from JUNO, SK and KM3):

((((('Control', 'test_arr_time', 'test_offset_time', 'test_det_time_JUNO'), ('Control', 'test_arr_time', 'test_offset_time', 'test_det_time_SK')), 'test_nutime_extraction'), ('Control', 'test_arr_time', 'test_offset_time', 'test_det_time_SK'), ('Control', 'test_arr_time', 'test_offset_time', 'test_det_time_KM3')), 'test_nutime_extraction')

Please to share with me your thoughts, Sincerely, Riccardo

tsengj10 commented 2 years ago

If there are 3 or more histories (h1, h2, and h3) being combined by one module, then they should be listed in the tuple at the same level, i.e., (h1, h2, h3).