Predictions #1128
Merged
Predictions #1128
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
mfeurer
approved these changes
Apr 19, 2022
|
As far as I am aware the test server is running but not yet populated with the usual test data... |
|
I see. Then I guess we're good to merge this :) |
PGijsbers
added a commit
to Mirkazemi/openml-python
that referenced
this pull request
Feb 23, 2023
* Add easy way to retrieve run predictions * Log addition of ``predictions`` (openml#1103)
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.
Reference Issue
Closes #1103
What does this PR implement/fix? Explain your changes.
Adds a
predictionsproperty to the OpenMLRun object which will download and format the predictions on-demand.Only output for a pandas dataframe is supported, since we will slowly move to that standard anyway.
Local run results can also be formatted in this way.
Data is only accessed and transformed when the property is called and does not impact performance otherwise.
How should this PR be tested?
I added a line to test where we test other run consistency (download vs local run).
Any other comments?
Test server is currently not live so I couldn't test on the whole suite, but since it's an added feature it shouldn't interfere with old tests. I did a test on the live server which worked, but it may not be as comprehensive.