Benjamin Bengfort

Results 101 issues of Benjamin Bengfort

In order to avoid style-related comments when discussing code with contributors, I propose that we implement the [black](https://github.com/ambv/black) python code formatter as a pre-commit requirement for development. This will potentially...

type: task
level: expert
contagious

This PR fixes #316 and extends #954 to get it wrapped up. I have made the following changes: 1. Added documentation and tests 2. Refactored the quick method according to...

**Describe the issue** In #1232 we discovered that printing out a Visualizer in a notebook with the `KElbowVisualizer` was failing because calls to `get_params` were failing with an attribute error....

We should enhance the `PCADecomposition` visualizer to provide many of the features the `Manifold` visualizer provides, including things like: - [ ] Color points by class with a legend (See...

type: feature
priority: medium
level: intermediate

**Describe the solution you'd like** I would like to create an at-a-glance representation of multiple model scores so that I can easily compare and contrast different model instances. This will...

type: feature

When performing classification one often wants to predict not only the class label but also the associated probability to give a level of confidence in the prediction. The `sklearn.metrics.calibration_curve` method...

type: feature
level: novice

**Describe the solution you'd like** Adapt or extend the `FreqDist` visualizer to show not just the frequency of tokens in the corpus but rank them according to their relationship to...

type: feature
level: expert

This PR fixes #1047 which reported that yellowbrick's internal implementation of RFECV is much slower than scikit-learn's. This PR introduces a new implementation of `RFECV` that is closer to the...

This issue is a follow on to #721 to wrap up the extension of `JointPlot` for machine learning-specific use cases. The tasks are as follows: - [ ] Finish the...

type: feature
priority: medium

**Describe the solution you'd like** Create a contrib module, `yellowbrick.contrib.keras` that better supports the use of Keras visualizers with Yellowbrick and creates the opportunity to create Keras-specific (or neural network-specific)...

type: contrib