lxtGH / lxtGH/OctaveConv_pytorch
Bug and error in Octave conv
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 581
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
When I used the model in libs/nn/OCtaveResnet.py, I found tow things.
One is the stride of last Bottleneck is 2, which cause bug when using this model, because the input size of last Bottleneck is 1414 and 77, and after conv block of stride=2, there will be two tensor, 66 and 77 which can not be added together, bug comes. Setting the stride of last Bottleneck equals to 1 will solve this bug, with a little change of resnet.
Another one is about stride of Octaveconv2.py. I found that when stride=2, you still used conv layer with stride=1, and implement pooing(stride=2) before ocnv layer instead, which is totally different from conv layer with stride=2. I think the latter one is what author do in original paper.
Still, thanks for sharing your work!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with libs/nn/OCtaveResnet.py and Octaveconv2.py, checking the final Bottleneck tensor sizes and how stride=2 is handled. Compare the Octave convolution stride behavior with the original paper, then verify that the model runs without the reported shape mismatch and that the stride implementation matches the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100