Mods to eos.py to improve dask compatibility #149
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pushed a commit to support |
|
Hi @mnlevy1981 , I'm wondering if this PR might get merged in the next iteration of pop-tools? This would be really useful to speed up some work that I'm doing that utilizes this functionality to create AMOC sigma diagnostics. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The proposed mods allow depth to be passed to
eos()as a simple 0-dimensional xarray DataArray, e.g.depth=xr.DataArray(2000)This is required if
saltandtempargs are DataArrays, but currently errors can arise ifdepthis 0-dimensional. Mods also improve performance ifsaltandtempare dask arrays by eliminating the unnecessary triple broadcasting ofsalt,temp, andpressure. The modifiedeos()works well for dask-enabled computation of MOC in sigma coordinates (https://github.com/sgyeager/POP_MOC).