-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
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
Issues with interactions of LOBPCG and LinearMaps.LinearCombination #259
Comments
Can you show the full stacktrace? What is calling julia> using LinearMaps
[ Info: Precompiling LinearMaps [7a12625a-238d-50fd-b39a-03d52299707e]
julia> a = LinearMap(identity, 10)
LinearMaps.FunctionMap{Float64}(identity, 10, 10; ismutating=false, issymmetric=false, ishermitian=false, isposdef=false)
julia> b = a + a
LinearMaps.LinearCombination{Float64,Tuple{LinearMaps.FunctionMap{Float64,typeof(identity),Nothing},LinearMaps.FunctionMap{Float64,typeof(identity),Nothing}}}((LinearMaps.FunctionMap{Float64}(identity, 10, 10; ismutating=false, issymmetric=false, ishermitian=false, isposdef=false), LinearMaps.FunctionMap{Float64}(identity, 10, 10; ismutating=false, issymmetric=false, ishermitian=false, isposdef=false)))
julia> using LinearAlgebra
julia> mul!(zeros(10,3), b, rand(10, 3))
10×3 Array{Float64,2}:
1.77102 1.00707 1.0886
0.718971 0.853393 0.156217
0.49425 0.908157 1.91741
0.928176 0.230759 0.580476
0.818615 0.511816 0.195229
1.52616 1.5837 0.964583
1.16619 1.55489 1.22776
1.17506 0.316413 0.779997
0.28235 0.558206 1.7167
0.200653 0.873268 0.634083 |
Please report the versions of the packages using |
I suspect the new Pkg upper bounds got you an ancient version of |
I'm using Julia 1.3 (2019-11-26)
Here's the stack trace:
|
I tried using |
I'm glad somebody is interested in/using the |
I'm not entirely sure whether this issue should be reported at LinearMaps or here, but here goes the MWE (on Julia 1.3):
Strangely enough, if I wrap the map, it works:
The offender seems to be the
Array{Float64,2}
, where it tries to do multiplication with a row vector instead a column vectorArray{Float64,1}
but I'm not sure why that is the case.The text was updated successfully, but these errors were encountered: