Update point tag with MG_REF if the edge in xtetra is MG_REF + ci tests associated #103
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.
Update the point tag with
MG_REF
if the edge in xtetra isMG_REF
in the analysis update.After load balancing, the analysis need to be updated (
PMMG_update_analys
), in particular, the point tag might not be up to date regarding the tagMG_REF
. Indeed, if in the input distributed meshes oneEdge
is also aParallelEdge
, the tagMG_REF
to the point is not assigned properly by the analysis because parallel interfaces are systematically skipped (for example, see conditionif(((pt->tag[i] & MG_PARBDY) && !(pt->tag[i] & MG_PARBDYBDY)) || (pt->tag[i] & MG_BDY) ) continue;
inMMG5_setadj
). This is not an issue in the first iteration, however after the load balancing and in the second iteration, point tags need to be up to date. To do so, the functionPMMG_updateTagRef_node
is now added when the analysis is updated.CI tests
MG_REF
IF ( NOT ONLY_LIBRARY_TESTS )