Skip to content

A/B: BLEND_HANDLING = uberseg vs noisefill — do the FLAGS=2 B-modes go away? #814

Description

@cailmdaley

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.

Before running: under uberseg, flagged pixels get zero weight but are not noise-filled (ngmix.py:1647–1665), so this A/B currently also switches off the defect fill. Keep noise-filling flag≠0 / weight==0 pixels under uberseg so the two arms differ only in neighbour handling.

Activity

  1. changed the title [-]A/B: uberseg vs noisefill — does UberSeg remove the FLAGS=2 B-modes?[/-] [+]A/B: `BLEND_HANDLING = uberseg` vs `noisefill` — do the FLAGS=2 B-modes go away?[/+] on Sep 17, 2026
  2. removed this from the First run on data (Nibi) milestone on Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions