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.
DataArray: propagate index coordinates with non-array dimensions #10116
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
base: main
Are you sure you want to change the base?
DataArray: propagate index coordinates with non-array dimensions #10116
Changes from all commits
f93b45a
01fc5fd
75b9ae5
b647df7
90ce0f9
ebcfa22
f27f2d0
528f356
27a1e38
695fb86
eea90cf
bc578d8
5e8093b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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'm having a hard time following the logic in this loop. Could you please separate it into two separate loops:
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.
Probably even better checking indexes and non-indexed coordinates in two separate loops, as you suggests in #10116 (comment).
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.
If I understand correctly, the only case in which a dimension is in
skip_check_dim_size
is when it is defined only on an index, in which case it won't appear insizes
.In that case, I think we could simplify this by checking
sizes
instead of creating theskip_check_dim_size
set: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.
Coud this use a separate loop after the existing loop instead? e.g.,
Or if we allow indexes without a coordinate of the same name:
Ideally, I would like the logic here to be just as simple as the words describing how it works, so a comment is not necessary!
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.
Are the variables in
_coords
different from those on.coords
? I'm surprised this is still true now...We should add one more invariant: something like "a dimension in
da.coords.dims
must be inda.dims
or be associated with an index associated with a dimension inda.dims
"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.
Good catch! The tests I added compare Coordinates objects, which thus skip this invariant check that we indeed need to update.