Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add upsample layer which is faster than the current deconvolution implementation. In my GTX-970, it's almost 6x faster than the current deconvolution way.
For example, to upsample (2x) the input in the deconvolution way. We have to define the following.
And test the forward time by built-in caffe tools.
this shows me the forward time in the deconvolution layer
It seems to me that it's worth to implement an upsample layer which is much faster than deconvolution.
Here is an use case. It's also worth noting that the parameters are much simpler.
and this is really fast.
The other difference is that upsample layer implements
Nearest Neighborhood
, but deConvolution implementsBi-Linear
. However, in my experiment in FPN (https://arxiv.org/abs/1612.03144), it does not affect the accuracy no matter what algorithm you choose.