Sebastian Flennerhag

Hi! Thanks for raising this issue - this would indeed be a good feature to have. For the time being, it isn't possible with the ready-made ensemble classes we have....

Hey! Thanks for flagging this, definitely looks like a bug. It's reordering based on name, the offending line seems to be the ``sorted()`` call applied to the output of ``_format_instances``,...

@jnothman thanks for the +1! To address your concerns, the API consists of four modules: ``ensemble``, ``model_selection``, ``preprocessing``, ``visualization``. ## Ensemble The ``mlens.ensemble`` module is the main component that houses...

And I'd be happy to take a look at the stacking PR when I get the chance.

@GaelVaroquaux I understand you point of view and for building a small ensemble, it certainly would be possible to have an ``estimators`` argument in the constructor. Building multi-layer ensembles would...

I suppose one alternative would be to have users specify specific layers and then pass them to an ensemble class, like so: ```python layer_1 = SubsembleLayer(ests, preps, *args) layer_2 =...

Yes that's exactly correct. An ensemble is instantiated with a ``layers`` parameter that is ``None`` by default. The ``add`` method then does ```python if not self.layers: self.layers = LayerContainer() self.layers.add(layer)...

Hey, that's a great question! You can definitely do what you propose, essentially, the difference from that and the above snippet is that we sneak in an extra step on...