google-research / google-research/nested-transformer

Is the bulk of the convergence speedup from the ConvPool?!

Open
#12 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
204
Forks
27
PR merge metrics
No merged PRs in 30d

Description

Reading https://github.com/google-research/nested-transformer/blob/main/models/nest_net.py#L107 and
https://github.com/google-research/nested-transformer/blob/main/libml/self_attention.py#L266 there's a 3x3 convolution at each change in resolution (so 2 total).

Did you get a chance to do any ablation studies on this?

E.g. comparing using the current ConvPool (Conv2d 3x3, LayerNorm, MaxPool 2x2) vs e.g. a patch embed style convolution (Conv2d 2x2, stride=2), which wouldn't have as much "power" for modeling the image contents?

Or ablating the early transformer blocks? So it would be just PatchEmbed -> ConvPool -> ConvPool -> Transformers -> head?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.