-
Notifications
You must be signed in to change notification settings - Fork 6
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
I359 programmatically query results #367
Conversation
…or single sector model, single output and *multiple* model runs
…rnal() for outputs with ndims>1
Codecov Report
@@ Coverage Diff @@
## develop #367 +/- ##
===========================================
+ Coverage 70.73% 71.02% +0.29%
===========================================
Files 59 60 +1
Lines 5204 5336 +132
Branches 618 659 +41
===========================================
+ Hits 3681 3790 +109
- Misses 1431 1449 +18
- Partials 92 97 +5
Continue to review full report at Codecov.
|
…ilability of quieried output as well as dimensionality Issue #359
I'm happy with the functionality now. @tomalrussell wanted to have a look through the testing options for you @fcooper8472, so over to him. |
That would be really helpful - I've been struggling to mock a "complete" state that includes the necessary model runs, sector models and results. If we could work out how to provide that in a fixture it would be useful more widely, but would definitely allow us to thoroughly test this. |
Include style niggles: - docstring parameter description on next line - prefer raising relevant errors to assertions - avoid abbrev.s in param. names (sec_model_name > model_name)
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.
This looks good to merge - especially the key Results.read
method seems to hit the spot.
If the testing around Results.read
and Store.get_results
can be fleshed out reasonably straightforwardly, based on the results_with_results
fixture, that would be great, otherwise let's not block this PR.
Looking forward to using this in coming weeks! 👍
I'm in the process of tinkering with the fixtures to improve the test coverage - but happy for you to merge this now and look at further changes down the line if you prefer? |
I'll pick this up on Tuesday afternoon and aim to cut 1.1 (#369) - a bit of tinkering and coverage would be welcome if you can fit it in before then. |
Codecov Report
@@ Coverage Diff @@
## develop #367 +/- ##
===========================================
+ Coverage 70.73% 71.02% +0.29%
===========================================
Files 59 60 +1
Lines 5204 5336 +132
Branches 618 659 +41
===========================================
+ Hits 3681 3790 +109
- Misses 1431 1449 +18
- Partials 92 97 +5
Continue to review full report at Codecov.
|
See #350.
Current shortcomings are:
get_results()
method.