JuliaDataCubes / JuliaDataCubes/YAXArrays.jl
Use DTable from Dagger.jl for CubeTable
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 132
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
We could either ditch the CubeTable type and add a short tutorial to use DTable, or we can represent the CubeTable as a DTable internally.
This would need that we would give the proper chunks to the DTable constructor, so that we would not have to copy data from the disk while the construction of the DTable.
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
The issue names no files or tests. Start by examining the CubeTable representation and DTable's constructor in Dagger.jl, focusing on how chunks are supplied. Done means choosing either removal plus a short DTable tutorial or an internal DTable representation, with construction receiving the proper chunks without copying data from disk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100