New LIGO-Virgo-KAGRA low-latency pipeline MLy appears as undefined in GCN Notices

[narnaud1974]

Current behavior

The LVK has recently added in production a new low-latency pipeline called MLy that has started uploading (automated) GCN notices like https://gcn.gsfc.nasa.gov/notices_l/S241206di.lvc or https://gcn.gsfc.nasa.gov/notices_l/S241211hi.lvc (more recent). The issue is that, in such notices, the pipeline is reported as PIPELINE_TYPE: 0 = undefined. While we think we send the pipeline name information properly:

<Param name="Pipeline" value="MLy" ucd="meta.code" dataType="string">
   <Description>Low-latency data analysis pipeline</Description>
</Param>

Do you need to add that pipeline in some list of known pipelines on the GCN side, or is there something that we should fix on our end?

Thanks in advance.

Expected behavior

MLy should appear on the line PIPELINE_TYPE: (...) in notices.

Steps to reproduce

All MLy notices seem to have the same problem so far.

Environment

[jracusin]

@narnaud1974 Thanks for submitting this issue. This is on the GCN Classic side. There's a conversion between these pipeline strings and numbers. I'll let you know when we've added MLy.

[jracusin]

@narnaud1974 We've implemented these changes and are testing them on the playground, but not yet in production. We can wait until we get a message on playground with the MLy pipeline, as that seems to be once every day or so. But if you could push one, that would be helpful.

[pshawhan]

Hi @jracusin (and @narnaud1974), there was an MLy low-significance alert in the past hour: S250111bh at 18:43:04 UTC.

[narnaud1974]

@jracusin : are you done with your tests? Is MLy now in your list of pipelines? If the answer is yes, could you tell us what information the LVK should provide GCN ahead of time if / next time we add a new low-latency pipeline. Thanks.

[jracusin]

@narnaud1974 @pshawhan Sorry for the delay. I've implemented the change on the production system. We should now be able to correctly process alerts from the MLy pipeline.

If you add pipelines in the future, please just let us know in advance, so we can modify the GCN Classic code. All we need is the name of the new pipeline.