Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rechunk retrospective channel routing data #119

Closed
jpolchlo opened this issue Dec 22, 2022 · 3 comments · Fixed by #122
Closed

Rechunk retrospective channel routing data #119

jpolchlo opened this issue Dec 22, 2022 · 3 comments · Fixed by #122
Assignees

Comments

@jpolchlo
Copy link
Collaborator

jpolchlo commented Dec 22, 2022

As we have learned, the retrospective NWM data are stored in a Zarr file in time-major format—that is, it is chunked so that different time slices' data are spatially coherent in storage. We've learned that this ordering of data makes queries on individual river reaches more time-consuming, and I've recently had some issues where the order of operations can result in some very crashy notebooks.

This issue, then, covers the creation of a rechunked version of the full channel routing dataset.

Connects #104
Closes #26

@jpolchlo jpolchlo self-assigned this Dec 22, 2022
@jpolchlo
Copy link
Collaborator Author

@rajadain @vlulla @elizawallace I'm assuming that there is a task in the proposal that associates with this work item? I can't find one, though, and I'd like to connect this issue to that one. Any ideas? Or did we not have an entry in the proposal for producing a rechunked retro dataset?

@jpolchlo
Copy link
Collaborator Author

We had deferred this task in favor of #104, but it sounds like this should be somewhat quick to do, and if that assessment holds up, then we're probably best to just do this task and retrospectively figure out how much it cost.

@elizawallace
Copy link

Need to create cost estimate for the rechunking.

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 a pull request may close this issue.

2 participants