Replies: 4 comments
-
any updates? |
Beta Was this translation helpful? Give feedback.
0 replies
-
isn't this fixed by now from mfem side? |
Beta Was this translation helpful? Give feedback.
0 replies
-
When we last had a discussion this will no longer be required, when the edges are fixed in mfem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
MFEM export for multipatch systems
Using Bezman routins
In a current PR in bezman, MFEM export was restructured to only use corner vertices of the splines, and it provides functionality to identify the connectivity, the edge enumeration with identical knot vectors as well as boundary elements. The use of corner-vertices-only makes it available also for arbitrary spline types (which could be handed on the python side).
Problem with misalignment
Still, the MFEM export is not "safe", as is relies on some strong assumptions. MFEM export requires spline patches to be structured, i.e., neighboring elements need to be ordered in the same manner.
Example:
This convention is arbitrary, as knotvectors can still be matching between two faces. Further, parametric axis can be arbitrarily changed within a spline. Starting from a random seed, we can propagate this information and permutate axis, which would allow the mfem export for all "structurable" spline patch systems.
Proposal
I would suggest solving this issue in two steps
ExtractMFEMInformation
routine in splinepy. This could be a fast solution to make splinepy accessible for first testsThe first step could be done very fast, the second one would be great for the next HACK DAYS ™️
@j042 I would love to hear your opinion on this...
Beta Was this translation helpful? Give feedback.
All reactions