Skip to content

Move measures-things into mlr3measures? #1291

New issue

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

Open
mb706 opened this issue Apr 17, 2025 · 0 comments
Open

Move measures-things into mlr3measures? #1291

mb706 opened this issue Apr 17, 2025 · 0 comments

Comments

@mb706
Copy link
Collaborator

mb706 commented Apr 17, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant