-
Notifications
You must be signed in to change notification settings - Fork 101
feat: Add the data accessor to CrossValidationReport #1965
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
Conversation
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.
It looks really. We still need the following:
- Similarly to
skore/tests/unit/reports/estimator/data/test_accessor.py, we need to createskore/tests/unit/reports/cross-validation/data/test_accessor.pywith the same type of tests. - We miss the documentation in the rst file
cross_validation_report.rst(we have the same issue for theestimator_report.rstand I'll make a quick PR to solve this problem). - In terms of documentation, we should scan the user guide to see where the information make sense to be added and we should use it somewhere in the example. I recall that it was complex when using the
EstimatorReportbecause our example used theCrossValidationReportso it should be quite easy to find the example where the data analysis will fit. - As commented I'll make a couple of PR that will isolate some fix or refactoring that are not related to the PR itself to make the history cleaner when it comes to the future us using
git blame.
skore/tests/unit/displays/table_report/test_cross_validation.py
Outdated
Show resolved
Hide resolved
| # pd.Series(np.ones(100)), | ||
| # pd.DataFrame(np.ones((100, 1)), columns=["Target"]), |
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 think that they are legit case and we need to test them as well. If there is a bug (I suspect that there is one because I stumbled in #1990), then we need to make a PR to fix it first. So here, I think that we should pass a Series that does not have a name as it is now, and another where we fix the 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.
See #2013
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.
Actually it may have been another error. I fixed it, but also did a ticket on skrub side to be sure: skrub-data/skrub#1593.
skore/tests/unit/displays/table_report/test_cross_validation.py
Outdated
Show resolved
Hide resolved
cecd1e2 to
ece0561
Compare
|
Caution Some commits in the pull request are not signed, or GitHub is not able to verify the signature. |
glemaitre
left a comment
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.
LGTM. I will check the documentation rendering before to merge but otherwise, it looks good.
Closes #1964
On the way, I split the tests of the data accessor for estimator report between things specifics and common.