We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProjectTo
Maybe this should be an error?
julia> using AxisKeys julia> ka = wrapdims(rand(3, 2), obs=1:3, point=["a", "b"]); julia> kb = wrapdims(rand(3, 2), obs=1:3, point=["c", "d"]); julia> ProjectTo(ka)(kb) 2-dimensional KeyedArray(NamedDimsArray(...)) with keys: ↓ obs ∈ 3-element UnitRange{Int64} → point ∈ 2-element Vector{String} And data, 3×2 Matrix{Float64}: ("a") ("b") (1) 0.928905 0.705413 (2) 0.493408 0.997449 (3) 0.877819 0.816695
We probably want to think about similar things as in invenia/NamedDims.jl#201 (comment)
The text was updated successfully, but these errors were encountered:
Could be. Unlike NamedDims there's some cost here to checking the key-vectors each time.
I'm not wholly convinced that this thing ought to exist. We could just accept a plain array as the gradient of a fancy one.
Sorry, something went wrong.
Yeah, fair, checking the keys is a performance/correctness checking tradeoff. Maybe we could still check dimnames by deferring to NamedDims though?
dimnames
Yes. I guess the style of this package would be to un-wrap & call the projector for the underlying NamedDimsArray?
No branches or pull requests
Maybe this should be an error?
We probably want to think about similar things as in invenia/NamedDims.jl#201 (comment)
The text was updated successfully, but these errors were encountered: