Skip to content
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

Fix face node ordering for Tetrahedron{3} #475

Merged
merged 1 commit into from
Sep 8, 2022
Merged

Conversation

fredrikekre
Copy link
Member

Fix face node ordering for Tetrahedron{3} s.t. they are counter clockwise from the outside.

@codecov-commenter
Copy link

codecov-commenter commented Sep 8, 2022

Codecov Report

Merging #475 (ecb9248) into master (b9998a0) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #475   +/-   ##
=======================================
  Coverage   91.35%   91.35%           
=======================================
  Files          22       22           
  Lines        3411     3411           
=======================================
  Hits         3116     3116           
  Misses        295      295           
Impacted Files Coverage Δ
src/Grid/grid.jl 85.66% <100.00%> (ø)
src/interpolations.jl 86.88% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@fredrikekre
Copy link
Member Author

Concerning that this passes tests :D

@lijas
Copy link
Collaborator

lijas commented Sep 8, 2022

Where would this cause an issue?We dont have any example that uses the normal, I think.

@kimauth
Copy link
Member

kimauth commented Sep 8, 2022

Add some tests? 🙃

This commit fixes the ordering for Ferrite.faces(...) s.t. they are
counter clockwise from the outside. Also adjust the face order for
Lagrange{3,RefCube,2}() to match Lagrange{3,RefCube,1}().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants