dsten / datascience

75%

master: 74%

LAST BUILD ON BRANCH fix-plot-ticks

branch: fix-plot-ticks

CHANGE BRANCH

x

Reset

• fix-plot-ticks
• 0.3.dev22
• add-table-except
• better-deploy-docs
• boxplot
• cholera
• configs
• counts
• create-empty-table
• docs
• eric/docs
• fix-currency-formatter
• fix-maps
• fix-table-doctests
• fix-travis-sphinx
• fix-tutorial-typos
• geoJSONdata
• get-set-item
• gitignore-docs
• hist-label-correction
• hist-overlay
• hist2table
• mapbug
• master
• modify-visualize-params
• more-docs
• new-row-representation
• one-row-table
• readthedocs
• regions
• requirements-travis
• revert-73-gitignore-docs
• sam-tutorial
• scatter-docs
• scatter-label-fix
• some-more-docs
• split
• take-docs
• to-csv
• travis-docs
• v0.3.dev22
• zenhub-usage

Build # 348

Build Type

push

travis-ci

Committed by SamLau95

Commit Message

Fix bug in xticks for Table.plot()

Before, calling

    Table([np.arange(0, 10, .1), np.arange(0, 1, .01)], ['x', 'y']).plot('x')

Would show xticks of 0, 0.1, 0.2, etc. instead of 0, 2, 4, ...
This was beacuse we assumed that the horizontal axis values as passed in
the `ticks` variable were integers. Instead, we should just ask the axis
for the ticks it used to plot the data.

To test:

```python

a = Table([np.arange(0, 10, .1), np.arange(0, 1, .01)], ['x', 'y'])
a.plot('x')

b = Table([np.arange(0, 20, .1), np.arange(0, 2, .01)], ['x', 'y'])
b.plot('x')

Run Details

792 of 1054 relevant lines covered (75.14%)

0.75 hits per line