TF Addons CV components
See original GitHub issueAre you interested to cover or migrate some of the CV components in the TF Addons namespace?
I suppose the starting point could be to review tf.addons.image
as we are already duplicated in this repo things like coutout/randomcoutout etc…:
https://www.tensorflow.org/addons/api_docs/python/tfa/image
P.s. This is a parallel ticket of https://github.com/keras-team/keras-nlp/issues/11
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (11 by maintainers)
Top Results From Across the Web
TensorFlow Addons
A library of useful extra functionality for TensorFlow maintained by SIG-addons with community contributions that conform to well-established API patterns.
Read more >tensorflow/addons: Useful extra functionality for ... - GitHub
TensorFlow Addons is a repository of contributions that conform to well-established API patterns, but implement new functionality not available in core ...
Read more >Plugins - VCV Library
Subscribe Unsubscribe Add all. Remove all 2.0.25 3 days ago
Add Remove Meander Add Remove Meander
Subscribe Unsubscribe Add all. Remove all 2.0.4 3 days...
Read more >Custom Operations Guide - OpenVINO™ Documentation
Implement a customer operation in one of the Inference Engine plugins to support inference of this operation using a particular target hardware (CPU,...
Read more >A Vision Transformer without Attention - Keras
Vision Transformers (ViTs) have sparked a wave of research at the intersection of Transformers and Computer Vision (CV).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you close this one that it is general enough then I need to post to every specific ticket or PR that is going to create any sort of potential duplication with Addons like https://github.com/keras-team/keras-cv/issues/289.
I honestly avoided doing this on every single ticket in these months cause I was thinking that we could sit down and calmly assess the situation as we have already “duplicated” or superseded many components here since February.
But we have not collected any specific position after 2 months and it’s a bit of a waste of resources.
https://github.com/tensorflow/tensorflow/issues/55824