Fix in _add_constraints() #45
Merged
Conversation
This file contains 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
with the logic of the local Gridap FESpace constructor Before the fix, whenever we were not passing the conformity kw-arg, we were building a H1-conforming space only for the conforming mesh interfaces and we were not gluing at all the non-conforming ones
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix in order to have an _add_constraints() function which is consistent
with the logic of the local Gridap FESpace constructor
Before the fix, whenever we were not passing the conformity kw-arg, we were building a H1-conforming space only for the conforming mesh interfaces and we were not gluing at all the non-conforming ones