Should sel with slice objects care about underlying coordinate order?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
If I have a xarray DataArray, that has x-coordinates in descending order, and I try to crop the DataArray using
da.sel(x=slice(10,50)), it gives me empty DataArray. If I use
da.sel(x=slice(50,10)), it finds everything it is supposed to find.
I think it would be useful to be able to use this feature without knowing the exact order of the DataArray. Is this intentional?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with a DataArray whose x-coordinates descend, comparing da.sel(x=slice(10,50)) with the reversed slice. The issue names no source file or test; done means establishing the intended slice semantics and verifying the behavior with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100