How to avoid variables with no dimensions from picking up concat_dim?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 366
- Forks
- 96
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
@martindurant , I've got a collection of netcdf files I'm combining with kerchunk along the ocean_time dimension.
These files have model constants stored as single value variables without a dimension.
When I combine them, these variables are picking up the ocean_time dimension, but they should not:
How can I avoid this?
Reproducible notebook here: https://nbviewer.org/gist/e0c74a4a7e947e5d04fa3e82147ff146
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproducible notebook linked in the issue and run the kerchunk combination using ocean_time. Inspect how single-value model-constant variables are represented before and after combining; done means those variables retain no ocean_time dimension while the time-varying data still combines correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100