10000 Implement ufuncs and gufunc for array-expr by phofl · Pull Request #11818 · dask/dask · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Implement ufuncs and gufunc for array-expr #11818

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

Merged
merged 34 commits into from
Apr 23, 2025
Merged

Conversation

phofl
Copy link
Collaborator
@phofl phofl commented Mar 7, 2025
  • Closes #xxxx
  • Tests added / passed
  • Passes pre-commit run --all-files

This adds support for ufuncs and gufunc and passes all tests

@phofl phofl mentioned this pull request Mar 7, 2025
3 tasks
Copy link
Contributor
github-actions bot commented Mar 7, 2025

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

      9 files  ±0        9 suites  ±0   3h 19m 32s ⏱️ + 3m 37s
 18 010 tests ±0   16 796 ✅ ±0   1 214 💤 ±0  0 ❌ ±0 
161 164 runs  ±0  149 058 ✅  - 2  12 106 💤 +2  0 ❌ ±0 

Results for commit 4f279bb. ± Comparison against base commit 913026f.

♻️ This comment has been updated with latest results.

@mrocklin
Copy link
Member
mrocklin commented Mar 7, 2025

Cool

@a-holm
Copy link
a-holm commented Mar 30, 2025

Would be great if the PR description could be expanded to detail which ufuncs/gufuncs are now supported, mention the known limitations (like the numba issues causing xfails), and explicitly state whether new tests were added or if only existing tests were adapted.

Would also be cool if you added module-level docstrings to _gufunc.py and _ufunc.py explaining their purpose. Add docstrings to key classes like ufunc, GUfuncLeafExpr, and potentially complex functions like apply_gufunc. Explain the minor changes in _blockwise.py, _expr.py, and _io.py in the PR description or code comments. Explain the name parameter added to from_array. The logic for handling gufunc signatures, axes, broadcasting, and potential vectorization is inherently complex.

Also the xfail markers in test_gufunc.py. Are these acceptable known limitations, or will they be fixed?

@fjetter fjetter merged commit ef66102 into dask:main Apr 23, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0