model-selection

When users starts Serve cluster with a set of options (http options, checkpoint path) and then connects to it with a different set of options, we should either update it, or error out.

Just reviewing the docs and found this under the AutoML User Guide:

We should figure out a way to deal with this kind of thing. I think a couple of options here are:

1. Modifying the cell to only show the first few keys or so of the output.
2. Modifying the output cell so that

We should add a description to each feature defined in smartcore in the Cargo.toml file, we could use as example the Cargo.toml file of the serde project.

We should add also the documentation for the "serde" feature that currently is not present in the Cargo.toml file.

Not sure if we can u

Is your feature request related to a problem? Please describe.
NA

Describe the solution you'd like
Implement in the sklearn_genetic.plots module a function named plot_parallel_coordinates to inspect the results of the learning process

Describe alternatives you've considered
The function should take two arguments:

• estimator: A fitted estimator from `sklearn_genetic.G

Is your feature request related to a problem? Please describe.
Feature is not directly related to a problem, but is rather an enhancement of existing functionality. As suggested by Julian King on the facet Slack channel, we could add Maximum Relevance Minimum Redundancy (MRMR) as a feature selection algorithm.

The algorithm is explained in the following papers:
https://arxiv.org/pdf/1