-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Comments
@alexcjohnson can you comment on this? I suspect this is a side-effect of #1194. |
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. |
@alexcjohnson, you mentioned that the precision is 100 microseconds now in this thread. |
@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. |
fix #1363 - honor tenths of milliseconds in old numeric date data
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)
The text was updated successfully, but these errors were encountered: