Skip to content

Fractional milliseconds in time series are not handled correctly. #1363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SemmZemm opened this issue Feb 8, 2017 · 4 comments
Closed

Fractional milliseconds in time series are not handled correctly. #1363

SemmZemm opened this issue Feb 8, 2017 · 4 comments
Labels
bug something broken

Comments

@SemmZemm
Copy link

SemmZemm commented Feb 8, 2017

Hi,

When I'm using scatter chart to display time series with fractional milliseconds, the fractional part is not displayed correctly. Multiple samples become one, this looks strange, for sure it's not the user expects to see on high resolution. The problem persists in all versions of plotly.js since 1.21.0. Version 1.20.5 doesn't have this problem.

Example on jsfiddle:
1.20.5 (expected behaviour)
1.23.0 (issue is reproduced)

@etpinard
Copy link
Contributor

etpinard commented Feb 8, 2017

@alexcjohnson can you comment on this?

I suspect this is a side-effect of #1194.

@alexcjohnson
Copy link
Collaborator

Yes, definitely a bug, we're clipping fractional msec because we go through native JS dates here and native dates do not support fractional milliseconds. Should be a fairly easy fix.

@SemmZemm - we'll fix this, but it's highly recommended to use date strings instead of millisecond numbers. If you do this, it works fine, and as a side benefit your plots will be portable across timezones.

@etpinard etpinard added the bug something broken label Feb 8, 2017
@hidai
Copy link

hidai commented Jul 19, 2018

@alexcjohnson, you mentioned that the precision is 100 microseconds now in this thread.
Isn't it possible to close this issue?

@alexcjohnson
Copy link
Collaborator

@hidai I'm afraid this bug is still open. 100 microseconds resolution works when you use date strings, but the issue here is when you provide the data as epoch milliseconds, and that still drops to 1 millisecond resolution.

alexcjohnson added a commit that referenced this issue Jul 26, 2018
fix #1363 - honor tenths of milliseconds in old numeric date data
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken
Projects
None yet
Development

No branches or pull requests

4 participants