-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MCT diffusive wave routing #179
Conversation
…olves issue with mBE in SplitRouting
…ugfix for mBE and warm start
…on fix) and small fixes to unit tests.
…/ec-jrc/lisflood-code into feature/mct_optim_results_update
Fixing warm start and updating reference results for MCT
tests/test_inflow.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see this test has been removed. Is it replaced by test_dyn_inflow?
|
||
def run(self, date_start, date_end, dtsec, type): | ||
# generate inflow (inflow.tss) one pixel upstream of inflow point | ||
out_path_ref = os.path.join(self.case_dir, 'reference_mct_dyn') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see here and in other unit tests that we are creating output files outside the "out" folder. Is there a reason for that? (I know that sometimes running unit tests in parallel and removing completely the out folder in the teardown method can cause the test to fail: was this the reason? If so I agree we should fix up all teardown methods before fixing the out folder...)
Implementation of MCT diffusive wave routing.
Tests were added for the MCT implementation. Tests run with only core LISFLOOD components on.
For MCT 'Dynamic' tests, the reference outputs are generated on the fly and tests should still pass after merging. MCT tests using fixed reference outputs (testing results) should pass after merging if there are no changes to the core LISFLOOD components.
MCT tests come in two flavors:'short' tests run on a small catchment (a small sub-catchment of the Po); 'long' tests run on LF_ETRS89_UseCase.