Anthony Blaom, PhD
Anthony Blaom, PhD
Thanks for the lightning reply ❤️
@cscherrer Could you try renewing your keys to see if that clears this up?
Anyone have some time to revisit this?
Related (duplication?): https://github.com/JuliaML/MLUtils.jl/issues/90
> As a further breakdown, I also suggest to move getobs and numobs and their implementations for the Base types to a MLCore.jl repo. Yes, please.
In work on MLFlow integration we see that we need such a function. So opening a new issue to add a `params2` which in the next breaking release replaces `params`...
And forward other methods/traits, such as `feature_importances`, and so forth (see BinaryThresholdPredictor code for other examples)
Also, after https://github.com/JuliaAI/MLJ.jl/issues/1125 is closed, they will need to overload `MMI.constructor`.
This makes sense. As far as changing the behaviour of the `@mlj_model` macro, that will have to wait for the next breaking release, which won't be for a while.
Thanks @ExpandingMan for these further thoughts. Sorry to hear about the parameter woes. Gradient boosters have a lot of them, that's for sure. In my experience maintaining the MLJ ecosystem,...