Request from Reed Essick on January 20, 2017 (from https://bugs.ligo.org/redmine/issues/5043)

In all our publications and internal documents, the pipeline is referred to as "oLIB." Therefore, it is the name "oLIB" that should be associated with significance estimates and be allowed to create events in GraceDb. The name "LIB" commonly refers to the parameter estimation follow-up done for all burst events. While oLIB uses the LIB pipeline, they are nonetheless separate concepts. LIB PE results do not contain significance estimates in the same way that LALInference PE results do not.

To minimize/mitigate possible confusion (which appears to be common), we propose changing the pipeline name in GraceDb. However, this will have many repercussions which we should carefully consider. An incomplete list includes

• the need to update all historical events in GraceDb to follow the new nomenclature
• the need to update all LVAlert nodes so they follow the new nomenclature
• the need to update all follow-up processes so they listen to the new LVAlert nodes

This change will almost certainly have to wait until a break between observing runs.

Request from Qi Chu on July 9, 2018 (from https://bugs.ligo.org/redmine/issues/6191)

Dear Tanner,

I would like to request the name for the SPIIR pipeline on the gracedb to be changed to "spiir" in order to remove the possible confusion that triggers from this pipeline are dependent on the that of gstlal pipeline. The connection with the gstlal pipeline is that the code of this pipeline is packed in the gstlal dev packages.

Cheers!