Add a Null Solver that has no action #252
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
aaadelmann
approved these changes
Jan 11, 2024
matt-frey
added
the
feature request
matt-frey
requested changes
Jan 11, 2024
matt-frey
reviewed
Jan 11, 2024
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.
A NullSolver class inheriting from the Poisson base class is added. The NullSolver class is convenient because it allows to maintain the structure/software design of the program, requiring the user to only change the solver type to NullSolver when no solve action is wanted instead of having to code if statements. This functionality in needed in some programs such as OPAL when we seek to not have any solve action in a simulation.