-
Notifications
You must be signed in to change notification settings - Fork 89
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
Cross-elements coupling for DiscontinuousLagrange
sparsity patterns.
#710
Cross-elements coupling for DiscontinuousLagrange
sparsity patterns.
#710
Conversation
…into elements-coupling
…into elements-coupling
It looks ugly currently, there is probably better ways to do this.
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## master #710 +/- ##
==========================================
+ Coverage 91.77% 91.92% +0.14%
==========================================
Files 32 32
Lines 4718 4766 +48
==========================================
+ Hits 4330 4381 +51
+ Misses 388 385 -3
☔ View full report in Codecov by Sentry. |
Nice. Didn't look at the details, but the code is surprisingly short.
Probably you can just |
…t indexing. If it's not we can revert.
…into elements-coupling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments.
Can you test and clarify the case when we use discontinuous interpolations with shared dofs? (e.g. Crouzeix-Raviart) |
…/Ferrite.jl into elements-coupling
…into elements-coupling
…into elements-coupling
…into elements-coupling
It iterates over all cells twice, once to get the length of I,J and another to fill them. There is probably a better way to estimate their length.
Also, codegen here looks a bit complicated, I'm still learning how to use it.
I think explicit tests for sparsity patterns are missing (they're used inside other tests, but they themselves don't have a standalone test)
Manual tests:
DiscontinuousLagrange
DiscontinuousLagrange
DiscontinuousLagrange
andLagrange
coupling
Tasks:
Things to check:
push!
vs size precalculation