-
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
Parallel polydata reader #634
Conversation
Test the local number of points/trees instead of the global
@Davknapp Please fix the merge conflicts and update the branch if applicable. Then I start the review. |
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.
Would you also update t8_cmesh_read_from_vtk
to be able to read paralle polydata files?
Co-authored-by: Johannes Markert <[email protected]>
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.
LGTM!
Just one final request.
Would you update t8_cmesh_read_from_vtk
to be able to read paralle polydata files?
I had this comment in the last review, too. Maybe you overlooked it?
Co-authored-by: Sandro Elsweijer <[email protected]>
Was adressed, but jmark is on holiday and cannot dismiss this on his own
Implemented a parallel reader for vtkPolyData.
Restructured the parallel reader to decrease Code-duplication.
The merging of polyData and vtkUnstructuredGrids are slightly different, resulting in two slightly different merging-functions.
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.Licence
doc/
(or already has one)