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

Enable lazy evaluation in iris.analysis.cartography.rotate_winds #4943

Closed
tinyendian opened this issue Sep 6, 2022 Discussed in #4934 · 2 comments
Closed

Enable lazy evaluation in iris.analysis.cartography.rotate_winds #4943

tinyendian opened this issue Sep 6, 2022 Discussed in #4934 · 2 comments
Labels
Stale A stale issue/pull-request

Comments

@tinyendian
Copy link
Contributor

Discussed in #4934

Originally posted by tinyendian August 26, 2022
Dear Iris developers,

I am currently working on enabling out-of-core computation in a file format conversion tool that uses Iris to load CF-netCDF data. Everything is working fine, including Iris regridding, but I noticed that the rotate_winds function in the cartography module is not currently lazy evaluation-enabled, so it will force wind field cube data to be loaded.

With a few straightforward modifications, I was able to enable lazy evaluation, including array masking. So I was wondering if there is any interest in this? I'd be happy to contribute an issue and pull request with the necessary changes. There seem to be more functions in the cartography module without lazy evaluation, though.

As per @pp-mo's comment, a pull request with the required changes for enabling lazy evaluation would be welcome, so I'll create one soon.

Copy link
Contributor

In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity.

If this issue is still important to you, then please comment on this issue and the stale label will be removed.

Otherwise this issue will be automatically closed in 28 days time.

@github-actions github-actions bot added the Stale A stale issue/pull-request label Jan 20, 2024
@trexfeathers
Copy link
Contributor

This was closed by #4972

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale A stale issue/pull-request
Projects
None yet
Development

No branches or pull requests

2 participants