You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This method actually plots fitted hyperparameter values as a function of fit number, not run number, so the name is a bit misleading. The x-axis label and docstring also say run number instead of fit number.
The title of the plot accurately says '...vs fit number'.
There is one fit per generation, so alternatively you could say it plots fitted hyperparameter values vs generation.
GaussianProcessLearner.plot_noise_level_vs_run() has the same issues as plot_hyperparameters_vs_run().
In particular:
GaussianProcessVisualizer.plot_hyperparameters_vs_run()
'...vs fit number'
.GaussianProcessLearner.plot_noise_level_vs_run()
has the same issues asplot_hyperparameters_vs_run()
.NeuralNetVisualizer.plot_losses()
To make things more clear I was thinking of making the following changes:
GaussianProcessVisualizer
methods mentioned above to end invs_fit()
.NeuralNetVisualizer.plot_losses()
to say epochs instead of training run.@charmasaur do you have any opinions on this? If not I'll just make the changes listed above, probably some time in the next week.
The text was updated successfully, but these errors were encountered: