Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
L
lalsuite
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 109
    • Issues 109
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 28
    • Merge Requests 28
  • 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
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • lalsuite
  • Merge Requests
  • !1241

Closed
Opened Feb 20, 2020 by ABHIRUP GHOSH@abhirup.ghoshContributor2 of 4 tasks completed2/4 tasks
  • Report abuse
Report abuse

Porting FTA infrastructure to master

  • Overview 6
  • Commits 27
  • Pipelines 7
  • Changes 24

Description

The testing_gr_FTA branch was set up to port code (previously reviewed and existing on the old lalinference_o2 branch: https://git.ligo.org/noah.sennett/lalsuite/tree/testing_gr_fd_infrastructure) related to the parameterised test of general relativity using the flexible theory agnostic (FTA) approach. The results produced by the old code were reviewed and part of several past testing GR collaboration publications, including the O2 TGR catalog paper.

API Changes and Justification

Backwards Compatible Changes

  • This change introduces no API changes
  • This change adds new API calls

Backwards Incompatible Changes

  • This change modifies an existing API
  • This change removes an existing API

If any of the Backwards Incompatible check boxes are ticked please provide a justification why this change is necessary and why it needs to be done in a backwards incompatible way.

Review Status

The review wiki for the ported code is here: https://git.ligo.org/noah.sennett/lalsuite/-/wikis/home It involved:

  1. a line-by-line code review
  2. waveform checks as was done in the review of the old code
  3. reproducing PE results from the old code The reviewers have now signed off the code: https://git.ligo.org/noah.sennett/lalsuite/-/wikis/home#reviewers-statement and it has been used to produce results for 12m and 14bv

Note: For the purpose of producing results for the upcoming papers, this branch was merged with the SEOBNRv4HM_ROM branch, and consists of several commits belonging to that branch [commits: 84d3ac33 to 75459592 (consecutive and all authored by Roberto Cotesta)]. We want advice about how best to proceed.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: lscsoft/lalsuite!1241
Source branch: testing_gr_FTA