Fix gradient double-counting in ScalarOperator compositions #307
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.
Summary
Fixes gradient double-counting issue where operator-based and matrix-based formulations of the same
LinearProblemproduced different gradients. The operator-based gradient was exactly twice the matrix-based one.Problem
When
ScalarOperatorwith parameter-dependent update functions were used inScaledOperatorcompositions (e.g.,Func * A2), Zygote was double-counting gradients because:This created exactly 2× the expected gradient, causing incorrect sensitivities in automatic differentiation.
Solution
SciMLOperatorsChainRulesCoreExtwith targetedrruleforScaledOperatorconstructorrrulecarefully manages the pullback to avoid structural dependency double-countingTesting
Original MWE (now passes)
Test Coverage
Files Changed
Project.toml- Added ChainRulesCore as weak dependencyext/SciMLOperatorsChainRulesCoreExt.jl- New ChainRules extension with fixtest/chainrules.jl- Comprehensive tests for the fixImpact
Before/After Comparison
Before (❌ Incorrect):
After (✅ Correct):
Fixes #305
🤖 Generated with Claude Code