Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
Description
The lsst-dm/sample-avro-alert repository holds the Avro schema definitions for alert packets, and some Python utility code (in lsst.alert.packet) for loading those definitions. DM-24324 adds alert generation to the production pipeline, so these definitions are now ready to be used in the stack.
Before adding lsst.alert.packet to lsst_distrib, this repository should be renamed and moved to lsst/alert_packet.
fastavro is a third-party dependency of the Python utility code, and is necessary for using the Avro schemas. It should be added to lsst_thirdparty too, I think (but am not sure - is that the right destination? I'm still learning the basics).
Attachments
Issue Links
- blocks
-
DM-24324 Generate alert packets in the alert production pipeline
- Done
- is triggered by
-
DM-24500 Place lsst.alert.packet in lsst_distrib
- Done
- is triggering
-
DM-24758 Update conda environment with cleanups after third-party move
- Done
-
DM-24500 Place lsst.alert.packet in lsst_distrib
- Done
Usually if a package is called "alert_packets" we expect the python import to be lsst.alert.packets so there seems to be an inconsistency in the proposed naming at the moment.
Is there a fastavro conda-forge package?