Cube arithmetic points/bounds mismatch errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Review the cube arithmetic validation work referenced in #3774 and the coordinate mismatch example linked from #2599. Determine where the exception is raised and how coordinate points and bounds are compared. Done means one error reports all mismatches and indicates the magnitude of each difference.
Written by the indexing model from the issue text.
Description
Following on from the outstanding cube arithmetic work, some thoughts/ideas about the exception that gets raised if our coordinate points or bounds don't match.
-
1. As already noted in #3774, it would be good to check all the coordinates and then raise an exception indicating the mismatches in all of them. This would allow the user to fix the issue all at once, rather than potentially going through several run code --> fix coords loops.
-
2. It would be handy to get an indication of how different the coordinates are. E.g., for example 3 in my comment here, if the error message tells my that all the points are out by three hours, I can think "that's fine given what I know about the data" and do some wrangling to get the points checking to pass. If, on the other hand, I get a message saying that latitude points are out by "up to 180 degrees", I know something has gone properly wrong. This happened to me previously as I didn't realise that Windspharm enforces a latitude direction.
I'd be happy to have a go at these myself, assuming I can find the time.
- Dominant language
- Python
- Stars
- 724
- Forks
- 317
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 9
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.
More from SciTools/iris
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100