-
Notifications
You must be signed in to change notification settings - Fork 23
Fix for subspacing with cyclic cf.wi and cf.wo arguments
#925
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
Merged
davidhassell
merged 2 commits into
NCAS-CMS:main
from
davidhassell:fix-cyclic-subspace-2
Feb 24, 2026
+80
−11
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code block does the job and sensibly so, but I feel like it would be better to pull out at least the core period-based boundary wrangling as a separate method, perhaps internal but I think could easily be argued as a useful one for users, that would 'normalise' queries for a given period. I notice we, at least (just from a
git grep period), use some quite similar logic in thedimensioncoordinatemodule:cf-python/cf/dimensioncoordinate.py
Lines 363 to 384 in bb01e7c
and it already quite close to what the
anchormethod does, plus in general it sounds like the kind of thing we'd possibly need to do in various places, so better to have it self-contained and reusable and ideally reduce use of similar logic elsewhere by replacing with a call to the new method.So I suggest a new mixin method
normalise_rangeornormalise_queryor similar (probably there's a better name to be determined). What do you think? (It could always be marked as follow-on work to consolidate, if you'd prefer in the interests of the backlog of work/reviewing we have to get through for the new release not to update this PR.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this idea, but I think the various use cases might be a subtly different to make putting it in here a "quick" job. Let's follow this up in a another issue, like you suggest. I'm wondering if a function in
cf.functionswould be a good way to go.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that's fair enough - indeed it might need some thinking in terms of the best way to consolidate things. Let's raise an Issue after we merge this (I can do it if that's easiest).