Standardizing and generalizing object-oriented transformations#628
Merged
chaoming0625 merged 16 commits intomasterfrom Feb 22, 2024
Merged
Standardizing and generalizing object-oriented transformations#628chaoming0625 merged 16 commits intomasterfrom
chaoming0625 merged 16 commits intomasterfrom
Conversation
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.
This PR standardizes the customization of object-oriented transformations. The key is using
brainpy.math.VariableStackandbrainpy.math.eval_shape.One OO transformation involves two steps. The first step is using
brainpy.math.eval_shapeto evaluate allVariables used in the target function. The second step is the actual compilation phase, to compile the model on the given target device.For example, to customize an object-oriented JIT compilation interface, we can use: