ML4GW / ML4GW/aframe

Validate on MDC

Open
#476 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

merger-time
Dominant language
Python
Stars
18
Forks
28
Avg merge
2d 2h
Merged PRs (30d)
7

Description

Run the full pipeline with merger time regression enabled on the Mock Data Challenge dataset and verify that recovered merger time residuals are within acceptable bounds.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the full-pipeline entry point, the merger-time regression configuration, and the Mock Data Challenge dataset setup. Run the pipeline with regression enabled, then compare recovered merger-time residuals with the project's defined acceptable bounds; the issue is done when those bounds and the validation procedure are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.