Feature Visualizer

[bbengfort]

This issue replaces #7

[rebeccabilbro]

Create a FeatureVisualizer base class where the intent is that it comes between or at the end of transformers but before the estimator. This should have

• fit
• transform
• draw
• fit_draw
• fit_transform (alias for fit_draw)

Needs to extend BaseEstimator, BaseTransformer, and VisualizerMixin.

[bbengfort]

@rebeccabilbro I've moved the FeatureVisualizer from yellowbrick.base to yellowbrick.features.base in order to keep the base class with the rest of the code.

As a result, I consider this story done!

[rebeccabilbro]

@bbengfort awesome! Should i be doing the same thing for ScoreVisualizer? e.g. moving regressors.py and classifiers.py into a separate folder with its own base?

[bbengfort]

If you think that's better organized, then yes - but I wasnt quite sure how
to divide up the model space. We could save it for discussion after the 0.3
release!

On Friday, October 7, 2016, Rebecca Bilbro notifications@github.com wrote:

@bbengfort https://github.com/bbengfort awesome! Should i be doing the
same thing for ScoreVisualizer? e.g. moving regressors.py and
classifiers.py into a separate folder with its own base?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#43 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAth7sNKdFeCaaRhsRXnzTrGEndSfZouks5qxoX_gaJpZM4J2b6q
.

Sent from Gmail Mobile

[rebeccabilbro]

Sounds good; opened new issue #65 for the backlog.