Move Tendencies class into separate files #159
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
|
CTests pass on Chrysalis and Frontier. |
mwarusz
force-pushed
the
mwarusz/omega/separate-tendencies
branch
from
8f09e6f
to
2639661
Compare
|
I tested this branch using the manufactured solution, which requires modifications to the I was able to run the manufactured solution test with the changes incorporated in this pull request. |
sbrus89
reviewed
Nov 18, 2024
@sbrus89 Done. |
sbrus89
approved these changes
Nov 19, 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.
This is a small PR that separates the
Tendenciesclass from the tendency terms files into its own set of files. This was suggested in #109 (comment), but we never got around to it. Since there are no open conflicting PRs, now it is a good time to do it.