-
Notifications
You must be signed in to change notification settings - Fork 44
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
Refactor model scitype check2 #732
Refactor model scitype check2 #732
Conversation
Codecov Report
@@ Coverage Diff @@
## for-a-0-point-20-release #732 +/- ##
===========================================================
Coverage ? 85.06%
===========================================================
Files ? 36
Lines ? 3369
Branches ? 0
===========================================================
Hits ? 2866
Misses ? 503
Partials ? 0 Continue to review full report at Codecov.
|
This looks good! I had figured the main issue was in the tests where we were checking for the presence of various log messages. I just checkout out your branch and ran through all the tests without issue! Thanks for helping me along here! |
…an-turing-institute/MLJBase.jl into refactor_model_scitype_check2
@pazzo83 I've rebased this PR onto |
Continuation of #731.
Needs:
@pazzo83 Be good if you review this (the most recent commits). The main problems fixed in this continuation are:
fit_data_scitype
for supervised models supporting weights (so not part of this PR, but partly responsible for failure of tests in remove specific model checks for general scitype check #731)Unknown
infit_data_scitype
. This is now a separate function_contains_unknown
with tests.check_model_scitype
was not returning the value ofnowarns
The difficulties encountered in #731 are due in some part to a lack of testing of the
check_model_scitype
"fallback" we are now using as the main method. The methods we are removing were covering up this lack of testing, but that's a poor excuse. My apologies for this.To do:
for-a-0-point-20-release
. Technically, the only "breaking" change is changes to strings in the warnings. However, I think these changes are pretty critical for new users, for which the new warnings will be more cryptic. So, we may want to at least wait for some progress on [Discussion] Review model documentation strings MLJ.jl#898 before releasing the changes here. @pazzo83 You could continue development of "supervised" transformers using thefor-a-0-point-20-release
branch? This is being regularly rebased onto dev. What do you think?