Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Deprecate iris.analysis.calculus.curl #6262

Open
trexfeathers opened this issue Dec 17, 2024 · 1 comment
Open

Deprecate iris.analysis.calculus.curl #6262

trexfeathers opened this issue Dec 17, 2024 · 1 comment

Comments

@trexfeathers
Copy link
Contributor

trexfeathers commented Dec 17, 2024

📰 Custom Issue

The current developer core is uncomfortable with iris.analysis.calculus.curl remaining in Iris' API.

curl was introduced in the earliest days when we were speculating about where Iris would prove most valuable, but complex calculus did not become a 'growth area', putting curl in an unfortunate position of requiring a high level of esoteric knowledge to maintain, and being unlike most other Iris operations. This leaves our developers unfamiliar and out of practice, hence our difficulty answering questions, and the fact that several elements (e.g. 3-dimensional curl) have never functioned as advertised.

Compare this to something like regridding, which also requires a challenging level of specific knowledge, but is a heavily used Iris feature and therefore has dedicated resource/expertise at all times.

There are several ways forward:

  1. Seek a volunteer with the right expertise to maintain curl in Iris. There is even potential for this to expand into a larger satellite project with more calculus conveniences. (see Plugins).
  2. Deprecate the curl function and convert the code into a detailed documentation example. This avoids the current implication that this is a maintained part of Iris, and leaves users to customise in whichever way works for them.
  3. Deprecate the curl function and recommend people use MetPy's curl instead. MetPy would need to be included in environments at the UK Met Office.
@trexfeathers
Copy link
Contributor Author

After posting this internally at the UK Met Office on 20th November, so far no volunteers have come forward. So it's currently looking like Options 2 or 3 above.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant