Conversation
Developed and generalized version
Updated the Project and removed the additional dep
N-dimensional generalization
Developement
Hossein's recent developements (adding affine transformations and optimizations) -Merged by Hossein-
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.
Summary
This PR refactors and extends the transformation implementation in
DataToFunctions.jl.Main changes
EvalMultiPoly.jlChainRulesCore.jlreverse rules for affine and polynomial parametersCUDA.jlas a package dependencyAdapt.jlOptim.jl/LBFGSDocumenter.jldocumentation and tutorialPerformance
The in-place affine and polynomial CPU paths can run with zero heap allocations after compilation.
Polynomial reverse-mode differentiation now uses a custom VJP (Vector-Jacobian Product) rather than tracing the full pixel-wise computation.
Compatibility
The existing public transformation interfaces are retained, including the legacy compatibility API.