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
The second code cell returns:
UndefVarError: ⋅ not defined
After adding using LinearAlgebra to get the ⋅ defined. The machine learning example using flux throws the following error:
using LinearAlgebra
MethodError: no method matching Adam(::Vector{Any}) Closest candidates are: Adam(::Any, ::Any, ::Any, ::Any) at ~/.julia/packages/Flux/kq9Et/src/optimise/optimisers.jl:168 Adam() at ~/.julia/packages/Flux/kq9Et/src/optimise/optimisers.jl:173 Adam(::Float64, ::Tuple{Float64, Float64}, ::Float64, ::IdDict{Any, Any}) at ~/.julia/packages/Flux/kq9Et/src/optimise/optimisers.jl:168 ... Stacktrace: [1] top-level scope @ In[10]:4 [2] eval @ ./boot.jl:368 [inlined] [3] include_string(mapexpr::typeof(REPL.softscope), mod::Module, code::String, filename::String) @ Base ./loading.jl:1428
Looking at the flux docs, it appears that the api has changed. I was using julia 1.8.3 and Flux 0.13.0.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The second code cell returns:
After adding
using LinearAlgebra
to get the ⋅ defined. The machine learning example using flux throws the following error:Looking at the flux docs, it appears that the api has changed. I was using julia 1.8.3 and Flux 0.13.0.
The text was updated successfully, but these errors were encountered: