Register Unary OPs, forward pass #1296
Open
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
shutovilyaep
force-pushed
the
feat/register_unary_ops
branch
from
9e73143 to
b367849
Compare
…sts. Added functions to transform tensors between real and complex formats. Updated OpTestConfig to include pre- and post-operation transformations. Modified unary operation tests to validate complex support for 'angle' and 'conj' operations.
shutovilyaep
force-pushed
the
feat/register_unary_ops
branch
from
a78a1ab to
2484481
Compare
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.
Registering Unary TTNN OPs
Problem description
Existing TTNN OPs should be registered to Pytorch Dispatcher.
The scope of this PR is Unary OPs only, other groups of OPs are planned to be added in other PRs
[TODO: to update links when PRs are moved to "tenstorrent" organization]:
What's changed