Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

Xarray >= 0.10.1 time decoding yields unexpected results for SST #579

Closed
JanisGailis opened this issue Mar 21, 2018 · 1 comment
Closed

Xarray >= 0.10.1 time decoding yields unexpected results for SST #579

JanisGailis opened this issue Mar 21, 2018 · 1 comment
Assignees
@JanisGailis

Comments

@JanisGailis
Copy link
Member

#548 #443 Are both due to xarray >= 0.10.1 working differently when decoding time than it used to in xarray == 0.10.0.

See: pydata/xarray#2002

This should be monitored to bump xarray version accordingly when possible. For time being, will pin it to 0.10.0.
@JanisGailis JanisGailis self-assigned this Mar 21, 2018
JanisGailis pushed a commit that referenced this issue Mar 21, 2018
Pin xarray to 0.10.0 due to #579
e59e1d6
@JanisGailis JanisGailis mentioned this issue Mar 21, 2018
Merged
forman added a commit that referenced this issue Mar 22, 2018
@forman
Merge pull request #580 from CCI-Tools/jg-548-time-decoding
6e77fa0 
Pin xarray to 0.10.0 due to #579
@JanisGailis
Copy link
Member Author

The issue has been closed upstream #2015, waiting for release to remove the 10.0 pin.

JanisGailis pushed a commit that referenced this issue Apr 18, 2018
Update Changes.md
52d5a72 
Closes #585
Closes #579
@JanisGailis JanisGailis mentioned this issue Apr 18, 2018
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@JanisGailis JanisGailis

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JanisGailis