Working on a Import Mesh Workaround (FerriteGmsh.jl Issue 15) #1117
jamesmichaelgorman
started this conversation in
General
Replies: 1 comment 2 replies
-
You can get the nodesids of a cell with But I think the it would be better to adress the original issue: Can you orient your Gmsh surfaces correctly such that counter-clock-wise elements are generated? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This topic may technically be better off in FerriteGmsh, but I am hoping more people will see this and have a suggestion.
It has been known for a little bit (Ferrite-FEM/FerriteGmsh.jl#15), that when FerriteGmsh.jl imports a mesh via Gmsh that nodes within elements may be clockwise instead of counter-clockwise (for an unknown reason, as far as I can tell). I want to use Ferrite to solve problems that require non-trivial geometries, and that means importing a mesh.
My workaround is slow because I intend to cycle through every element. However, right now I am slowed down because I don't appear to be able to easily extract out nodes number from grid.cells[1], but I have not yet found an easy way to get node numbers out from the output. While I can easily output the node values, such as
Triangle((1, 3, 2))orQuadrilateral((1, 5, 9, 7)), I cannot appear to easily extract them out individually. Does someone know a function that would allow me to get that done? Currently, the only way I see to brute force this correction is to usegetcoordinates()and then match the coordinates to nodes in a list (inefficient, but should work). Does anyone else have any ideas?James
Beta Was this translation helpful? Give feedback.
All reactions