-
Notifications
You must be signed in to change notification settings - Fork 63
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
Liveocean #179
Liveocean #179
Conversation
It looks like there may be a problem with the structure of your PR. I encountered a |
2 similar comments
It looks like there may be a problem with the structure of your PR. I encountered a |
It looks like there may be a problem with the structure of your PR. I encountered a |
@rabernat and @cisaacstern, the pre-commit.ci failed, but because of other recipes, not my "liveocean" one, right? I also fixed a few of the issues with the pre-commit, and the formatting issues with some other recipes which were autofixed by:
I believe at least the liveocean recipe should be good to go! |
👋 @rsignell-usgs thanks for re-opening this. Re: pre-commit, yes this is long-running issue being tracked in #88, and which I plan to resolve soon. You are correct it doesn't affect this recipe. (@andersy005, I've had some recent ideas of how we'll handle this pre-commit issue, will follow up with you separately within the next few days.) Re: running liveocean, copying a few points I noted #154 (comment) here (didn't realize that PR was closed when I commented there 🤦 ):
|
Okay @cisaacstern , thanks for the update! 🤞 |
BTW, the PR got closed because I deleted my fork (forgetting the PR was still open). I had to revive it with this approach: https://stackoverflow.com/a/73549088/2005869. But then even though when I reopened the old PR, Github saw the new fork, it was confused, so I closed the PR again and created a new one. 😖 |
Removing the
|
@cisaacstern , any updates here? |
Charles is currently on parental leave. 👶 In the meantime, maybe @andersy005 might be able to help move this forward? |
i'm happy to look into this sometime this afternoon... |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
/run liveocean |
🎉 The test run of import xarray as xr
store = "https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/test/pangeo-forge/staged-recipes/recipe-run-1279/liveocean.zarr"
ds = xr.open_dataset(store, engine='zarr', chunks={})
ds |
@rsignell-usgs, something seems to have gone wrong because the written store appears to be empty. i don't know why :( ....
File ~/mambaforge/envs/playground/lib/python3.10/site-packages/xarray/backends/zarr.py:401, in ZarrStore.open_group(cls, store, mode, synchronizer, group, consolidated, consolidate_on_close, chunk_store, storage_options, append_dim, write_region, safe_chunks, stacklevel)
385 except KeyError:
386 warnings.warn(
387 "Failed to open Zarr store with consolidated metadata, "
388 "falling back to try reading non-consolidated metadata. "
(...)
399 stacklevel=stacklevel,
400 )
--> 401 zarr_group = zarr.open_group(store, **open_kwargs)
402 elif consolidated:
403 # TODO: an option to pass the metadata_key keyword
404 zarr_group = zarr.open_consolidated(store, **open_kwargs)
File ~/mambaforge/envs/playground/lib/python3.10/site-packages/zarr/hierarchy.py:1347, in open_group(store, mode, cache_attrs, synchronizer, path, chunk_store, storage_options, zarr_version)
1345 if contains_array(store, path=path):
1346 raise ContainsArrayError(path)
-> 1347 raise GroupNotFoundError(path)
1349 elif mode == 'w':
1350 init_group(store, overwrite=True, path=path, chunk_store=chunk_store)
GroupNotFoundError: group not found at path '' |
@rsignell-usgs, Just realized this is using kerchunk, and everything seems to be working fine when using the reference filesytem ref_url = "https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/test/pangeo-forge/staged-recipes/recipe-run-1279/liveocean.zarr/reference.json"
ds = xr.open_dataset("reference://", engine='zarr',
backend_kwargs={'consolidated': False,
'storage_options': {'fo': ref_url, 'remote_options': {'anon': True}, 'remote_protocol': 's3'}},
chunks={})
ds We need to update the pangeo-bot and the front-end to remove hard-coded assumption about all datasets being zarr native and ensure the right code snippets are used for different types of recipes supported by pangeo-forge. |
@andersy005 is there anything for me to do at this point, or just hang tight on my end? |
/run liveocean |
🎉 The test run of import xarray as xr
store = "https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/test/pangeo-forge/staged-recipes/recipe-run-1279/liveocean.zarr"
ds = xr.open_dataset(store, engine='zarr', chunks={})
ds |
oh, I see. The recipe is working correctly. It's just the code snippet that isn't working. This notebook works! |
I guess now this can be merged, right? |
Apologies for the delay, @rsignell-usgs! Thanks for the nudge. Yes, if test run passed then we can merge, which I'll do now. |
redo of #154