Carlos Parada

> Point 1 makes sense to me. I agree with recommending 2^n points, but I'm not sure about forcing it with the API. > > Point 2 sounds like it...

What about the opposite--a way to limit a multivariate transform to a subset of columns? This seems more general, since all multivariate transforms can be used as a univariate transform,...

@juliohm has there been any work on hyperparameter tuning with TableTransforms.jl? I'd like to add `asinh` (pseudolog) transformations to the package, but that would require the ability to tune 1...

> We are starting to brainstorm an API for this feature. It would be nice to have an additional hand :) Sounds good! Should we just stick to just the...

> > Sounds good! Should we just stick to just the MLJ model interface for now? > > What interface exactly? Can you share a MWE? [This interface.](https://github.com/JuliaAI/MLJModelInterface.jl)

Ahh, sounds perfect! > That means that you can use any MLJ.jl model there directly and we will wrap the interface into a more general interface with tables. Does the...

> Probably not, as our interface is a bit more general. Hmm, if that's the way it goes, I think it should be possible to have SLM.jl models work with...

Right now, model tuning. In the future, I just want to avoid duplicating work across the MLJ and JuliaML ecosystems.

> These are different ecosystems with diverging design decisions. How/why? MLJ doesn't support multivariate targets yet, but that's a feature they've wanted for quite a while now > That is...

> * Pipeline interface with various kinds of transforms that are not just "stats" (see chapter 5 of the book: https://juliaearth.github.io/geospatial-data-science-with-julia/05-transforms.html) These are implemented in MLJModels.jl, where these transforms are...