-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat: Revamp CrossValidationReport to use EstimatorReport #1091
feat: Revamp CrossValidationReport to use EstimatorReport #1091
Conversation
Coverage Report for backend
|
Side-note: Was it intentional to link to PR 538? |
Nop, it seems wrong. There might be a PR in the 500'ish to be close then :) |
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.
Apart from the caching question I just have a few suggestions.
Also, I guess the feature where we save intermediate data (e.g. save after evaluating each split) is pushed back to later?
Co-authored-by: Sylvain Combettes <[email protected]>
Co-authored-by: Sylvain Combettes <[email protected]>
So here, the data are stored in the |
Co-authored-by: Auguste Baum <[email protected]>
Co-authored-by: Auguste Baum <[email protected]>
Closes probabl-ai#1003 When running skore from source, it occurs that some contributors where puzzled by the nonexistence of the UI. This PR introduces a 404 page if the UI as not been built. ## preview ![Screenshot 2025-01-17 at 09 48 00](https://github.com/user-attachments/assets/0fb38493-31fe-4c27-b7e7-3ca83f5ce838)
Closes probabl-ai#1065 ![Screenshot 2025-01-17 at 14 58 49](https://github.com/user-attachments/assets/9a261b51-5d1f-4bb5-a383-8cf79d94c47f)
…i#1141) Co-authored-by: Thomas S. <[email protected]>
Coverage Report for frontend
File Coverage
|
The comment should be addressed @augustebaum @sylvaincom |
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.
Many thanks
…rt (#1156) Build upon #1091 We should merge #1091 to make it easy to review. This PR revisits the documentation for the `EstimatorReport` and `CrossValidationReport`. The idea is to provide different examples for different purposes: - technical section: it is a section to explain more in details some internal for user that might be interested. I think that we should move those inside this specific section because we should have more a pure data science section to only show the added values of our tools on data science - use-case section: it is indeed the section to show case our tools on real data. Here we want to show the added value on the data science side. --------- Co-authored-by: Sylvain Combettes <[email protected]> Co-authored-by: Auguste Baum <[email protected]> Co-authored-by: Matt J. <[email protected]> Co-authored-by: Thomas S. <[email protected]> Co-authored-by: MarieS-WiMLDS <[email protected]>
closes #731
closes #860
closes #938
closes #978
closes #976
closes #977
closes #953
closes #1012
closes #1014
It is a revamp from the current
CrossValidationReporter
. I am working in another module such that:CrossValidationReporter
is still available such that we do the transition for the UI partCrossValidationReport
to a private module since we want to encourage people to import either fromskore
orskore.sklearn
.There is quick demo here: https://gist.github.com/glemaitre/1216d2098e3f92e045fb064b9647f3f0
TODO