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
Agreed. We have been discussing if there is any value in having a consistent interface (or just a list of common plots) here. Most of the plots we do are already provided somewhere else.
What do you feel @dfds-data/data-science-chapter? Should we remove this plot or let it be for now? 💀
As @KPLauritzen mentions, it could be valuable if we had the same interface for all of our plots. That way we would be able to plug them into a training component that pushes the plot artifacts to mlflow (as an example).
I like the idea of having one interface for all the plots.
However, if we want this library to be installed in many projects, we will suddenly drag in many extra dependencies. Maybe we can add yellowbrick or seaborn or some other plotting library as an optional dependency?
Does the
plot_roc_curve
provide anything addtional than what is in Scikit-learn?See RocCurveDisplay
From what I see, it does not.
The text was updated successfully, but these errors were encountered: