You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've set up a gcn-kafka listener to pickup detected coincident icecube neutrino events to LVK alerts for the Gravitational Wave Treasure Map. I used the example json package and have noticed inconsistencies in the actual alerts being sent over this kafka stream that caused some inability to associate events to LVK alerts.
The ref_ID keyword in the example is actually ref_id in the alerts, which caused us to actually never associate the alerts to the events.
The format of the ref_id was never documented. We just assumed it would be the graceid for the event like it is in the example, but the actual alert ref_id is in the form of graceid_iter_alerttype like S230814r-2-Preliminary.
There is no reference keyword in the package that links to the gcn.notices.LVK.alert id.
In the coincident_events list, the spatial keywords are behind a "localization" dictionary, that isn't in the example.
We will update our listener to adapt to what is being sent over the kafka stream, yet request the example.json package also be updated to reflect what is being sent out over kafka.
Best,
-SW
The text was updated successfully, but these errors were encountered:
Corrects the example. Additionally, there are a few tweaks we need to make the example match the schema. These are not yet in production, but staged and ready to go. Once we get the PR accepted in gcn-schema and new example published, we will change our production alert sender and close/update this issue when live.
Just to be clear: example in PR matches what WILL be coming after new version is live.
I've set up a gcn-kafka listener to pickup detected coincident icecube neutrino events to LVK alerts for the Gravitational Wave Treasure Map. I used the example json package and have noticed inconsistencies in the actual alerts being sent over this kafka stream that caused some inability to associate events to LVK alerts.
The
ref_ID
keyword in the example is actuallyref_id
in the alerts, which caused us to actually never associate the alerts to the events.The format of the
ref_id
was never documented. We just assumed it would be the graceid for the event like it is in the example, but the actual alertref_id
is in the form ofgraceid_iter_alerttype
likeS230814r-2-Preliminary
.There is no
reference
keyword in the package that links to the gcn.notices.LVK.alert id.The link to the package $schema returns 404
In the
coincident_events
list, the spatial keywords are behind a"localization"
dictionary, that isn't in the example.We will update our listener to adapt to what is being sent over the kafka stream, yet request the example.json package also be updated to reflect what is being sent out over kafka.
Best,
-SW
The text was updated successfully, but these errors were encountered: