Verify and document quick methods

Our codebase is primarily class-based, however we do have quick-methods for quickly drawing a visualizer from data without a lot of setup (for the common case). Unfortunately, most of these quick methods are undocumented and are not verified. Before the 1.0 release, it would be good if we could include them in our documentation.

Verifications:

• Does the quick method return a visualizer? (Most probably return an axes object)
• Does the quick method have an associated test?
• Does the quick method support all its parent visualizer arguments?
• Does the quick method behave as expected?

For documentation:

• Should we create a new page for the quick methods?
• Should we add the docstring automodule to the relevant documentation pages?

Other questions:

• Should quick methods call poof() or finalize() should this be an argument (e.g. poof=True)?
• Should quick methods do train/test splits? (See ROCAUC and PrecisionRecallCurve)
• Do the quick methods require other arguments?
• Is there any reason not to make the quick methods prime time?

[bbengfort]

An example of a quick method and a visualizer with detailed doc strings that discuss how best to create meaningful interactions between the two: (I tried to come up with the trickiest quick method that needs to be implemented for discussion)

https://gist.github.com/bbengfort/5d5b211c1cf49f7dac147654e75e5d24

[Kautumn06]

@bbengfort Also, I did add two additional columns to the “Quick Methods” tab to record some additional information I noticed while finishing it. One column to track when a quick method has additional parameters not found in the Visualizer and another that contains notes about when a parameter has different defaults (for instance, balanced_binning_reference has target='Frequency' while BalancedBinningReference has target=None).

The third column I added includes information about when I saw that the difference in parameter names was because of capitalization. For example, freqdist has the parameter N=50, while it is n=50 in FrequencyVisualizer . Most of the additional examples where this occurred involved one having x while the other has X.

So I hope that this is helpful! Please just let me know if you have any questions.