Resolve padding semantics in global dim data spec
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- distributed-systems
Research direction
Start by comparing the global dim data spec with the protocol's description of padding, using the 1D distarray example as the reference case. Resolve how communication padding and overlapping global index bounds should be represented, then document an agreed minimal specification with no duplicated data.
Written by the indexing model from the issue text.
Description
Padding support is currently spotty, so there are several places where it needs to be worked on. One area is in the global dim data spec and making it consistent with the protocol's description of padding. For instance, if communication padding is 2, then the global index bounds for a 1D distarray would be something like:
| Process | 0 | 1 |
|---|---|---|
| Padding | (0, 2) | (2, 0) |
| (start, stop) | (0, 13) | (9, 20) |
Note especially that the stop of process 0 is greater than the start of process 1.
Topic for discussion: how should this be specified in the global dim data? We'd like it to be straightforward, allow full control over how things are specified, and (ideally) minimal, so no data is duplicated.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 enthought/distarray
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in enthought/distarray
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·