Response to Reviewer tsUS
We sincerely thank the reviewer for their time and efforts in reviewing our work and providing valuable feedback that can further strengthen our manuscript. Below please find our detailed responses:
> **Throughput comparison on other platforms**
We have added additional throughput comparison on different platforms such as V100, TITAN RTX and A6000 GPUs, Jetson Nano
and Intel(R) Xeon(R) E5-2698 v4 CPU. For all comparisons, we show that FasterViT achieves a Pareto-front in for ImageNet Top-1 and throughput trade-off, hence validating the effectiveness and scalability of our model to different hardware platforms.
In V100 ([Figure](https://drive.google.com/file/d/1FP0pDnZMdxw2Sy0z1tX-8A54T6eKD0cq/view?usp=sharing)) or TITAN RTX ([Figure](https://drive.google.com/file/d/1elnLkDMM5s2ch-E5MKb5YDj1vV_Rsx1s/view?usp=sharing)) comparisons for instance, we observe a strong performance for all FasterViT models. Even on CPU ([Figure](https://drive.google.com/file/d/1iVsev1XxgNaFEgFrhV0i4lGO-Fldl3z9/view?usp=sharing)), FasterViT still outperforms competitors by a significant margin.
Please see the supplementary materials of the revised manuscript for all the figures regarding throughput and Top-1 accuracy.
> **Additional Downstream Benchmarks**
We thank the reviewer for their comment. We provide additional experiments for both object detection and semantic segmentation with more models, across different sizes, to demonstrate the effectiveness and efficiency of our work.
Firstly, we present additional object detection experiments with DINO on MS-COCO dataset as shown below:
| Backbone |Model|AP_box |Throughput
|-------------------|----------------|---------------|---------------|
|Swin-L |HTC++ |57.1|-|
|Swin-L |DINO|58.5|71|
|**FasterViT-4**|DINO|58.7|84|
The DINO model with FasterViT-4 is 18.30% faster than its counterpart with Swin-L backbone in terms of image throughput and outperforms it by +0.1 in terms of box AP.
We also added a semantic segmentation study on the ADE20K dataset with the FPN network, as shown below. Specifically, we compare against PoolFormer and PVT backbones:
| Backbone |Model|mIoU |Throughput
|-------------------|----------------|---------------|---------------|
|PoolFomer-S36 |FPN |42.0|453|
|**FasterViT-1**|FPN|42.7|491|
|PoolFomer-M36 |FPN |42.4|368|
|**FasterViT-2**|FPN|43.5|405|
The model with FasterViT-1 backbone outperforms counterpart PoolFormer-S36 by +0.7 in terms of mIoU while also being 8.38% faster in terms of image throughput. Similarly, the model with FasterViT-2 backbone significantly outperforms PoolFomer-M36 counterpart by +1.1 in terms of mIOU while being 10.05% faster.
We believe that the above experiments validate the effectiveness of FasterViT as an efficient backbone for downstream tasks such as segmentation and detection across different model sizes.
> **How does latency change with respect to change of HAT parameters**
Thank you for your question. We have conducted an additional ablation study to investigate the effect of HAT hyperparameters on the latency and accuracy of the model. Specifically, we examine the effect of window size (W) and carrier token window size (W_C) as shown below for 224x224 resolution. We use FasterViT-2 with 7x7 window size and 2x2 carrier token window size as the base model. Latency ratio is measured against this base model.
| Resolution |Window Size|Carrier Token Window Size |Latency Ratio|Top1|
|-------------------|----------------|---------------|---------------|---------------|
|224 |7 |2|1|84.2|
|224 |7 |1|1.05|83.9|
|224 |7 |5|0.67|84.3|
|224 |7 |6|0.57|84.4|
|224 |7 |9|0.47|84.9|
|224 |14 |0|0.9|84.4|
We observe that increasing the carrier token window size can improve the performance at the cost of increased latency, sometimes by a significant margin. The 2x2 carrier token window size offers a great trade-off between accuracy and latency.
In addition, increasing the window size from 7 to 14 increases the Top-1 accuracy by +0.2%. However, as expected, it increases the latency by 10%. We also note that although increasing the window size results in better performance, it does not scale properly to higher resolution images. As a result, HAT is a more effective and efficient mechanism that can be employed without sacrificing image throughput.
> **How do you determine the architecture for the model variants from 0 to 6**
Key design choices for each model variant are : (1) stage-wise depth (2) embedding dimension (3) number of attention heads. Our base model starts with a simple configuration that consists of 2, 3, 6, 5 layers per stage 1, 2, 3 and 4 respectively, an embedding dimension of 64 and 2, 4, 8, 16 attention heads for stages 1, 2, 3 and 4. From this base configuration, we increased the model capacity by increasing the embedding dimension or stage-wise depth to create a Pareto front of Top-1 and throughput trade-off.