Hello, What is the status of this package? Even though there was some activity lately it looks as if it lacks a little bit of love an care… Can it already be used in a production system, or are a lot of hidden bugs to be expected? Uwe

[image] ufechner7: Can it already be used in a production system, or are a lot of hidden bugs to be expected? You can use AxisArrays in production, Invenia does. But they are very touchy and so can be frustrating to work with. Any production system should have good enough integration tests …

Is somebody aware of a package that does not encode the axes in its type?

See also WIP: The Plan · Issue #1 · JuliaCollections/AxisArraysFuture · GitHub and the two packages that do each of the main halves and are designed around being composable: https://github.com/invenia/IndexedDims.jl/blob/master/src/IndexedDims.jl (WIP) GitHub - invenia/NamedDims.jl: For working …

[image] oxinabox: Note that if you want zero overhead at runtime (like NamedDims does), Its not fully clear to me, why this needs to be like that. The axis are just metadata and indexing could be done on the raw array. Its clear that permutedims and slicing require some additional things but …

DimensionalData.jl will definitely have more bugs than AxisArrays.jl, its only at 0.1.0! But they will also be fixed promptly if you post an issue. @tobias.knopp I’m wondering what the negative consequences are for you of “creating a new type”? do you mean you have problem with creating a new struc…

For instance I have written a Gtk based data viewer that can display 4D tomographic data. It looks something like: struct DataViewer data:: ??? end With a simple Array, I can do struct DataViewer data::Array{Float32,4} end With an AxisArray this is much more complicated. And no, …

[image] tobias.knopp: With an AxisArray this is much more complicated. And no, struct DataViewer{T} data::T end is not an option, because data can be changed at runtime. You could just do: mutable struct DataViewer data::AbstractArray end The performance implictations are not …

To get somewhat more concrete, here is the type that I am using ImageMeta{Float32,5,AxisArray{Float32,5,Array{Float32,5},Tuple{Axis{:color,UnitRange{Int64}},Axis{:x,StepRangeLen{Quantity{Float64,𝐋,Unitful.FreeUnits{(mm,),𝐋,nothing}},Base.TwicePrecision{Quantity{Float64,𝐋,Unitful.FreeUnits{(mm,),𝐋,n…

what a glorious type. Godlike and powerful. Huge like a mountain. :joy:

Status of AxisArrays.jl

General Usage

mauro3 September 12, 2019, 8:41am 2

There is also the new DimensionalData.jl, announced recently ANN: DimensionalData.jl and GeoData.jl.

Topic		Replies	Views
The fate of DimensionalArrays / AxisArrays in Julia, and which to actually use Specific Domains	7	3477	May 19, 2022
Converting between AxisArray like packages? General Usage	18	1603	February 27, 2021
Indexing by names, current favorites in the package space Data question , indexing , arrays	7	272	June 6, 2025
Including Named Dimensions in Base Internals & Design	2	1615	June 21, 2021
[ANN] AxisIndices Package Announcements package , announcement	15	1605	March 16, 2020

Status of AxisArrays.jl

Related topics