Weighted vs unweighted m-bias disagree in the latest image-sim runs
@martinkilbinger is already working on this.
Since Sep 8, 2026.
Assessment
This issue has not been assessed yet.
Description
Recent runs with the WCS fix give m consistent with zero, but weighted and unweighted estimates differ — unexpected given earlier tests where weights did not move the m-bias (see Fabian's comment in UNIONS-WL/MultiBand_ImSim#1: https://github.com/UNIONS-WL/MultiBand_ImSim/issues/1#issuecomment-5066465616). Understand the difference before the m-bias is called done. Related: uberseg (#776) is implemented but reportedly not enabled and made no difference on blended sims.
- Dominant language
- Python
- Stars
- 18
- Forks
- 14
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CosmoStat/shapepipe
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in CosmoStat/shapepipe
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·