-
Notifications
You must be signed in to change notification settings - Fork 55
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: More robust connect cmesh faces by vertices and sphere cmesh examples #1296
Conversation
Do you need any input in order to progress on the review? Please agree on who feels responsible for doing the review. |
I will do it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small changes, then we can merge.
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
Co-authored-by: David Knapp <[email protected]>
I like it! Done. |
Describe your changes here:
This PR introduces fixes/enhancements to make the
join_by_vertices
routine more robust regarding the value range of the input vertices. Besides that this PR makes the sphere cmesh examples more robust by applying the actual radius parameter at the end when the vertex information is stored in the cmesh object. For some use cases the radius gets extremely big, e.g. around 1e6, and the shell thickness, quite small, e.g. around 10. This might confuse thejoin_by_vertices
routine. The fix is to determine the face connectivity on a reference sphere/shell with sane radius/thickness.All these boxes must be checked by the reviewers before merging the pull request:
As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.
General
The reviewer executed the new code features at least once and checked the results manually
The code follows the t8code coding guidelines
New source/header files are properly added to the Makefiles
The code is well documented
All function declarations, structs/classes and their members have a proper doxygen documentation
All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue)
Tests
Github action
The code compiles without warning in debugging and release mode, with and without MPI (this should be executed automatically in a github action)
All tests pass (in various configurations, this should be executed automatically in a github action)
If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):
Scripts and Wiki
script/find_all_source_files.scp
to check the indentation of these files.License
doc/
(or already has one)