Shift machine learning backend to mlr3?

[nt-williams]

No description provided.

[ck37]

I think this is a good idea - I’ve shifted my predictive work to mlr3, and piggybacking on it for tmle-related estimation would take advantage of their comparatively high software development capacity. I’m also planning to try out lmtp soon.

[nt-williams]

@ck37 Glad to hear you plan on trying out lmtp. A shift to mlr3 is tricky since the mlr3 API seems more suited to interactive use. I've been playing around with developing a convenience Super Learner package that uses mlr3 (https://github.com/nt-williams/mlr3superlearner) as a solution. Would be interested in your thoughts on this.

[ck37]

The mlr3superlearner package looks awesome; I could see it really helping people, and the code efficiency is huge.

Just out of curiosity though, what is it that makes you feel mlr3 is best for interactive usage - the large amount of code needed to implement an ensemble?