Behaviour of `i3_to_json.py` - Githubissues

icecube / skywriter

Upstream Tools for SkyDriver & the Skymap Scanner

MIT License

0 stars 0 forks source link

Behaviour of `i3_to_json.py` #5

Closed mlincett closed 1 year ago

mlincett commented 1 year ago

The current behaviour of i3_to_json.py is confusing:

https://github.com/icecube/skywriter/blob/7da71b341908ffe8e9eea0c98cb828286e70d444/skywriter/i3_to_json.py#L161-L185

If I add a "Dump" module before alertify, I get the first logging from the alertify function after the dump of frame number 4, that shows as I3Frame (DAQ). Yet if I print frame.Stop inside alertify it appears as Physics (?!)
If I add a print(frame) before alertify, nothing is printed before the first call to alertify.

mlincett commented 1 year ago

@tianluyuan clarified that the trigger splitter module (required to get SplitUncleanedInIcePulses) creates a new P-frame, which is then processed by alertify, hence the original P-frame is skipped (and all recos are lost).

Will open a new issue about how to preserve L2 reco data.