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
BB suggests that we should move everything concerning measures, or at least all the concrete classes, into mlr3measures. In particular MeasureClassifCost and MeasureRegrRSQ -- these are currently in mlr3 since they have config parameters and are therefore R6-classes, not functions.
If we put the R6 classes into mlr3measures, then mlr3measures must "import" mlr3, so the dependency switches around compared to the current status (mlr3 imports mlr3measures). We could think of some mechanism that mlr3 automatically loads mlr3measures in the background if it is installed.
The text was updated successfully, but these errors were encountered:
BB suggests that we should move everything concerning measures, or at least all the concrete classes, into mlr3measures. In particular MeasureClassifCost and MeasureRegrRSQ -- these are currently in mlr3 since they have config parameters and are therefore R6-classes, not functions.
If we put the R6 classes into mlr3measures, then mlr3measures must "import" mlr3, so the dependency switches around compared to the current status (mlr3 imports mlr3measures). We could think of some mechanism that mlr3 automatically loads mlr3measures in the background if it is installed.
The text was updated successfully, but these errors were encountered: