Summary
The paper’s key advantage lies in its integration of large language models (LLMs) into affordance segmentation, leveraging their semantic richness to enhance understanding and address limitations of fixed affordance labels in prior methods, thus increasing adaptability in open-world settings. The proposed task, Instruction Reasoning Affordance Segmentation (IRAS), combines LLM-encoded text features with point features, with a pretraining step on part segmentation to address data scarcity.
However, IRAS closely resembles prior affordance tasks, particularly Language-guided Affordance Segmentation on 3D Objects (LASO), which raises questions about its novelty. Additionally, the methodology shows minimal distinction from existing work, with pretraining as the main difference, which does not provide strong novelty. Another limitation is the lack of rigorous comparative experiments to demonstrate clear advantages over previous approaches, leaving key aspects, such as the contributions of LLM features and pretraining, unclarified.
The paper also suffers from poor organization and inconsistent notation, which hinder readability. While additional experiments could strengthen validation, the limited novelty and unclear contributions reduce the impact of the work. Therefore, I recommend rejection.
Strengths
1. **Motivation**: the strength of this paper is its motivation to leverage large language models (LLMs) for enhancing semantic comprehension in 3D affordance detection. Unlike previous methods that are limited by a fixed set of affordance labels, this approach uses an LLM to interpret complex, instruction-based queries, enabling the model to recognize affordances in a more flexible and context-aware manner. By incorporating LLMs, the model can process nuanced instructions, overcoming the constraints of rigid label sets and allowing it to generalize affordances in open-world settings.
2. **Pretraining**: The authors address the challenge of limited data by introducing a pretraining stage on part segmentation, which enhances the model's ability to capture part-level features even with a smaller affordance dataset. This pretraining strategy not only compensates for data scarcity but also provides the model with a foundation to learn more transferable features, contributing to improved performance in affordance segmentation.
Weaknesses
1. **Limited Novelty Regarding the Proposed Task**: The authors introduce a task, Instruction Reasoning Affordance Segmentation (IRAS), aiming to address perceived limitations in existing 3D affordance detection approaches. However, IRAS shares substantial overlap with previous work, particularly with the Language-guided Affordance Segmentation on 3D Objects (LASO) task[1]. Both IRAS and LASO involve generating a mask over functional parts of a 3D object point cloud based on a question or instruction. Specifically, each query in both tasks consists of an object type and an affordance type, with the objective of inferring the functional part relevant to the query. To clarify the distinctiveness of IRAS, the authors should elaborate on how their queries are generated, detailing the heuristics and rationale behind their construction, and the specific differences between IRAS and LASO, and any innovations that set IRAS apart as a unique contribution to the field. Without this, the similarities between IRAS and LASO bring into question the novelty of IRAS as a distinct task.
2. **Limited Innovation in Methodology**: To address these challenges, the authors integrate a large language model (LLM) into a point cloud segmentation framework, using the LLM to process instructions and produce text features along with point cloud features for affordance mask prediction. However, the design involving two separate point encoders is confusing. The authors may claim that incorporating multimodal text and point cloud inputs allows the LLM to capture semantic information better, potentially enhancing segmentation performance. However, given the limited dataset size, it is unclear if sufficient point-text alignment can realistically be achieved. Furthermore, this design lacks supporting experiments to validate its effectiveness. Aside from a part segmentation pretraining step for extracting part-based features, the approach doesn't show a significant difference from LASO, which uses text features from LLM and point cloud features from a point backbone to decode affordance masks. This makes the contribution of pretraining alone insufficient as a distinguishing factor for novelty. The author needs to explain the core difference between your method and LASO.
3. **Lack of Rigorous Experimental Validation**: though the proposed method shows performance gains over previous approaches, the effectiveness of the proposed design is not convincingly demonstrated due to concerns about the experimental setup and baseline data, as noted in the questions. A key issue is the lack of ablations to demonstrate the extent to which the improvements stem from the pretraining stage, the large-scale pretrained backbone, or the method itself. The following baseline experiments could strengthen the validation. The authors are encouraged to prioritize experiments based on their assessment of each module's importance, conducting analyses to substantiate the effectiveness of different components and explaining which aspects they consider most critical, and why.
- **Basic Baseline A**: Use the LLM to encode only text features, inputting them into the decoder along with point features encoded by a standard backbone, like PointNet++. This approach would closely follow LASO’s baseline method.
- **Pretraining Variant B**: Use the proposed pretraining task, ROPS, train variant **A** and then fine-tune **A** on the IRAS task. This would help isolate the contribution of pretraining compared to **A** and show its impact on performance. In your current experiments, you simply remove the pretraining step (as shown in **Table** 6). This makes it difficult to determine whether the improvements over LASO are due to the proposed `AFF` token or the use of the Point Transformer segmentation backbone. The Without additional experiments, it’s challenging to draw convincing conclusions about the source of the performance gains.
- **Backbone Variant C**: Replace the point encoder with the same point segmentation backbone (Point Transformer) used in this work, to determine the extent to which the performance improvement is due to the backbone choice rather than the proposed method.
- **Dual Encoder Variant D**: Introduce a second point encoder, initially using PointNet++, which outputs point features to the LLM along with text tokens. The LLM’s output is then fed into the decoder from Variant **C**. This setup would reveal how much the proposed `AFF` token contributes to performance.
- **Current Approach E**: Test the full model with the proposed `AFF` token integration and two encoders to measure the combined effectiveness of all components.
- **Comparison with previous approaches F**: The fairest comparison to the previous approaches is to remove the pretrain stage and replace your segmentation backbone with PointNet++.
4. **Inadequate Clarity and Organization in the Paper**: The methodology section lacks clear logical flow, and inconsistent notation makes it challenging to follow. The experimental setup is insufficiently detailed, and numerous errors in descriptions further reduce clarity. Improvements in notation consistency, methodology organization, and experimental description are needed to enhance the overall clarity and coherence of the proposed approach.
[1]Yicong Li, Na Zhao, Junbin Xiao, Chun Feng, Xiang Wang, and Tat-seng Chua. Laso: Language-
guided affordance segmentation on 3d object. CVPR 2024
Questions
- **Q1**: In **Figure 1**, the example question is ambiguous. Given a prompt like “something I can use to drink water” for a mug, most people would interpret this as referring to the whole mug, not specifically the handle or the body. In **Figure 2**, the questions are much clearer and directly target specific parts. Can you explain how your model infers that the handle of a mug is the intended affordance in such an ambiguous scenario in **Figure 1**? Is any specific design in your method to handle ambiguity or resolve cases with multiple possible interpretations? You could provide a range of example queries, from ambiguous to specific, to illustrate how the model addresses each type of query and manages interpretational differences.
- **Q2**: In **Line 210**, the explanation and organization of the point encoder section are unclear and inconsistent. Why is the subscript for $f_{pe}$ lowercase, while $f_{PB}$ is uppercase? According to the projector section, the feature X is fed into the LLM. However, in **Figure 2**, it appears that feature X originates from the "point backbone" rather than the "point encoder," as mentioned in **Line 210**. Could you clarify this inconsistency?
- **Q3**: In **Lines 289-297**, the explanation is unclear, and the notations are inconsistent. The symbols $\textbf{f}$, $f_{pb}$, and $\textbf{p}_{clouds}$ do not match the earlier sections or the figures. Could you provide a clearer and more cohesive explanation?
- **Q4**: In **Figures 2 and 3**, the "b" stage is inconsistent. In **Figure 2**, the point cloud feature input into the LLM is encoded by a "trainable point backbone," while in **Figure 3**, it is processed by a "frozen point encoder." Could you clarify this pipeline, ensuring consistent notations and descriptions?
- **Q5**: In **Line 341**, how is the ground truth text obtained?
- **Q6**: In **Line 353**, the formula for $L_{mask}$ appears incorrect. The summation should be outside the formula. It seems that your query already includes the affordance type, meaning the affordance type is known beforehand. Therefore, this task can be treated as a binary classification problem, as opposed to a multi-class setting. In OpenAD, they maximize the cosine similarity between points and the target affordance type, making it a multi-class classification problem. Given this setup, I’m curious about the role of the affordance class weights in your binary classification loss. Could you clarify how these affordance class weights are used in this binary classification context?
- **Q7**: In **Table 1**, you claim the experiment is zero-shot and open-vocabulary and you seem to reference results from TZSLPC, 3DGenZ, and ZSLPC in OpenAD[2]’s **Table 1**. If your setup is identical to OpenAD’s **Table 1**, which evaluates 37 classes, why do you mention evaluating only 18 valid classes in **Line 402**? Could you clarify your experimental setup?
- **Q8**: In **Table 1**, how is the accuracy (Acc) computed? In OpenAD’s **Table 1**, all reported accuracies are over 40%, yet here, your best result is only 29%, and the two OpenAD variants show values around 3.9%. Given that your reported mIoU and mAcc for the two OpenAD variants are closer to those in OpenAD, one would expect similar Acc values. Where do these reported accuracy results for the two OpenAD variants come from, and why aren’t you referencing the accuracies for TZSLPC, 3DGenZ, and ZSLPC, even though you reference other metrics for these models?
- **Q9**: In **Table 1**, could you specify what “full view” and “partial view” refer to in your experimental setup?
- **Q10**: In **Table 2**, could you further clarify the difference between the mAcc in **Table 2** and the mAcc in **Table 1**? It’s somewhat understandable that "over all classes" and "over all instances" might differ, but why does, for example, the mAcc for OpenAD-PointNet++ differ so significantly from 16.4 in **Table 1** to 74.59 in **Table 2**?
- **Q11**: In **Tables 2 and 3**, why is the performance on out-of-distribution (OOD) unseen object data higher than on the test set of your primary dataset in **Table 2**? Adding visual examples could help clarify this discrepancy.
- **Q12**: In **Tables 4 and 6**, the experiment setting is highly unclear, on what dataset were the experiments conducted, and did you use the full view or partial view setting?
[2]Toan Nguyen, Minh Nhat Vu, An Vuong, Dzung Nguyen, Thieu Vo, Ngan Le, and Anh Nguyen.Open-vocabulary affordance detection in 3d point clouds. IROS 2023.