-
Notifications
You must be signed in to change notification settings - Fork 7.1k
[proto] Draft for Transforms API v2 #6205
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
Conversation
- Added H/V flip ops - Added resize op - Added center_crop
Other nits
…ision into proto-transforms-api-oo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking cool so far. Just a few questions:
# Just output itself | ||
# How dangerous to do this instead of raising an error ? | ||
return self |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would raise a "not implemented" error here and implement no-op explicitly on the implementations. So if bbox can't blur, then it should explicitly implement to be no-op as opposed to leaving the default implementation which returns self. Could help us avoid issues but if you disagree I'm happy to leave as-is and discuss later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that raising NotImplemented
could be good. The only drawback I found that all targets features like Label
, OneHotLabel
should also implement explicitly these no-ops. From the first glance, implementing all methods like OneHotLabel.blur(self, *args, **kwargs)
as no-op made me think that it is a bit too much...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to you. I've added this for your consideration. Feel free to ignore or postpone for later.
Closed in favor of #6305 |
A draft for Transforms API v2