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

Issues with xarray v0.14 #1203

Closed
3 tasks
zbruick opened this issue Oct 15, 2019 · 8 comments
Closed
3 tasks

Issues with xarray v0.14 #1203

zbruick opened this issue Oct 15, 2019 · 8 comments
Labels
Area: IO Pertains to reading data Area: Xarray Pertains to xarray integration Type: Bug Something is not working like it should
Milestone

Comments

@zbruick
Copy link
Contributor

zbruick commented Oct 15, 2019

Another xarray release, another round of broken tests. Main issues are:

  • AttributeError: 'GiniFile' object has no attribute 'tell' (several test failures)
  • AssertionError on test_narr_example_variable_without_grid_mapping
  • AssertionError on test_dataset_parse_cf_varname_list
@zbruick zbruick added Type: Bug Something is not working like it should Area: IO Pertains to reading data Area: Xarray Pertains to xarray integration labels Oct 15, 2019
@zbruick zbruick added this to the 0.11.1 milestone Oct 15, 2019
@jthielen
Copy link
Collaborator

jthielen commented Oct 15, 2019

The GiniFile errors appear to have arose from pydata/xarray#3389.

The assertion errors for test_narr_example_variable_without_grid_mapping and test_dataset_parse_cf_varname_list look to be the same error—a doubling of the 'x' coordinate's shape as pointed out in the comment in test_narr_example_variable_without_grid_mapping. This arose with the changes in pydata/xarray#3234, but what exactly in that PR, I'm not sure yet.

@kgoebber
Copy link
Collaborator

Is it worth starting to test on xarray master to get ahead of some of these changes due to our reliance on xarray for our data model?

@jthielen
Copy link
Collaborator

@kgoebber We already do: #1144.

@zbruick
Copy link
Contributor Author

zbruick commented Oct 15, 2019

I haven't gone back to look at those builds since we started them...should have been doing this. I'll keep digging and see if I can get a PR up today to fix this so that we can get 0.11.1 out the door.

@zbruick
Copy link
Contributor Author

zbruick commented Oct 15, 2019

@jthielen, looks like your fix in 2fe00b6 isn't having the correct effect anymore. You know this code better than the rest of us...any quick fix you see?

@jthielen
Copy link
Collaborator

@zbruick I found a quick fix that resolves the issue on MetPy's end (see #1206), but I still can't figure out what went wrong in the first place. I think there is an upstream issue with the way the Dataset constructor used in Dataset.apply combines coordinates/indexes after pydata/xarray#3389 that conflicts with the unit conversion MetPy does...but I can't quite track it down yet (or be totally confident it is all upstream and not a problem with MetPy's coordinate unit conversion).

@zbruick
Copy link
Contributor Author

zbruick commented Oct 15, 2019

Thanks @jthielen for the quick fix...interesting bug here. Hopefully between #1204 and #1206 we have this taken care of now.

@zbruick
Copy link
Contributor Author

zbruick commented Oct 17, 2019

With #1204 and #1206 being merged, this issue is resolved.

@zbruick zbruick closed this as completed Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: IO Pertains to reading data Area: Xarray Pertains to xarray integration Type: Bug Something is not working like it should
Projects
None yet
Development

No branches or pull requests

3 participants