You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using IterativeSolvers.jl on custom vectors and matrices, I find it easier to add methods to generic BLAS routines (scal!, mul!, axpy!...) than customizing the broadcasting machinery on said types.
This is a very small modification that simply requires changing lines like
it.r .-= alpha .* it.c
to
axpy!(-alpha, it.c, it.r)
and so on as illustrated in the cg.jl file in this PR.
If this is a modification that is acceptable, I'll work my way through the other solvers (bicgstabl...).
I believe we've gone back and forth on this. Long ago there was overhead to broadcasting, so the BLAS routines were called. Then Julia improved and folks wanted broadcasting because it's more generic. I think I'm happy with the current broadcasting stuff, also because for example CG would need an axpby somewhere, which I think is not standard BLAS.
These functions are now owned by LinearAlgebra (and not LinearAlgebra.BLAS) and admit generic fallbacks, likely using broadcasting but I don't remember. Another option could be to introduce _axp[b]y!, that use broadcasting generically but may be overloaded with a custom axpy!-like implementation.
These functions are now owned by LinearAlgebra (and not LinearAlgebra.BLAS) and admit generic fallbacks, likely using broadcasting but I don't remember. Another option could be to introduce _axp[b]y!, that use broadcasting generically but may be overloaded with a custom axpy!-like implementation.
Fair enough, I might have to dig into how to customize broadcasting for my own datatypes...
These functions are now owned by LinearAlgebra (and not LinearAlgebra.BLAS) and admit generic fallbacks, likely using broadcasting but I don't remember. Another option could be to introduce _axp[b]y!, that use broadcasting generically but may be overloaded with a custom axpy!-like implementation.
That's pretty much what Krylov.jl does with some macros (@kaxpy...).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using IterativeSolvers.jl on custom vectors and matrices, I find it easier to add methods to generic BLAS routines (
scal!,mul!,axpy!...) than customizing the broadcasting machinery on said types.This is a very small modification that simply requires changing lines like
to
and so on as illustrated in the cg.jl file in this PR.
If this is a modification that is acceptable, I'll work my way through the other solvers (bicgstabl...).