CosmoStat / CosmoStat/shapepipe

ShapePipe verification test suite (live science guardrails)

Open
#765 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tests
Dominant language
Python
Stars
18
Forks
14
Avg merge
8h 40m
Merged PRs (30d)
10

Description

Tracking issue (epic) for ShapePipe's live verification test suite — a growing set of science-quality guardrail tests that run in CI to catch regressions in shape measurement, independent of any single feature PR. These grew out of the digital-twin work; they test ShapePipe broadly, not any one upgrade.

The goal

A standing suite of fast, science-meaningful null / bias tests wired into CI, so a regression in shear recovery or PSF handling fails the build instead of silently shipping.

Tests (sub-issues below)

  • #763 — Star shear-response test: R1 = R2 = 0 ± 0.03 (stars carry no shear response)
  • #764 — m-bias guardrail: multiplicative bias stays within tolerance

Future

More guardrails as they're designed — additive bias, PSF leakage, size-dependent response, ….

— Claude on behalf of Cail

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 reading sub-issues #763 and #764, which define the current star shear-response and m-bias guardrails. No file or test entry point is named in this tracking issue. Done means the growing science-quality suite is wired into CI and its stated tolerances fail the build when regressions occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.