Handle missing or unparseable timestamp field

htm-community / nupic.visualizations

Web application for interactive graphs, anomaly highlighting and online monitoring.

MIT License

17 stars 11 forks source link

Handle missing or unparseable timestamp field #28

Closed breznak closed 8 years ago

breznak commented 8 years ago

Fixes #2

As it says, we are now more robust to plotting any CSV files! The order is as follows:

TIMESTAMP column is parsed as date string
- if numeric, used as that value (x-data)
- if un-parseable, fallback to iteration number.
if no TIMESTAMP, fallback to iterations

breznak commented 8 years ago

@jefffohl when you have time, can I have your review on the standing PRs? This one should be merged last, for possible merge conflicts.

breznak commented 8 years ago

@jefffohl thanks for the improvements, fixed.

I've merged with master and again a breakage Mismatch between number of labels (__iter__,anomaly) and number of columns in array (1) do you know where it could come from?

breznak commented 8 years ago

@jefffohl fixed the above problem, works nice now. Please merge if you agree.

breznak commented 8 years ago

Thanks! FYI Jeff, fixed above.