JuliaDataCubes / JuliaDataCubes/PyramidScheme.jl
Making the coarsest resolution the base of the pyramid
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 18
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I discussed with @rafaqz how to deal with Base and DD functions in PyramidScheme and we came to the conclusion that the Base function should work as if the Pyramid is a single layer and the different other layers are just add ons.
If we do it that way, it might be better to invert the pyramid, so that the normal functionality would happen on the coarsest resolution because that would mean, that the user would not run into memory issues when they try to run some Base functionality suddenly on a very large array.
We should add some errors or hints to tell the user, that they are operating only on the coarsest resolution and how to get the higher resolution data.
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 by inspecting the Base and DD functions in PyramidScheme.jl and the current ordering of pyramid layers. Clarify how Base should behave on the coarsest resolution, how higher-resolution data is requested, and what user-facing errors or hints would define the work as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100