Skip to content

GitLab

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

Closed
Open
Created Oct 29, 2018 by Vivien Raymond@vivienMaintainer

Bilby pipe

A pipeline for bilby, see https://git.ligo.org/Monash/bilby_pipe.

With:

  • Interface with gwcelery for automated launch of follow-ups.
  • Interface with GraceDB to (1) get information from detection pipeline, and (2) upload summary results. Potentially using the using the lalinference.io event’s class.
  • Condor submission, including access reserved queues for online follow-ups
  • Input .ini files and output samples files being convertible either direction, e.g. .ini files for TestingGR
  • Interface with BayesWave: settings/data treatment need to be identical. (We may just want to read in frame-files created by the PE code)
Assignee
Assign to
1.0.0
Milestone
1.0.0
Assign milestone
Time tracking
None
Due date
None