Skip to content
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

Change DepthwiseConv() to use in=>out instead of in=>mult. #756

Merged
merged 3 commits into from
May 13, 2019

Conversation

staticfloat
Copy link
Contributor

This is an API change, but I think it makes more sense, and is more consistent with our Conv() API. This also dumps the DepthwiseConv((3,3), C_in) API, as I'm not sure why you would want to specify only the input channel count and default the output to a channel multiplier of 1; if anything I would think you'd want to specify the channel output and leave the input to be default. In any case, I think consistency with Conv() is the best thing to chase after here.

@staticfloat staticfloat force-pushed the sf/depthwise_inout branch 3 times, most recently from 02571db to 77af671 Compare April 26, 2019 22:36
@MikeInnes
Copy link
Member

Agreed on all counts. Especially with leaving out the input channel; we should prepare our APIs for this so we can eventually do #703.

It's just a shame we can't deprecate this. But I guess for the most part people will get a fairly obvious shape error, if not an assertion error.

@MikeInnes
Copy link
Member

Oh, worth adding a news item for this though!

staticfloat added a commit that referenced this pull request Apr 30, 2019
@staticfloat
Copy link
Contributor Author

Anything else to do here?

This is an API change, but I think it makes more sense, and is more
consistent with our `Conv()` api.
@DhairyaLGandhi
Copy link
Member

Lgtm

@MikeInnes
Copy link
Member

bors r+

bors bot added a commit that referenced this pull request May 13, 2019
756: Change `DepthwiseConv()` to use `in=>out` instead of `in=>mult`. r=MikeInnes a=staticfloat

This is an API change, but I think it makes more sense, and is more consistent with our `Conv()` API.  This also dumps the `DepthwiseConv((3,3), C_in)` API, as I'm not sure why you would want to specify only the input channel count and default the output to a channel multiplier of 1; if anything I would think you'd want to specify the channel output and leave the input to be default.  In any case, I think consistency with `Conv()` is the best thing to chase after here.

Co-authored-by: Elliot Saba <staticfloat@gmail.com>
@bors
Copy link
Contributor

bors bot commented May 13, 2019

Build succeeded

@bors bors bot merged commit 06da965 into master May 13, 2019
@CarloLucibello CarloLucibello deleted the sf/depthwise_inout branch April 7, 2022 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants