Move ngsPETSc mesh code into Firedrake to break dependency cycle #4614
+463
−12
Conversation
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
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.
Goes with NGSolve/ngsPETSc#91
At present ngsPETSc, despite being a Firedrake dependency, imports Firedrake. This creates a challenging dependency cycle that is currently causing me a fair bit of pain thinking about releases.
Here I make a rough first attempt to move all of the Firedrake-importing code out of ngsPETSc and into Firedrake. This will not create a hard netgen dependency.
This will require a decent amount of thought regarding the interface ngsPETSc now gives to Firedrake. In fact we possibly don't need ngsPETSc at all and can make do with netgen.