-
Notifications
You must be signed in to change notification settings - Fork 55
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
use of AbstractArray #935
Comments
Hi Romain! I have another alternative if you want but I would like to know the type of the matrix before (just |
You are using like
I was hoping for a solution ala KrylovKit where you dont need those but I guess this is not a big deal. IterativeSolvers has the same requirements |
You allocate You just need to create your own I only recommend it for an advanced use like multi-GPU with MPI. |
Ok it just halfed my computation time and I did not optimise it. With bifurcationKit, I regret now not having tried earlier, the fact that you can reuse the krylov space is a massive boost in perfs, I thought KrylovKit was good enough |
If you use it on a GPU, the speed-up will be even greater because allocations and deallocations are more expensive, and the garbage collection system works differently. KrylovKit.jl is probably more flexible but was not developed for performances and also doesn't support preconditioners which is quite relevant for Krylov methods. |
The only con is the lack of general eigensolver like in KrylovKit |
Yes, you're totally right. I should implement some eigensolvers one day. Off-topic: Romain, I will probably come to see JB-Caillau at INRIA the second week of January. |
Great! Please ping me the week before so I can free some time. |
By the way, thanks for your detailed answers, I am typing on my phone so I am not really verbose |
Hi,
In the matrix free context, I would like to apply an operator to a Matrix representing the solution of a PDE. In order to use Krylov.jl, I have to pass AbstractVectors hence reshape / views. Is there a better workflow?
Thank you a lot
The text was updated successfully, but these errors were encountered: