CosmoStat / CosmoStat/sp_validation

Galaxy selection: replace the IMAFLAGS_ISO == 0 cut with a MASK_r bit cut once ShapePipe consumes healsparse masks

Open
#318 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2
Forks
5
Avg merge
1d 14h
Merged PRs (30d)
19

Description

classification_galaxy_base keeps objects with IMAFLAGS_ISO == 0.
That column carried the tile-level ShapePipe mask (GSC star halos, spikes, Messier/NGC) and was the only place bright-star masking reached the galaxy sample.
After CosmoStat/shapepipe#847 ShapePipe no longer generates masks and tile detection runs without a flag image, so IMAFLAGS_ISO is absent from the final catalogue.
Instead, every UNIONS healsparse mask bit is queried per object and written as MASK_<band> columns (bit table: wiki).

Needed here: the galaxy cut becomes (MASK_r & BITS) == 0 with a configured bit set — the natural default is halos + star + manual + MaxiMask (bits 0, 1, 2, 3, 10), the same combination as the cumulative area table on the wiki page.
The instrument flags stay available per epoch through ngmix's epoch handling; nothing else in the selection changes.

Not urgent: only after #847 (and its base #852) merge and the first catalogues with MASK_<band> columns exist.

— Claude on behalf of Cail

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the galaxy-selection code containing classification_galaxy_base and inspect how the IMAFLAGS_ISO cut is configured and tested. Review the MASK_r bit mapping in the linked wiki and wait for #847/#852 and catalogues with MASK_ columns. Done means the selection uses the configured halos, star, manual, and MaxiMask bits while leaving other selection behavior unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.