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.