-
Notifications
You must be signed in to change notification settings - Fork 1
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
As a user, I want an "unbounded" time dimension in pairs and statistics formats that most software applications can parse into a time #275
Comments
Original Redmine Comment See #96190-12 onwards. |
Original Redmine Comment |\3. Date Ranges | |
Original Redmine Comment Useful, thanks. Those python bounds are surprising. Is that core python or whatever you call it? |
Original Redmine Comment I mean, no paleontological time-series in Python, I guess, at least not as times :) |
Original Redmine Comment Yeah, that's vanilla. The Numpy ranges are probably greater due to them being implemented in C or Fortran, not python. |
Original Redmine Comment It looks like numpy can handle [9200000000000000000 BC, 9200000000000000000 AD]. |
Original Redmine Comment Ha, that should be wide enough :) ( Still, we should change it. ) |
Author Name: James (James)
Original Redmine Issue: 96218, https://vlab.noaa.gov/redmine/issues/96218
Original Date: 2021-09-14
Given an evaluation that writes pairs or statistics
When the pools are described for an unbounded time dimension
Then most software applications used by real users should be able to read them
Examples of languages: python applications, R applications, bash applications etc.
( Some applications can handle things like @+1000000000-12-31T23:59:59.999999999Z@, such as java and bash applications, others cannot so easily, such as python, apparently. )
The text was updated successfully, but these errors were encountered: