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
{{ message }}
Repository navigation
Add a Mimetic Operator Vs Finite Difference tutorial with a step-by-step explanations and comparisons #143
Is your feature request related to a problem? Please describe.
We need a simple step-by-step tutorial that showcases the mimetic properties as opposed to other familiar discretization methods that people with an entry-level knowledge (e.g., students) can grasp, such as Finite Differences (FD). Something that shows when the mimetic discretization is better than the other.
Describe the solution you'd like
Can we find a discerning test case that showcases that this method is really superior? For instance could we provide an example in which being just high-order FD, but not mimetic, makes the difference? And then compare the same example using the MOLE operators?
After this, we could add an efficiency-focused benchmark to report on the MOLE operators efficiency. It would be useful to have benchmarks in this regard for new users/application developers that approach the library.
Describe alternatives you've considered
An alternative could be comparing a MOLE example with a high-order FEM/SEM example from another package, e.g., libCEED.
Additional context
Some of the suggestions came up from the ICorps interviewees.
cc: @jbrzensk , I think you gave a sort of similar tutorial at the beginning of the academic year for the master students working in the project. Can we re-use part of that and make it a tutorial in our documentation?
Thanks for the discussion and work here. This issue has had no activity for 28 days, so it is now marked stale. If there is no further activity, it will be closed in 42 days.
Closing because this issue stayed stale for 42 days with no activity. If this is still needed, please reopen it or open a new issue with updated context.
Thanks for the discussion and work here. This issue has had no activity for 28 days, so it is now marked stale. If there is no further activity, it will be closed in 42 days.
Closing because this issue stayed stale for 42 days with no activity. If this is still needed, please reopen it or open a new issue with updated context.
Activity
github-actions commentedon May 23, 2026
Thanks for the discussion and work here. This issue has had no activity for 28 days, so it is now marked
stale. If there is no further activity, it will be closed in 42 days.github-actions commentedon Jul 4, 2026
Closing because this issue stayed stale for 42 days with no activity. If this is still needed, please reopen it or open a new issue with updated context.
valeriabarra commentedon Jul 4, 2026
Issue only partially complete (missing BC)
github-actions commentedon Jul 19, 2026
This issue has had no activity for 14 days. It will be marked
stalein 14 days if there is no further activity.github-actions commentedon Aug 2, 2026
Thanks for the discussion and work here. This issue has had no activity for 28 days, so it is now marked
stale. If there is no further activity, it will be closed in 42 days.github-actions commentedon Sep 13, 2026
Closing because this issue stayed stale for 42 days with no activity. If this is still needed, please reopen it or open a new issue with updated context.
github-actions commentedon Sep 28, 2026
This issue has had no activity for 15 days. It will be marked
stalein 13 days if there is no further activity.valeriabarra commentedon Sep 28, 2026
keep-open
github-actions commentedon Oct 12, 2026
This issue has had no activity for 14 days. It will be marked
stalein 14 days if there is no further activity.valeriabarra commentedon Oct 12, 2026
keep-open
github-actions commentedon Oct 27, 2026
This issue has had no activity for 14 days. It will be marked
stalein 14 days if there is no further activity.valeriabarra commentedon Oct 27, 2026
PR #502 will finally close this issue.