-
Notifications
You must be signed in to change notification settings - Fork 494
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
Introduce cross-validation earlier in module 1 and related changes #415
Comments
I would add
|
If it is consise enough why not, I would have thought that module 2 was more the right place for a longer discussion (see #416). I guess we can quickly show here that the score depends on the train-test split which motivates the introduction of cross-validation
The figure you mention has things about hyperparameter tuning so we probably don't want to include this exact figure. We already have a cross-validation figure: https://inria.github.io/scikit-learn-mooc/python_scripts/02_numerical_pipeline_scaling.html#model-evaluation-using-cross-validation. If you think it can be improved (which is quite likely) you can look at the script generating the figure: https://github.com/INRIA/scikit-learn-mooc/blob/master/figures/plot_cross_validation_diagram.py |
I think most of this has been tackled. |
train_test_split
and introducecross_validate
. This would be a notebook called something like "Evaluate your first model".Pipeline
anymore.Pipeline
insidecross_validate
(I guess when this happens later in the "Preprocessing for numerical features" notebookThe text was updated successfully, but these errors were encountered: