Response to Reviewer LtSJ (1/2)
Thanks for your comments and suggestions. We hope the following clarifications help to address your concerns.
**[Q1:]** How would the adapters work with other (smaller) models?
**[A1:]** The adapters can work with smaller models in the way described in the paper and achieve good performance. But it only makes sense if this model is pre-trained on a large amount of data and produces well-generalized representations. Otherwise, we can directly fully fine-tune the model. Here we provide the results (only fine-tuning the model on Pitts30k and testing on Pitts30k) of our adaptation method using a distilled version of DINOv2 (based on ViT-Base) as backbone, denoted as DINOv2-B. The DINOv2-L (based on ViT-Large) is the backbone used in our paper. Their performances are close, demonstrating that our adaptation method can be used with smaller models.
| Backbone | R@1 | R@5 | R@10 |
| :---: | :---: | :---: | :---: |
| DINOv2-L | 91.4 | 96.5 | 97.8 |
| DINOv2-B | 90.5 | 96.1 |97.1 |
**[Q2:]** What are the reasons why the proposed adapters work?
**[A2:]** Although visual foundation models can provide powerful feature representations, the objects that need to be focused on may be different for various downstream tasks. Freezing the foundation model can retain the powerful representation capabilities, while inserting the lightweight trainable adapters so that the entire model can be adapted to the VPR task after fine-tuning on VPR datasets, that is, the trained adapter has learned VPR-related knowledge. Our visualization results well illustrate that the adapted model can focus on objects that are helpful for place recognition and ignore dynamic foreground interference, which is the key reason for its good performance. Meanwhile, our hybrid adaptation method combines global adaptation and local adaptation, which not only yields a robust global representation, but also enables the model to output dense local features for spatial matching re-ranking, thereby further boosting performance.
**[Q3:]** How the adapter parameter space influences the improve of performance, and how does it relate with 'smaller' backbones.
**[A3:]** The number of parameters of the adapter in our global adaptation is adjustable. Appropriately increasing the parameters of the adapter can slightly improve performance. However, in most cases, we can actually use a very lightweight adapter to obtain good performance. In the Appendix.C of our paper, we have shown the results of using only one adapter in each transformer block or reducing the bottleneck ratio to 0.25, and the performance is still good. Here, we provide the results (on Pitts30k) of using only the parallel adapter and reducing the bottleneck ratio from 0.5 (in the paper) to 0.05, as shown in the table below (SelaVPR** uses the more lightweight adapter. SelaVPR represents the original setup in paper). The SelaVPR** has only 5.19M trainable parameters (less than most methods), and the results are still excellent. For smaller backbones, fewer transformer blocks and lower token dimensions will naturally lead to fewer parameters of the adapter. Overall, the original paper focused more on recognition performance without excessively limiting the number of parameters. In fact, our method can achieve good performance using a significantly smaller number of parameters.
| Method | Tunable Param (M) | R@1 | R@5 | R@10 |
| :--- | :---: | :---: | :---: | :---: |
| ResNet50-GeM | 7 | 82.3 | 91.9 | 94.6 |
| SelaVPR | 53 | 91.4 | 96.5 | 97.8 |
| SelaVPR** | 5 | 91.2 | 96.4 | 97.4 |