You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -24,4 +24,18 @@ Before starting to jump into this package it is worth checking if it is actually
24
24
3. Your data is too large to fit into the memory of all your workers when distributed among them (otherwise try [DistributedArrays.jl](https://github.com/JuliaParallel/DistributedArrays.jl))
25
25
4. You want to process *all* or almost all of your data and not just a small subset. Otherwise just read the subset of interest into memory and do your processing based on this one
26
26
27
-
If you are still here
27
+
If you are still here you should also note that this package is not intended to be used by end-users directly, but the plan is to wrap functionality from this package
28
+
in other packages, in particular YAXArrays.jl, DimensionalData.jl or PyramidSchemes.jl that provide more user-friendly interfaces for the end users.
29
+
30
+
## Status of the package
31
+
32
+
This package is still under active development and should be considered experimental. Expect things to break and to already be broken. In particular, extensive documentation and tests are still missing. However, some core functionality of the package is already used by e.g. [PyramidScheme.jl](https://github.com/JuliaDataCubes/PyramidScheme.jl) which is why we decided to already register this package while still under active development.
33
+
34
+
## Basic package usage
35
+
36
+
To be done, describe the generalized moving window concept, how to define user functions, lazy interface and which runner options exist
37
+
38
+
## EngineArrays
39
+
40
+
The simplest way to use some the machinery in DiskArrayEngine is to wrap any existing DiskArray into an EngineArray by calling `engine(mydiskarray)`. Afterwards, many operations like mapslices, mapreduce, broadcast and simple statistics like mean, median, max/min etc will be dispatch using DiskArrayEngine instead of the simple
41
+
DiskArrays.jl implementation and might give significant speedups. However, currently we still default to using the `LocalRunner`, which will only use a single process, we will experiment with defaulting to `DaggerRunner` as soon as multiple processes are available.
0 commit comments