Thank you for your comment!
### **Reviewer's explanation on the contribution comment**
#### *Author response*:
Thank you for the response, and we appreciate that you recognize our hard work. We agree that our proposed reasoning may not be unique. However, we would like to emphasize the importance and relevance of this problem (self-supervised transformers, which have been the de facto choice of different research communities for learning from unlabeled data, as demonstrated by our experiments in NLP, CV, and Graph). We also hope that by observing and interpreting the problems, more people would notice this phenomenon and (potentially) other related phenomena in self-supervised transformers. We believe our observation and explanation are self-contained, and we propose a simple yet effective approach to mitigate the issue and demonstrate the empirical performance gains across various tasks. We will add more discussions in the future work section to point out potential extensions and follow-ups of our work.
### **Reviewer's clarification on the frequency question**
#### *Author response*:
Thank you for your clarification!
**Here is our short response**: We advocate treating [CLS]/[SEP] as different variables for other natural tokens.(by natural, we mean the token is originally in the dataset and not introduced heuristically, such as [CLS],[SEP]). But we do not think treating natural tokens differently based on their behavior (for instance, their frequency) is a good idea. While SepNorm works well in promoting representation quality, we agree that it is not the only solution separating the two kinds of variables, and other promising solutions may exist. We’d like to leave such work in the future. We think that apart from SepNorm, another contribution of our work is the finding that the two types of tokens should not share the same embedding space (through uniformity analysis). We hope the reviewer could agree on this.
Below we further elaborate on the reviewer's comments:
**(We advocate treating [CLS]/[SEP] as different variables (outliers) against other natural tokens.)**\
Your observation that “the improvement can come from a purely statistical effect of taking out statistical outliers, or recursive mean computation” is insightful. Your assumption that the [CLS] embeddings (outliers) do not belong to the intrinsic distribution of the other token embeddings aligns with our motivation. Our approach takes a further step and assumes those “outliers” belong to another distribution and access the uniformity of the “outliers” distribution.
**(treating natural tokens differently (as outliers) based on their behavior (for instance, their frequency) & biased fitting)**\
However, we do not feel it’s reasonable to identify “outliers” based on their frequency. Since stopwords like “the” and “a” are frequently observed in the data. Statistically, their high frequency will not bias the fitting of the normalizing parameter because such behavior is the nature of the data. On the contrary, adopting different treatments to those high-frequency may result in biased fitting. Such an argument does not apply to the [CLS]/[SEP] tokens! Since they are heuristics and not originally from the data. We further provide an ablation study that performs SepNorm on stopwords (collected from NLTK) such as “a”, “the”, and “are” tokens. The performance gain is marginal (74.04→74.18 on unsup. STS with BERT model).
**(Simple treatment that reweights contribution between [CLS] and other tokens)**\
The remark made by the reviewer that “one could scale the contribution of [CLS] proportionally (when updating the normalization statistics) to improve model performance” is a possible approach. Intuitively, such an approach can determine “the 'volume' the [CLS] token and the other tokens should occupy” by tunning the contribution coefficient. To do this, we increase the weight of the [CLS] token by L/2L (L=256) when optimizing the normalization statistics. Such an operation leads to a performance gain (see table below), but not as good as SepNorm. Moreover, further increasing the important weight might result in performance drops. We believe such an operation requires careful parameter selection to balance the two types of tokens. SepNorm directly separates them into two embedding spaces, ensuring they won’t “compete” for space.
| | ShareNorm | ShareNorm(L)| ShareNorm(2L)|SepNorm|
|-|:-:|:-:|:-:|:-:|
|**Accuracy**| 92.01 |92.75| 91.88| 93.84|
**(SepNorm on [SEP] token)**\
In response to the last comment about the [SEP] token, there is no harm in introducing SepNorm to it. *We believe such an operation may help promote the uniformity of the natural token embedding but the downstream improvement gain might be marginal*. Because [CLS] token may benefit less from it since it already has its normalization layer.
We thank you again for the clarification, and we hope we've answered all the questions. Please do not hesitate to ask if there are more questions.