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
Is your feature request related to a problem? Please describe.
In the version to come (v0.5.0), the CrossValidationReporter has only one plot, with scores and time at the same place. It doesn't make much sense because 99.99% of the time, they will not have the same magnitude, therefore it's troublesome to see them at the same place.
Describe the solution you'd like
I'd like to have three different plots. Keeping the current one: CrossValidationReporter.plots.compare_scores, but without the timings. And add a two new ones: CrossValidationReporter.plots.timing with the fit_time & score_time, and CrossValidationReporter.plots.timing_normalized with the fit_time_per_data_point & score_time_per_data_point
Describe alternatives you've considered, if relevant
remove the time, but it's interesting so it would be a bummer to remove them.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In the version to come (v0.5.0), the CrossValidationReporter has only one plot, with scores and time at the same place. It doesn't make much sense because 99.99% of the time, they will not have the same magnitude, therefore it's troublesome to see them at the same place.
Describe the solution you'd like
I'd like to have three different plots. Keeping the current one:
CrossValidationReporter.plots.compare_scores
, but without the timings. And add a two new ones:CrossValidationReporter.plots.timing
with thefit_time
&score_time
, andCrossValidationReporter.plots.timing_normalized
with thefit_time_per_data_point
&score_time_per_data_point
Describe alternatives you've considered, if relevant
remove the time, but it's interesting so it would be a bummer to remove them.
Additional context
No response
The text was updated successfully, but these errors were encountered: