-
Notifications
You must be signed in to change notification settings - Fork 7k
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
ConvNormActivation block for 3D convolutions #5430
Comments
In my opinion 2nd one is better. I can give a shot at this :) |
Thanks for the feedback @oke-aditya! I was thinking and discussing with @datumbox offline, and I'm inclined to the following solution:
The advantages of this approach is that we have a clear naming convention in line with the The major disadvantage is that the current |
Also, thank you for offering to give it a shot, let's just wait for some more feedback and then would be great if you wish to work on it! |
The approach sounds good to me. If you bring a separate PR, that does step 1, we should replace all existing uses in TorchVision and also do the same on the next fbsync for all FBcode internal cases. |
@oke-aditya I kicked off by renaming the |
Nice will do this over the weekend 😄 |
🚀 The feature
I suggest we add a
Conv3d
equivalent for theConvNormActivation
blockMotivation, pitch
This will be used in the upcoming ResNext3d implementation.
Alternatives
I see two possible alternatives:
We can re-purpose the existing method in a BC way by adding an extra named parameter
conv layer
with default value ofConv2D
.We can explicitly add a new class
Conv3DNormActivation
, which will be very similar to the existing one.Additional context
No response
The text was updated successfully, but these errors were encountered: