Vectorized (GPU) cfd solver#14412
Conversation
…unidentified problem with dirichlet conditions
…iphysics/Kratos into vectorized_cfd_solver
There was a problem hiding this comment.
Chery pick this into an independent PR
There was a problem hiding this comment.
I woukd prefer to ñeave this together as it is needed for this pr.
There was a problem hiding this comment.
You can keep it here, but can be cherry-piced and merged in advance there, so it simplifies review here and keeps it simple
There was a problem hiding this comment.
I agree @loumalouomega. Indeed, I had this pending to be done. @RiccardoRossi I can do it.
There was a problem hiding this comment.
OK. I just saw that Charlie did it.
loumalouomega
left a comment
There was a problem hiding this comment.
Minor comment related to changes that can be cherry-picked to another PR
|
I've move the changes to #14413 but they will not work without part of the changes in the solver... |
Well, only what is actully standalone can be ported...Anyway, CI is failing... |
|
FYI: https://www.modular.com/open-source/mojo, is python GPU accelerated |
…rices-cp [Core] Cherry pick changes from #14412
…iphysics/Kratos into vectorized_cfd_solver
…/Kratos into vectorized_cfd_solver
📝 Description
this PR adds a semi explicit CFD solver which can either run on the CPU or GPU. Myself and @rubenzorrilla we have been working on this for quite a while and it is currently in a reasonable state.
it requires the library cupy and pyamg
The solver is entirely written in python but leverages blas calls to be efficient.
With the current version and using a mid-tier GPU it is about 10 times faster than the gpu.
Having said this, honestly the style is a good fit to the gpu but probably not for use on cpu. Efficient and parallel use of the CPU will depend on the undetying blas.
user can set gpu or OpenMP as: