Make ConvLayerGrad usable on its own as a transposed convolution - #102
Merged
jessegrabowski merged 6 commits intoAug 23, 2026
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #102 +/- ##
==========================================
- Coverage 97.89% 97.51% -0.39%
==========================================
Files 59 59
Lines 2856 2938 +82
==========================================
+ Hits 2796 2865 +69
- Misses 60 73 +13 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Inductor could not resolve shapes through the nested autograd tape the previous form built, failing the transposed-convolution gradient test with `cannot determine truth value of Relational`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A transposed convolution is the input gradient of a forward one, so
ConvLayerGradalready computes it. Using it that way didn't work: it always computed the kernel gradient too, and differentiating it hitOpFromGraph's default pullback, which builds an anonymous op only numba can run.It now returns either gradient alone, a rewrite drops whichever has no clients, and its own pullback is written as
ConvLayerand one-sidedConvLayerGradcalls so every backend dispatches it. TheConvTransposelayers come next.