Response to Reviewer 6zjS
Thanks for your thoughtful reflections on this question and pointing out the confusion about the calculation and comparation of label efficiency. We will discuss these questions more deeply and below are our analysis and explanation:
## Q1: Rethinking whether not using the AP metric in instance segmentation
- **Why the previous works[1,2] are called "instance segmentation" :** As we mentioned in the paper, the previous works adopt two-stage workaround. The first stage utilizes a 3D instance semantic segmentation network to get instance proposals. And the second stage leverages a network to match the query with corresponding instance proposals. Because the first stage is of great importance to this task, previous works simply named this task with "instance segmentation", while we followed the previous works to do that and will extand more discussions into our revised version to rethink how to strictly name this task.
- **Why not use AP metric in the R3DIS task:** Thanks for this detailed reading and question. The target of referring 3D instance segmentation about a corresponding query is only one. Therefore the IoU metric is sufficient to measure this task. In addition, the Acc@x metrics also is used to measure the accuracy of the segmentation mask. We will consider to add more comparative definition between Acc@x and AP into our revised implementation details.
- **Rethinking about our LESS:** We will take necessary in-depth discusions to explain and compare referring 3D instance segmentation with conventional instance segmentation task. Since our method is one-stage and lacks a first instance proposal stage, the title with "instance segmentation" may be not strictly align with the common instance segmentation task. However, the core contribution of our paper is to develop a simple yet effective single-stage for this community, shifting from complicated two-stage pipeline into single-stage one, which paves more spaces for future works. We will add more in-depth discussions to the final version of the paper and consider whether to revise the confusing title.
## Q2: For the labelling time on the whole dataset
- **The number of scenes needed to annotate:** Previous works [1,2] contain a 3D instance segmentation and a matching network. Based on their open source codes, we find that training a typical instance segmentation network requires annotations for **1513** scenes (train+val) rather than **800** scenes (which is the number of ScanRefer). Therefore, in light of the aforementioned assumption that the time required for the annotation of a single scene is 25 minutes, the overall time required for the training process should be 25 * 1,513 = 37,825 minutes, rather than the 20,000 minutes as estimated before.
- **The number of objects needed to annotate:** In order to make a fairer and more reasonable comparison of label-efficiency between our LESS and previous works, we compare the number of objects required labelling. Firstly, we follow the open source codes of the previous works to process the dataset. From the processed dataset we find that the number of annotated objects under 1513 scenes is about **45,711**, even though excluding walls and floors. As for our LESS, we only need to annotate **11,046** objects, which is 4 times fewer compared to previous works. Here we need to note that the objects referred by ScanRefer is the subset of the objects in ScanNetv2.
- **For the comparative method of time in the paper:** As we mentioned above, the objects referred by ScanRefer are a subset of all objects among all scenes. In the context of the time comparison presented in the paper, the comparison of labeling effort is based on a single sample. This is because that, in consideration of reality scenarios, it is often the case that the model is adapted to incorporate new data in order to align with evolving referential requirements. Therefore, in our method, there only necessitate just a single or a few objects needed to be labelled, rather than the entire scene. When scaling up the dataset scale for this task, our advantages will become much more significant. As a result, we compared the label effort of a single sample in the paper. Thank you for pointing out this issue, and we will make further discussion on this in our paper to reduce any potential ambiguity.
In summary, our method takes less time than the previous works in different comparison methods, which indicates our method is more label-efficient. Also We would like to extend our gratitude once more for your insightful suggestion. It is our sincere hope that the responses above could address your concerns. If you have any additional questions or suggestions, please let us know.
[1]. Text-guided graph neural networks for referring 3d instance segmentation, AAAI 2021
[2]. X-RefSeg3D: Enhancing Referring 3D Instance Segmentation via Structured Cross-Modal Graph Neural Networks, AAAI 2024