Time column error - sorting error?

[conradlee]

I have twenty different times that I would like to have displayed. The values for these times are 1-19. However, when openheatmap displays my data, the slider only contains the maps for times

 [1,10,11,12,13,14,15,16,17,18,19].

So it has left out times 2-9.

My guess is that times are sorted using an alphanumeric sort rather than a numeric sort, leaving the sorted list of times at

[1,10,11,12,13,14,15,16,17,18,19,2,3,4,5,6,7,8,9]

At some later stage the times after 19 are left out because some piece of code detects that they violate the sorting. But I have not worked throught the sorce code to confirm this theory.

[conradlee]

Oh, I see that this is noted in the documentation. So this "issue" is not really a bug---rather it's more a feature request for a slicker handling of times.

[petewarden]

Sorry about that Conrad! Could you email me the spreadsheet or CSV file you're using through [email protected] and I'll debug what's going wrong. You're right about the alphanumeric nature of the sort, but it shouldn't be dropping those out-of-order values.

cheers, Pete

On Fri, Sep 23, 2011 at 5:17 AM, Conrad Lee < [email protected]>wrote:

I have twenty different times that I would like to have displayed. The values for these times are 1-19. However, when openheatmap displays my data, the slider only contains the maps for times

 [1,10,11,12,13,14,15,16,17,18,19]''.'

So it has left out times 2-9.

My guess is that times are sorted using an alphanumeric sort rather than a
numeric sort, leaving the sorted list of times at

```python
[1,10,11,12,13,14,15,16,17,18,19,2,3,4,5,6,7,8,9]

At some later stage the times after 19 are left out because some piece of code detects that they violate the sorting. But I have not worked throught the sorce code to confirm this theory.

Reply to this email directly or view it on GitHub: https://github.com/petewarden/openheatmap/issues/6