-
Notifications
You must be signed in to change notification settings - Fork 615
[2/2] Add Image Ops for Data Augmentation #1353
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
Comments
@gabrieldemarmiesse, @dynamicwebpaige does this issue is meaningfull for Tensorlfow. |
@vinayvr11 Closing #1342, create separate PRs for each op. |
Sure @Squadrick i will make seperate PR for all operations. |
@gabrieldemarmiesse The list does not contain Canny Edge detection. But it is useful functionality and is contained in almost all Standard image processing libraries. Should it be added? |
About image processing I think that we need to think about priorities:
In the first two case, as an example, see how many Opencv calculators (search for |
Per #1226 (comment) the autoaugment/randaugment features will be a part of https://github.com/keras-team/keras-cv Apologies for not being able to present this information sooner to the contributors. |
Part 1: #1333
As part of #1226, relevant image ops need to be added to
tfa.image
. List of ops tracked in this issue (tick the op only once the corresponding PR is merged):Reference: https://github.com/google-research/simclr/blob/master/data_util.py
The text was updated successfully, but these errors were encountered: