Full Event_Followup¶
- Release Notes
- main
- June 18, 2024 don la dieu (nega at icecube.umd.edu)
- Feb. 20, 2024 don la dieu (nega at icecube.umd.edu)
- Dec. 14, 2023 don la dieu (nega at icecube.umd.edu)
- Sep. 28, 2023 don la dieu (nega at icecube.umd.edu)
- June 22, 2023 don la dieu (nega at icecube.umd.edu)
- Jul. 27, 2022 don la dieu (nega AT icecube.umd.edu)
- Dec. 20, 2021 E. Blaufuss (blaufuss AT umd edu)
- Dec. 20, 2019 Alex Olivas (aolivas@umd.edu)
- June 12, 2018 Erik Blaufuss (blafufuss@umd.edu)
- Mar 23, 2017 Erik Blaufuss (blaufuss@umd.edu)
- April 20, 2015 Meike de With (meike.de.with@desy.de)
- April 8, 2015 Meike de With (meike.de.with@desy.de)
- Code Review for Full_Event_Followup
Overview¶
The Full Event_Followup roject provides reader and writer modules to convert single frames into messages suitable for fast followup transmission via iridium (RUDICS) or I3Live in general. A writer module will work on P-frames, package them with all their dependent frames (usually GCDQ) and send the result to a callback function. Callbacks for conversion to JSON suitable for I3Live are provided. The result can be stored in text files or directly in the original frame as an I3String. The string, in turn will be read by PnF’s onlinewriter on the fpmaster machine and transmitted to I3Live. All RUDICS/SPADE/email transmission of messages is handled by i3Live.
A reader module (icetray driving module) is provided to decode the JSON blob into a frame packet which can then be used for further processing in the North.
The module is agnostic to the input data and will serialize the whole frame including all GCD information by default. It is meant for HESE event follow-up work, but can be used for any channel with low rates.
A Keys argument can be used to limit the number of frame objects transmitted. When transmitting GCD information, this project should be used with a GCD diff/compression scheme in order to only send differences to a baseline GCD (these should be small compared to the usual GCD file size of >100MB).