S230630bq circular draft issues

For some reason, the initial circular draft generated for S230630bq listed the p-astro numbers from G414338, a spiir event, instead of the preferred event G414341, an mbta event. It may be worth noting that the GCN notices summary page listed the pipeline as undefined instead of MBTA. It's not clear if these two problems are related or not. I've opened a ticket with GCN about the issue on their page.

changed milestone to %GWCelery v2.1.4 Release

added to epic &11

Maybe related note is also the circular template from the June 27th event where the value in circular template was incorrect and had to be corrected. The value in the notice was correct in this case however. I'll CC @brandon.piotrzkowski since it might be something to do with ligo-followup-advocate.

One solution is to default to grabbing values from the VOEvent (not sure why we weren't already doing that): ligo-followup-advocate#106 (closed)

Okay the MR to fix this is here: ligo-followup-advocate!153 (merged)

Tagging @keita.kawabe so he knows the problem is understood now, thanks Brandon!

Also I noticed that S230630bq never had an update GCN notice for either the skymap or classifications, only for preliminary and initial. Note that the dashboard for creating an update circular explicitly states that it requires a notice before creating the circular or it will not work correctly: https://emfollow.ligo.caltech.edu/gwcelery/#create-update-gcn-circular

Brandon this problem happened for an initial circular, does that change anything?

No it doesn't change anything, this was broken for all types of circulars.

Okay ligo-followup-advocate!153 (merged) is merged so will close this issue.

@keita.kawabe can you make it a point in the future that update notices are sent prior to circulars? Maybe the procedures document needs to be updated?

@brandon.piotrzkowski, S230630bq Initial Notice was distributed over GCN Classic. Responders sent the Initial Circular after that. Cody was online and found that the Notice hasn't gone out on gcn kafka. That's what I remember. What are you proposing that the responders should have done differently? Or am I talking about something completely diffefent?

FYI responders are required to check that Intial Notice has been sent out prior to issuing Initial Circular. No Initial Notice -> gwcelery experts will be called. But that check is done by looking at the GCN Classic archive as that's the only public-facing repository on the gcn web page.

Sorry I realized @deep.chatterjee linked a different superevent that did have an update notice/circular. My bad. The response to S230630bq looks to me to have been fine.

I see, thanks for confirmtion, Brandon!

Just for the record, I note here that the same problem occurred again on S230707ai.

The initial circular draft generated for S230707ai listed the p-astro numbers from G415813, a SPIIR event, instead of the preferred event G415815, a MBTA event. GCN notices summary page (on SEQUENCE_NUM: 2 and 3) listed the pipeline as "undefined" instead of MBTA.

The fix for the circulars still needs a release in ligo-followup-advocate and then a release in gwcelery release to be deployed.

The GCN notices listing MBTA as undefined is likely a problem with GCN itself (recall MBTA changed its pipeline name recently so likely doesn't recognize the new value).

mentioned in issue #666

mentioned in merge request ligo-followup-advocate!153 (merged)

closed