-
Notifications
You must be signed in to change notification settings - Fork 10
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
Usage of xarray ufuncs is deprecated #183
Comments
@jgrss is it possible to downgrade |
Yes, you can use current version of geowombat with: pip install xarray==2022.3.0 |
The following workaround solved the problem for me, but maybe this is not a really good solution.
In the given file I commented the lines 26 & 27 out (see above) and changed the xarray min/max function to
|
Finally, after a bit of back and forth, I was able to freshly install Thank you @mattijn |
@jgrss just opened a pull request to resolve this. |
@mmann1123 What is the status of PR #186? Was it closed because we had discussed using the fixes in jgrss/store? |
Thanks for comfirming this, @mattijn -- a branch in the waiting that should push geowombat to |
@jgrss I intended PR #186 to resolve the ufunc issues but then some tests were failing in ML and another elsewhere, I was worried I had inadvertently pushed some old ML code, so closed it. But I think we need to push the jgrss/store. I will try to test it today, but its first day of classes so things are busy. Might be a few days. But I figure jgrss/store can't make things worse - since people can't write out files - and would likely fix things. But I defer to you on that. |
Should be addressed with #189. |
Xarray has removed support for the deprecated
xarray.ufuncs
functions since versionv2022.06.rc0
: https://docs.xarray.dev/en/stable/whats-new.html#breaking-changes.Now I receive the following error:
Searching the repo: https://github.com/jgrss/geowombat/search?q=xarray.ufuncs&type=code
Reveals at least one file needs updating:
geowombat/src/geowombat/backends/xarray_.py
Lines 26 to 27 in 342bb2b
Linked issue: #42
The text was updated successfully, but these errors were encountered: