Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#972 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
data, machine-learning

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Python
Estrellas
18
Forks
14
Merge medio
4 d 14 h
PR fusionados (30 d)
44

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CosmoStat/shapepipe

Todos los issues de CosmoStat/shapepipe

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.