We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add explanation of hyperparamter tuning to episode 3
In this section: https://carpentries-incubator.github.io/deep-learning-intro/03-monitor-the-model/index.html#counteract-model-overfitting we are actually doing hyperparamter tuning (we are changing a hyperparameter). It is only a small extra step to do this within a for-loop.
You can get inspiration from @qualiaMachine 's script here: https://colab.research.google.com/drive/1B_F5ik6P9hfbKT2pzfMgsvFeF99_Uy9V?usp=sharing
This issue resulted from discussions in #348
The text was updated successfully, but these errors were encountered:
I just realized we already have something like this in the final exercise related to dropout: https://carpentries-incubator.github.io/deep-learning-intro/04-advanced-layer-types/index.html#vary-dropout-rate We can slightly build that out further by adding an infobox on grid search.
Sorry, something went wrong.
svenvanderburg
Successfully merging a pull request may close this issue.
Add explanation of hyperparamter tuning to episode 3
In this section: https://carpentries-incubator.github.io/deep-learning-intro/03-monitor-the-model/index.html#counteract-model-overfitting we are actually doing hyperparamter tuning (we are changing a hyperparameter). It is only a small extra step to do this within a for-loop.
Add an infobox that discusses hyperparameter tuning in a for-loopsee Add hyperparameter tuning to episode 3 #351 (comment)You can get inspiration from @qualiaMachine 's script here: https://colab.research.google.com/drive/1B_F5ik6P9hfbKT2pzfMgsvFeF99_Uy9V?usp=sharing
This issue resulted from discussions in #348
The text was updated successfully, but these errors were encountered: