Update zarr reader for general datasets

Open
#53 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
data

Research direction

Start by locating the current zarr reader and reviewing how it assumes the JHU Turbulence Databases channel flow dataset, including one chunk per direction and a leaf chunk named 0. Then examine how the xarray and zarr libraries can support general datasets; done means the reader no longer depends on those hard-coded naming and chunking conventions.

Written by the indexing model from the issue text.

Description

The current zarr reader is only meant for the JHU Turbulence Databases channel flow case, which is in zarr format, but only has 1 chunk in each direction. Some naming conventions are also hard-coded for this case, like the leaf chunk file being named 0 with no extension.

  • For general zarr datasets we should use the xarray and zarr libraries to handle data reading.
Dominant language
Python
Stars
13
Forks
9
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ORNL/MATEY

All issues in ORNL/MATEY

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.