Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Emit the instrument flags as a healsparse defect map for the survey footprint

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data

Research direction

Start by reading the coverage map builder from #797 and how it walks exposure headers, then inspect the instrument flag files consumed by ShapePipe. Trace how the healsparse mask inputs from #845 and #847 are represented; done means emitting per-exposure footprint ∧ flags maps at the mask nside and combining them across epochs like #797.

Written by the indexing model from the issue text.

Description

The survey footprint is being built as a positive coverage map minus the healsparse mask bits (#845, #847). One masking input never leaves the pixel domain: the instrument flag images (bad columns, saturated pixels, bleed trails). The coverage map of #797 is built from CCD corner WCS in the headers, so it cannot subtract them — the footprint would silently include defective pixels.

The lost area is percent-level, but it carries exactly the complex small-scale geometry (thin bad columns, bleed trails) that an accurate window function needs.

Proposal: emit the instrument flags as a healsparse defect map — per exposure, footprint ∧ flags rasterized at the mask nside, then combined across epochs the same way #797 combines coverage. This is a natural extension of #797's map builder, which already walks the exposure headers; only ShapePipe reads these flag files, so the map has to come from our side.

— Claude on behalf of Cail

Dominant language
Python
Stars
18
Forks
14
Avg merge
8h 40m
Merged PRs (30d)
10

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.

More from CosmoStat/shapepipe

All issues in CosmoStat/shapepipe

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.