Fix poly_fit signature to work with ProcessingChain #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
poly_fitfactory function had an incorrectGUFuncWrappersignature"(n),(m)"which was parsed as 2 inputs / 0 outputs instead of 1 input / 1 output. This broke DSP configs usingpoly_fitwithbuild_dsp().Changes
"(n),(m)"→"(n)->(m)"to correctly indicate input/output dimensions["ff", "dd"]→["ff->f", "dd->d"]to match signature formatpoly_fit,poly_diff,poly_exp_rmsExample Configuration
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.