Repository navigation
Fix: preserve flat FISTA cost dispatch for ND operators - #805
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
mrava87
left a comment
There was a problem hiding this comment.
@mikamikasuki well spotted and thanks for the PR. I left a few minor comments but overall I think is good (including the new test :))
|
@claude review. |
|
Claude finished @mrava87's task in 22s —— View job Review of PR #805
The fix is correct and minimal. Still open from the earlier reviewAll of the points below are still unaddressed. The branch has only the one commit.
Minor points
SummaryThe core change is good to merge once the four open points above are done. I made no code changes. |
|
Added the input-layout clarification to |
FISTA computed its data cost through
Op @ x, which reshapes output toOp.dimsdand fails against flattened multidimensional data or multiple right-hand sides. Use the solver's existingOpmatvecdispatch for the cost.Cover ISTA and FISTA with 16 regression cases across real/complex data, single/multiple right-hand sides, and both preallocation modes. Clarify the input layout in both public docstrings and the deblurring tutorial.
Fixes #801.
Validation:
pytest pytests/test_sparsity.py— 92 passed;make lint— passed.AI assistance: Codex authored the fix, documentation, and regression tests.