-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RawOps Operations for TensorFlow frontend #1565
Labels
hacktoberfest
hacktoberfest
TensorFlow Frontend
Developing the TensorFlow Frontend, checklist triggered by commenting add_frontend_checklist
ToDo
A ToDo list of tasks
Comments
Closed
_[ ]# 26768 (ScatterNd) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
hacktoberfest
hacktoberfest
TensorFlow Frontend
Developing the TensorFlow Frontend, checklist triggered by commenting add_frontend_checklist
ToDo
A ToDo list of tasks
Add RawOps Operations for TensorFlow frontend:
Note: If the RawOps function to be implemented has identical behavior to an existing TF frontend function (Eg: https://github.com/unifyai/ivy/blob/36a346b2cccb5317a00106d147f7d642f3c65870/ivy/functional/frontends/tensorflow/math.py#L259 and https://github.com/unifyai/ivy/blob/36a346b2cccb5317a00106d147f7d642f3c65870/ivy/functional/frontends/tensorflow/raw_ops.py#L195
you should simply keep an alias in the raw ops file rather than creating a duplicate implementation. For the above example, this would mean simply writing https://github.com/unifyai/ivy/blob/ba9eaeca32617486e10882f7dfe6b6c61ceb0235/ivy/functional/frontends/tensorflow/raw_ops.py#L368 instead of a full function definition.
The task of determining whether a function needs to be an alias or not should be done based on the docstring, the arguments, and/or the behaviour of the function and its similar counterpart.
_
Please keep in mind that the proper way to link an issue to this list is to comment "- [ ] #issue_number" while the issue's title only includes the name of the function you've chosen.
_
The main file paths where these functions are likely to be added are:
ivy/functional/frontends/tensorflow/raw\_ops.py
ivy\_tests/test\_ivy/test\_frontends/test\_tensorflow/test\_raw\_ops.py
ivy/functional/frontends/tensorflow/math.py
ivy\_tests/test\_ivy/test\_frontends/test\_tensorflow/test\_math.py
ivy\_tests/test\_ivy/helpers.py
ivy\_tests/test\_ivy/test\_functional/test\_core/test\_dtype.py
ivy/functional/frontends/tensorflow/\_\_init\_\_.py
ivy/functional/frontends/tensorflow/activations.py
ivy/functional/frontends/tensorflow/layers.py
ivy/functional/frontends/tensorflow/linalg.py
ivy/functional/frontends/tensorflow/metrics.py
ivy/functional/frontends/tensorflow/nest.py
ivy/functional/frontends/tensorflow/nn.py
ivy/functional/frontends/tensorflow/quantization.py
ivy/functional/frontends/tensorflow/random.py
ivy/functional/frontends/tensorflow/regularizers.py
ivy/functional/frontends/tensorflow/sets.py
ivy/functional/frontends/tensorflow/signal.py
ivy/functional/frontends/tensorflow/sparse.py
The text was updated successfully, but these errors were encountered: