Fetch upstream commits into wq-updates-tmr to squash merge conflicts#40
Merged
tredder75 merged 14 commits intowq-updates-tmrfrom Aug 25, 2021
Merged
Fetch upstream commits into wq-updates-tmr to squash merge conflicts#40tredder75 merged 14 commits intowq-updates-tmrfrom
wq-updates-tmr to squash merge conflicts#40tredder75 merged 14 commits intowq-updates-tmrfrom
Conversation
Wq updates tmr
…zation enhancement
…ors to better match HSPF results
regression_base.py -- add special exception code
…sion test results with better aliasing and initializing
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
3 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.
@tredder75, I created this PR to help identify merge conflicts sooner than later and resolve them.
Please feel free to resolve these conflicts and merge sooner than later.
As you do that, merge conflicts should also resolve in "Merge OXRX, NUTRX, and PLANK class approach into LimnoTech develop #39
cc: @ptomasula, @PaulDudaRESPEC