Uh oh!
There was an error while loading. Please reload this page.
Conversation
Uh oh!
There was an error while loading. Please reload this page.
| ) | ||
| except NotFittedError: | ||
| # model is not fitted, as is required | ||
| pass |
There was a problem hiding this comment.
I thought in the Python call we discussed that perhaps we would check this at the first call to run_model_on_task?
In either case I would extract this to a separate method _raise_warning_if_fitted to make sure the functions don't get too big (they already are).
There was a problem hiding this comment.
Alright, will make it into a function and push.
As for its placement, I reconsidered it given that irrespective of what is called, run_model_on_task or run_flow_on_task, this function is what the call is reduced to. Hence went ahead with this placement for this snippet of code.
There was a problem hiding this comment.
run_model_on_task actually calls run_flow_on_task. That said, then we would need to add a function to the extension interface that will indicate if a model is already fit, otherwise we can't check it in a general way.
There was a problem hiding this comment.
@mfeurer do you think this is something we should want? or do we just leave it to the extension devs to implement a warning if they see it fit?
There was a problem hiding this comment.
I like the idea of having this function as callback that can be implemented by the extension deves. And yes, I expected this function to be called from the run_model_on_task function.
Co-authored-by: PGijsbers <p.gijsbers@tue.nl>
mfeurer
left a comment
There was a problem hiding this comment.
This PR looks good now, but you accidentally committed a .orig file. Could you please remove that again?
Neeratyoy
commented
Nov 2, 2020
Done |
mfeurer
commented
Nov 2, 2020
Hey, it's a bit hard to see this but among all the failures it says: Could you please have a look? |
joaquinvanschoren
commented
Nov 2, 2020
@all-contributors please add @Neeratyoy for code |
I've put up a pull request to add @Neeratyoy! 🎉 |
PGijsbers
commented
Nov 2, 2020
@all-contributors please add @Neeratyoy for code (sorry for the spam) |
I've put up a pull request to add @Neeratyoy! 🎉 |
Neeratyoy
commented
Nov 2, 2020
Given the error message, it might be that the older versions of sklearn had I updated the design of the check to be agnostic to the sklearn versions and also to the kind of model passed. |
Codecov Report
@@ Coverage Diff @@## develop #989 +/- ##
===========================================
- Coverage 87.91% 87.86% -0.06%
===========================================
Files 36 36 Lines 4551 4565 +14 ===========================================
+ Hits 4001 4011 +10 - Misses 550 554 +4
Continue to review full report at Codecov.
|
PGijsbers
commented
Nov 3, 2020
As far as I can tell these failures are a combination of timeouts and server issues, am I overlooking something? |
mfeurer
commented
Nov 3, 2020
Yes, except for:
|
PGijsbers
commented
Nov 3, 2020
Yes this is what I referred to with timeouts (not server timeouts), my bad for leaving it ambiguous.
Will do. |
Reference Issue
Addresses #968.
What does this PR implement/fix? Explain your changes.
Prints a warning if the user passes an already fitted sklearn model to
run_model_on_task.How should this PR be tested?