O-9: distarray global API -- array expressions with partially overlapping arrays (optional)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- distributed-systems
Research direction
Start by clarifying the semantics for expressions combining partially overlapping distributed arrays, including result distribution and which nodes perform computation. Compare the desired behavior with NumPy functionality, then evaluate the communication-versus-computation tradeoffs and possible user controls such as decorators or context managers. Done means the ambiguities are resolved and an implementation direction is defined.
Written by the indexing model from the issue text.
Description
Objective: The goal of this sub-task is to define the semantics for distributed array expressions with arrays that are not identically distributed.
Relevance: Supporting array expressions when the component arrays are not identically distributed will allow ODIN to more closely align with NumPy’s functionality, will improve overall usability, and will more closely conform to what is expected for users coming from a NumPy background (i.e. the principle of least surprise).
Description: When partially overlapping distributed arrays are combined in an expression whose result is another distributed array, certain ambiguities arise: how should the result array be distributed? What nodes are responsible for the computation? In which circumstances is communication more costly than computation, and what heuristics can be devised to help guide these decisions at runtime?
Given these ambiguities, allowing end-user control in some form is a possible option to pursue, whether it be via decorators, context managers, or other mechanisms provided by Python control flow structures.
- 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
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100