310 add postprocessing to the poisson profiling case - #313
Merged
spossann merged 4 commits intoAug 3, 2026
Conversation
spossann
marked this pull request as ready for review
August 3, 2026 06:42
spossann
marked this pull request as draft
August 3, 2026 06:59
max-models
approved these changes
Aug 3, 2026
max-models
left a comment
max-models
left a comment
Member
There was a problem hiding this comment.
Looks good! These figures will be included in the profiling-data once #315 is merged.
spossann
marked this pull request as ready for review
August 3, 2026 15:39
spossann
deleted the
310-add-postprocessing-to-the-poisson-profiling-case
branch
August 3, 2026 15:40
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
2 participants
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.
Solves the following issue(s):
Closes #310
Assertion for the relative errors for solution and rhs have been added. If these assertions pass, figures and errors are stored in
sim.env.sim_folder. Should we push them to the server for later inspection?