Add GPU zarr decode path and runtime packaging#672
Closed
jder wants to merge 4 commits into
Closed
Conversation
oa-jder-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 8, 2026 20:01
d3b2497 to
c79628e
Compare
oa-jder-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
2 times, most recently
from
April 8, 2026 21:07
8d5507c to
cf0da5f
Compare
oa-jder-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 8, 2026 21:07
c79628e to
6a988d6
Compare
fomo-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
from
April 13, 2026 15:22
cf0da5f to
4e86aba
Compare
fomo-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 13, 2026 15:22
6a988d6 to
48817fb
Compare
fomo-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
from
April 13, 2026 16:24
4e86aba to
62c9a2f
Compare
fomo-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 13, 2026 16:24
48817fb to
4ca8250
Compare
fomo-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
from
April 15, 2026 20:42
62c9a2f to
2ed6626
Compare
fomo-bot
force-pushed
the
llc-stack-04-llc-training
branch
2 times, most recently
from
April 15, 2026 21:12
088d66e to
bdd0521
Compare
fomo-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
from
April 15, 2026 21:12
2ed6626 to
46484bc
Compare
fomo-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 21, 2026 18:11
bdd0521 to
3745683
Compare
fomo-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
2 times, most recently
from
April 22, 2026 19:42
48f32bd to
6fab0dc
Compare
fomo-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 22, 2026 19:42
3745683 to
58589da
Compare
fomo-bot
force-pushed
the
llc-stack-05-gpu-zarr-decode
branch
from
April 29, 2026 18:19
6fab0dc to
b1a9a15
Compare
fomo-bot
force-pushed
the
llc-stack-04-llc-training
branch
from
April 29, 2026 18:19
58589da to
a7659e1
Compare
This was referenced Jul 10, 2026
Member
Author
|
This is fragile and requires us to maintain forks of various libraries, so closing for now until we've shown that #800 is insufficient. (At which point we might add the GPU-side decode into that instead of via xarray) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is PR 5 in the LLC stack, based on #671.
It combines the guarded GPU zarr decode runtime path with the dependency, container, and smoke-test updates needed to make that path reproducible. The PR includes GPU-aware xarray/zarr opening, tensor materialization changes, the pinned zarr/xarray/kvikio/nvcomp stack, and container smoke coverage.
Why
The runtime path and the packaging changes are tightly coupled: the GPU decode code is only useful if reviewers can see the exact dependency and container assumptions it requires. Keeping them together makes the rollout boundary clearer.
Notes
This remains a draft stacked PR.