JuliaAI / JuliaAI/MLJOpenML.jl
Problems parsing using `:openml` or `:auto` options
Open
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 10
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
julia> df = OpenML.load(470, parser=:openml)
ERROR: MethodError: copyto!(::CategoricalVector{String, UInt32, String, CategoricalValue{String, UInt32}, Union{}}, ::ChainedVector{String, Vector{String}}) is ambiguous. Candidates:
copyto!(dest::Union{SubArray{var"#s5", N, var"#s4", I, L} where {var"#s5", var"#s4"<:(CategoricalArray{T, var"#s3", R, V, C, U} where {var"#s3", V, C, U}), I, L}, CategoricalArray{T, N, R, V, C, U} where {V, C, U}} where {T, N, R<:Integer}, src::AbstractArray) in CategoricalArrays at /Users/anthony/.julia/packages/CategoricalArrays/rDwMt/src/array.jl:615
copyto!(dest::AbstractVector{T} where T, src::ChainedVector) in SentinelArrays at /Users/anthony/.julia/packages/SentinelArrays/1hMOA/src/chainedvector.jl:326
Possible fix, define
copyto!(::Union{SubArray{T, 1, var"#s4", I, L} where {T, T1, R<:Integer, var"#s4"<:(CategoricalArray{T1, var"#s3", R, V, C, U} where {var"#s3", V, C, U}), I, L}, CategoricalVector{T, R, V, C, U} where {C, U, T, R<:Integer, V}}, ::ChainedVector)
This appears to be a CategoricalArrays issue.
However, if highlights the need for more testing.
cc @jbrea (just FYI)
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 reproducing the OpenML.load examples with parser=:openml and parser=:auto, then read the related CategoricalArrays issue and MLJOpenML issue #16 on testing. Done means the affected parsing options no longer produce the reported copyto! ambiguity and regression coverage is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100