Closed cofri closed 2 years ago
This PR introduces a new PadConv2D layer that is the combination of a padding operation and a Conv2D layer. Different padding types can be set:
PadConv2D
tf.pad()
Moreover, some bugs are fixed and unit tests are added.
As PadConv2D is not lipschitz constrained, we need to find a way to make sure that users are aware of it. Should we move it to a separate module for instance ?
This PR introduces a new
PadConv2D
layer that is the combination of a padding operation and a Conv2D layer. Different padding types can be set:tf.pad()
. The output shape is equal to the input shape.Moreover, some bugs are fixed and unit tests are added.