Rename torch types #284
Merged
Rename torch types #284
Conversation
This file contains 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
Merged
nix-apollo
reviewed
Jan 17, 2024
nix-apollo
reviewed
Jan 17, 2024
nix-apollo
reviewed
Jan 17, 2024
nix-apollo
approved these changes
Jan 17, 2024
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.
Rename torch types
NOTE: I recently turned CI off for PRs pointing at feature/unify because I was expecting to merge, but the --runslow tests pass on my machine
Description
Renames torch types. The most frequent changes are:
as well as other changes that replace "hidden" with "orig" for dimensions that refer to the concatenation of inputs/outputs over their final dimensions, and "hidden" with "emb" for the final dimension of a single input/output of a module.
Does this PR introduce a breaking change?
No