Skip to content

fix: let customFrag own NaN discard decisions#72

Open
Shane98c wants to merge 1 commit into
mainfrom
customfrag-owns-discard
Open

fix: let customFrag own NaN discard decisions#72
Shane98c wants to merge 1 commit into
mainfrom
customfrag-owns-discard

Conversation

@Shane98c

Copy link
Copy Markdown
Member

Closes #71.

In multi-band mode the generated fragment shader injected an any-band-NaN discard before customFrag ran, so aggregations over partial coverage (e.g. multi-model median/mean with gaps) could only render the intersection of all bands, never the union.

Now when a customFrag is supplied it owns the discard decision — every band value is already in scope (NaN included for missing/fill pixels), so the shader chooses how to handle missing bands. Default (no-customFrag) single- and multi-band paths keep their existing discards.

Breaking: existing customFrag shaders that relied on the implicit NaN discard must now add their own discard. README examples updated to show the pattern.

@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
zarr-layer Ready Ready Preview, Comment Jun 23, 2026 11:32pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

multi-band shader discards on any-NaN before customFrag runs

1 participant