-
Notifications
You must be signed in to change notification settings - Fork 99
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
Nedelec element on boundaries #927
Comments
ups, there was a small error in the example, I've updated it. |
+1 this would be very useful! |
Here a simplified version which generates the same error: I generated two meshes using (python code)
Both meshes are the same, just the z-coordinate for all points differs in t1-1.msh to let Gridap handle it with 3D point dims The error from the previous example can be reproduced with:
While the generation of the lagrangian FESpace works just fine, the nedelec FESpace fails with the same error. Would be great if someone could have a look, I don't really know how to go on debugging :/ Thanks a lot! |
It seems that Nedelec RefFEs are not working on manifolds. Fixing this will provably require to allocate VectorValues here
with length equal to the dimension of the ambient space (instead of the reference space) and use the pseudoinverse here: Gridap.jl/src/ReferenceFEs/NedelecRefFEs.jl Line 318 in ffe4667
|
Thanks @fverdugo ! I just tried to fix this, but it seems to me, that I cannot just allocate VectorValues of a different dimension in that line. Would we need to fix this maybe within the Basis? |
Hi @HelgeGehring ! FYI ... in the following PR: I introduced a set of misc changes to support RT FEs on general manifolds. I do not have time now to take a careful look at nedelec elements, but I would guess the changes required would be similar ... Hope this helps. |
I'm trying to use a Nédélec element on a boundary, but the creation of the FESpace fails.
Is this an error in Gridap? Or am I just creating it wrong?
Thanks a lot for your help and the nice library!
Here a minimal example producing the error
The text was updated successfully, but these errors were encountered: