Skip to content
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

Switch internal time units to microseconds #85

Open
spencerkclark opened this issue Aug 17, 2021 · 0 comments
Open

Switch internal time units to microseconds #85

spencerkclark opened this issue Aug 17, 2021 · 0 comments
Labels
New: Issue Highlight a new community raised "generic" issue

Comments

@spencerkclark
Copy link
Member

📰 Custom Issue

Historically the time units used in nc-time-axis have been "days since 2000-01-01". cftime.num2date and cftime.date2num are exact as of cftime version 1.2.1 if units of microseconds are used, since all arithmetic can be done with integers. Therefore it might be beneficial to switch to using microseconds internally within nc-time-axis. Errors are very small if we do not use microseconds, but we might as well be as exact as possible.

@spencerkclark spencerkclark added the New: Issue Highlight a new community raised "generic" issue label Aug 17, 2021
@scitools-ci scitools-ci bot removed this from 🚴 Peloton Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New: Issue Highlight a new community raised "generic" issue
Projects
Status: No status
Development

No branches or pull requests

1 participant