Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
G
gracedb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 99
    • Issues 99
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • gracedb
  • Issues
  • #18

Closed
Open
Opened Aug 17, 2018 by Tanner Prestegard@tanner.prestegardMaintainer

Change pipeline names for LIB and gstlal-spiir

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!

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Readiness for second OPA test
Milestone
Readiness for second OPA test (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: lscsoft/gracedb#18