Conversation
…tmp point's fields: this field is used in the distributed analysis of ParMmg (that calls setVertexNmTag too) and has to be preserved.
… to skip points for which the function returns 1 (in Mmg we want to skip parbdy points while in ParMmg we want to skip all points that are not old parallel boundaries).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR replaces the use of the
tmppoint field in thesetVertexNmTagfunction by the use of a temporary array.For Mmg it should not change anything but it fixes the issue introduced in the parallel analysis of ParMmg by the modification of the
tmpfield (that is used to store the global node numbering and should not be modified before, at least, the end of the normal computation).See ParMmg issue 97