External events appearing in superevent neighbors `gw_events`
First noted by Deep Chatterjee, within the superevent_neighbors
field external events can appear as gw events. This can potentially disrupt the logic used in the superevent manager.
Summary of https://gracedb-test.ligo.org/api/superevents/MS220920p/ , where M304272
appears as an external event in the superevent (and not included in gw_events
) but under superevent_neighbors
appears as a gw_event
:
{
"superevent_id": "MS220920p",
"gw_events": [
"M304283",
"M304282",
"M304281",
"M304280",
"M304279",
"M304278",
"M304277",
"M304276",
"M304275",
"M304274",
"M304273",
"M304271",
"M304270",
"M304269",
"M304268",
"M304267"
],
"em_events": [
"M304272"
],
"preferred_event_data": {
"superevent": "MS220920p",
"superevent_neighbours": {
"MS220920p": {
"superevent_id": "MS220920p",
"gw_events": [
"M304283",
"M304282",
"M304281",
"M304280",
"M304279",
"M304278",
"M304277",
"M304276",
"M304275",
"M304274",
"M304273",
"M304272",
"M304271",
"M304270",
"M304269",
"M304268",
"M304267"
]
}
}
}