fix(adjoint): optional argument for postprocess_adj for backend #3277
+1
−2
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.
Optional argument for when this is imported by the backend for the adjoint pipeline
updated emulated_run in unit test to catch a regression for this
(reposting because of error in branch name for jira)
Note
Low Risk
Low risk: a small signature/default-argument change plus a test update, with no change to adjoint computation logic beyond allowing omitted
custom_vjp.Overview
Adjoint postprocessing no longer requires
custom_vjp.postprocess_adjnow defaultscustom_vjptoNone, allowing callers (including backend imports) to omit the parameter.Tests updated to prevent regression. The autograd emulation unit test stops passing
custom_vjp=Noneexplicitly, ensuring the defaulted call path is exercised.Written by Cursor Bugbot for commit d1ef0f7. This will update automatically on new commits. Configure here.