Open mlincett opened 1 year ago
Looking at i3_to_json.py it seems the current format is quite cluttered from realtime-related metadata.
I understand we chose to stick with the "standard" realtime JSON format to avoid reinventing the wheel, but I think the sky*
projects are now mature enough to dictate their own rules.
I suggest to:
skymap scanner
.i3_to_json
code and the handling of simulated dataskywriter
/ skymap scanner
.Sounds like a reasonable need to me. The way the event is compressed is my favorite part of the realtime format--not because it's better than an alternative, but because it's been standardized. I'm not really familiar with metadata
@tianluyuan may have some ideas
Sounds like a reasonable need to me. The way the event is compressed is my favorite part of the realtime format--not because it's better than an alternative, but because it's been standardized. I'm not really familiar with metadata
@tianluyuan may have some ideas
Definitely the I3Frame encoding would follow the same standard and possibly use the same IceTray code (it just needs to be factored into more atomic functions).
To me it's mostly a matter of removing unnecessary data from the "envelope".
Looking at the following:
It seems that all that is used by the scanner is the "frame packet" (list[I3Frame]
).
The information in the "envelope" was used to evaluate the alert passing criteria, but this is no longer the case for the Skymap Scanner.
In
skymist
, I am experimenting pydantic templates for the parsing of realtime messages.It could be nice to have some form of specification of the input data format of
skymap_scanner
to be be defined inskywriter
.Whether this should be based on
pydantic
or something else is TBD.