You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While computing averaged time using time_bounds via times = bounds.mean('d2'), I get weird results (see example below). It's my understanding that this is a bug, but I don't know yet where it's coming from.
I should note that in addition to getting wrong time values, the resulting time values are not monotonically increasing even though my time bounds are.
Yikes, this looks bad; thanks for the report @andersy005. The logic in duck_array_ops is pretty thorny surrounding cftime dates. I'm guessing there's some sort of integer overflow issue happening here (hence the weird non-monotonic behavior). I'll have a closer look tomorrow.
What happened:
While computing averaged time using time_bounds via
times = bounds.mean('d2')
, I get weird results (see example below). It's my understanding that this is a bug, but I don't know yet where it's coming from.I should note that in addition to getting wrong time values, the resulting time values are not monotonically increasing even though my time bounds are.
What you expected to happen:
Correct averaged time values
Minimal Complete Verifiable Example:
Anything else we need to know?:
Environment:
Output of xr.show_versions()
The text was updated successfully, but these errors were encountered: