MCCD on a small DR6 area after the PSFEx production run (proposal)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- python
- 领域
- data, machine-learning
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.inipath). - 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
- 主要语言
- Python
- 星标
- 18
- 派生
- 14
- 平均合并
- 4 天 14 小时
- 30 天内合并 PR
- 44
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CosmoStat/shapepipe 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
In-allocation runs: whole-second mtimes on Lustre products_dir trigger Snakemake clock-skew failures未关闭
难度 4/5 3-5 天 新手友好度 45/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 54/100
维护者通常 1 天内回复
查看 CosmoStat/shapepipe 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
btclib-org/btclib-ecc#404 ·
-
changelog investigate
难度 1/5 1 小时以内 新手友好度 78/100
ramnes/notion-sdk-py#430 ·
-
bug good first issue
难度 1/5 1 小时以内 新手友好度 91/100
hyeonjoong/debussy#56 ·
-
documentation
难度 2/5 1-3 小时 新手友好度 68/100
Lagrunge82/yandex-mail-mcp#43 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
liberation-data/drivine-python#252 · 1 条评论 ·
维护者通常 1 天内回复