- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper adress FSMIS by expanding a single support feature through random elastic deformation, generating multiple features with different morphologies for prototype extraction. In this way, it provides more candidate representations for support-query matching and attempts to mitigate the impact of support-query bias. Despite the seemingly strong experimental results, I find that the proposed design is not sufficiently justified and, in my understanding, contains several questionable aspects, including but not limited to random deformation sampling, the computational overhead, and the lack of clear validation of the claimed advantages. Also, I find that the introduction of SAM in this work seems more like an add-on to make performance look better, without any dedicated design. Currently, I am inclined to reject this paper.
Critical strengths
- The support-query bias (or intra-class differences) addressed in this paper is indeed a real issue in FSMIS.
- The proposed method achieves strong experimental results.
Critical weaknesses
-
Support-query bias appears to be an old research problem in FSMIS and has already been considered even in very outdated works such as Q-Net and RPT. I do not see sufficiently valuable new insights from this work.
-
The overall method design is not elegant and, in my view, tends to complicate a relatively simple problem for limited improvement. For example, replicating the support features multiple times and processing all of these copies can introduce substantial computational overhead. Even the authors themselves acknowledge in the limitation section that the increase in computational cost and memory consumption is significant. Therefore, I am not convinced that this method would have a practical advantage in real-world deployment.
-
In EFDM, the deformation is randomly sampled from a uniform distribution. My understanding, based on the explanation in Appendix A.1, is that the authors assume that there is a certain probability that the query feature can be approximated by applying a deformation to the support feature. If this is the case, why does increasing the number of sampled deformations actually decrease the final performance, as shown in Figure 6? Intuitively, sampling more deformations should increase the probability that at least one deformed support representation is close to the query.
-
In my view, poor support-query matching is more likely to be caused by semantic feature misalignment than by spatial morphological differences. I am therefore confused about why a random and non-learnable spatial deformation can effectively address this issue. I suggest that the authors conduct additional experiments to separately investigate the effects of semantic discrepancy and spatial/geometric discrepancy on support-query matching.
-
The construction of the local prototypes is somewhat different from previous methods such as RPT and GMRD. The authors claim that averaging along rows and columns captures vertical texture variations and horizontal structural consistency. I would be interested in seeing experiments that directly validate this claim, particularly comparisons showing why this row/column-based construction is better than existing local partitioning or local prototype construction strategies.
-
How are the prompts used for SAM extracted from the coarse prediction? In addition, I think in Eq 6 may be better denoted by , since has already been extensively used throughout the paper to represent feature maps.
-
Section 3.5 explains the effectiveness of the proposed method by saying that it reduces the L2 distance between support and query features. However, the actual matching operations throughout the method are based on cosine similarity. The authors should therefore additionally report how cosine similarity changes before and after deformation, since cosine similarity, rather than L2 distance, is the metric that actually determines the matching results.
-
Since this work still follows a coarse prediction -> SAM -> refined prediction pipeline, I am interested in the performance before SAM refinement and in the results of using other existing FSMIS models as prompt generators for SAM, since any segmentation model could potentially provide prompts for SAM. What is the specific advantage of EFG-SAM and what design is truly necessary for supporting SAM?
Questions for authors
Please see weakness section.
Dear reviewers and authors,
As the discussion period is limited, please follow up on the latest responses and comments in a timely manner to address any remaining concerns. Thank you!