CosmoStat / CosmoStat/shapepipe
A/B: `BLEND_HANDLING = uberseg` vs `noisefill` — do the FLAGS=2 B-modes go away?
@fabianhervaspeters is already working on this.
Since Jul 13, 2026.
- Dominant language
- Python
- Stars
- 18
- Forks
- 14
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 10
Description
noisefill (the default) zeroes and noise-fills only pixels flagged in the mask/weight; light from neighbouring detections stays in the stamp. uberseg masks pixels the segmentation map assigns to a neighbour, plus sky pixels nearer to a neighbour than to the object; it needs the segmentation stamp from vignetmaker run 3, which should only run when uberseg is on.
Fabian's hypothesis: the B-modes seen in FLAGS=2 (deblended) objects come from unremoved neighbour light.
Test: both settings on the blended image sims (m-bias, shape noise) and on a data patch (FLAGS=2 subset B-modes). A blended-sims uberseg run from July exists, uninspected.
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.
Assessment
This issue has not been assessed yet.