Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

MCCD on a small DR6 area after the PSFEx production run (proposal)

Offen
  • Stimmt etwas nicht?
#972 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
20/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
data, machine-learning

Rechercherichtung

Read #674 and inspect workflow/config/cfis/config_exp_mccd.ini after resolving its removed-rule reference. The proposal depends on #601, #630 and #402, and still leaves the patch size, location, runtime plan and comparison owner undecided. Done would mean running MCCD through the v2 workflow on the selected DR6 tiles and comparing the listed PSF residual, leakage, rho/tau and shear catalogue measures against PSFEx on identical objects.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Proposal, not a decision (UNIONS tomography call, 20 Oct): once the current PSFEx production run on DR6 is done, run MCCD on a small DR6 area through the v2 workflow and compare it with PSFEx on the same tiles. A larger MCCD run would be considered only after that.

Why: on the older catalogues, MCCD gives similar or slightly better PSF systematics, and the 11–12 arcmin B-mode bump improves after footprint matching. A provisional MCCD−PSFEx jackknife on a common footprint shows nothing above ~1.5σ. That is suggestive but not enough to switch the production PSF model. A matched test on DR6 data separates the PSF model from the footprint and selection differences that confound the old comparison.

What the test would be:

  • Area: a contiguous patch already run with PSFEx in v2 production, so the PSFEx side costs nothing extra. Size to be chosen so that rho/tau statistics and leakage are measurable, likely tens of tiles.
  • Run: the same v2 workflow and code commit, with only the PSF model changed (config_exp_mccd.ini path).
  • Compare: per-exposure PSF residuals, star-galaxy leakage, rho/tau statistics, and the shear catalogue on identical objects.

Prerequisite: the MCCD exposure chain has to run in the v2 workflow first. That is #674. Its known blockers are #601 (ModOpt), #630 (interp) and #402 (install), and workflow/config/cfis/config_exp_mccd.ini still references a removed rule.

Open questions: patch size and location; whether MCCD's cost per exposure changes the plan; who runs the comparison side (the cosmo_val / B-mode stack already used for the 2D comparison is the natural place).

Claude (Opus 5.5) on behalf of Cail

Vorherrschende Sprache
Python
Sterne
18
Forks
14
Ø Merge
4 T. 14 Std.
Gemergte PRs (30 T.)
44

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CosmoStat/shapepipe

Alle Issues in CosmoStat/shapepipe

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.