Conversation
…ts 4 Hermite derivatives, still wip
Benchmark Results
Benchmark PlotsA plot of the benchmark results have been uploaded as an artifact to the workflow run for this PR. |
Codecov ReportAttention: Patch coverage is
... and 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
|
improvements to be made inside StencilData.jl in the function |
kylebeggs
left a comment
There was a problem hiding this comment.
Thanks Davide for this PR. This is going to be awesome. So right now if you want to use Hermite to build an operator, how would that look like? I think you'd have to use all the low-level functions that aren't meant for the public users (i.e. they are not exported from the package), right? if so, that's fine, we can merge this after we make the minor changes I commented on. Then we can expose this functionality to the public API in another PR. This is a great start to get the ball rolling.
the matrices are Some future work could be implementing custom solvers to exploit the structure (and save some memory because we don't care about saving/returning the lagrange multipliers). As you know this is not a new idea (matrices coming from KKT conditions) but that usually involves bigger matrices. I think if we use |
thank you, I pushed a version where the weights are a field of |
Thank you, I'll read this, we should also think about using an AMG solver for the sparse system. |
Correct, I did not think about implementing a higher-level function yet, I wanted to have this "backend" part finished and tested before we do that. We might face some issue, like the fact that we need access to normals and boundary flags, in my view these should be aggregated along with point coordinates (and possibly other info) in a larger struct. |
|
Ok, then we can merge this since it is non-breaking and we can make further modifications and update the user facing code at a later time. Thanks Davide!! 🎉 |
here we go!