-
Notifications
You must be signed in to change notification settings - Fork 615
Image Processing Operations #358
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
Hi Parth,
Thank you! |
@WindQAQ, Thanks for notifying me on this one, I'll remove the Averaging filter part from the notebook. |
Hi Parth, do you have any information on some of these being using in a ML pipeline? I'm afraid it's hard to justify all standard image operations becoming part of Addons. I think we could work in most of these if we had a solid use case (e.g. image preprocessing for pathology). Perhaps if you could update these examples to show how they can be used in a regression problem... how many cells per image or something |
@parth-p Could you go ahead and submit a PR for thresholding methods? |
In addition to the previous image operations, I have implemented a few more operations:
Also, there is an update in the implementation of canny edge detector. |
We are making a catalog of some useful image ops for AutoAugmentation policies at #1333. Probably some ops could be useful also in post-processing tasks as i.e. Mediapipe heavly use Opencv operation in postprocessing calculators. See google-ai-edge/mediapipe#515 |
Closing this issue due to lack of activity. Discuss on #1333, that seems to have grown into the mega-thread for all things image proc. |
System information
Describe the feature and the current behavior/state.
I am proposing the following image operations:
The text was updated successfully, but these errors were encountered: