- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper introduces HGMamba, which represents MRI modalities and tumor regions as two types of nodes and uses Mamba to exchange information among a small number of nodes. The motivation is intuitive and reasonable: different tumor regions benefit from different imaging modalities. However, I have some concerns about the evaluation benchmarks, comparisons with other methods.
Critical strengths
- Clear presentation and informative figures.
- The paper is well organized, and the figures clearly illustrate the main design choices and processing steps, making the method easy to follow.
- An insightful fusion strategy.
- The method extracts features from four MRI modalities and compresses them into modality nodes. It also introduces three learnable region nodes for the whole tumor (WT), tumor core (TC), and enhancing tumor (ET), allowing each region to draw selectively on information from different modalities. This design fits the motivation for multimodal brain tumor segmentation: using the complementary information provided by different MRI sequences. The broader idea of region-aware modality fusion could inform future work, even without adopting the specific modules proposed here.
Critical weaknesses
- Older benchmarks with limited data and task coverage.
- Relying on BraTS 2018 and BraTS 2020 as the main benchmarks feels somewhat dated for a study in 2026. Both datasets focus on preoperative adult glioma segmentation and overlap substantially, with most of BraTS 2018 included in BraTS 2020. BraTS 2021 expanded the training set for this task to 1,251 cases, while subsequent BraTS challenges have covered more patient populations, tumor types, and geographic regions. Even if the scope remains limited to preoperative adult glioma segmentation, additional experiments on the corresponding BraTS 2021 training set would provide a more representative assessment on a larger, more recent benchmark.
- Several implementation and evaluation details need clarification.
- The HD95 calculation, ET post-processing, and efficiency evaluation settings could affect both the interpretation of the results and the fairness of the comparisons. Specific questions are listed below.
Questions for authors
- HD95 calculation and paired statistical tests.
- According to the paper and the supplied code, cases in which only the prediction or the ground truth is empty appear to be excluded from the mean HD95 without a penalty. This excludes both false positives when the ground truth is empty and complete misses when the prediction is empty. HD95 is generally undefined or treated as infinite in these situations. Please clarify this convention, provide representative examples, and report results with an explicit penalty for these cases, specifying the penalty rule.
- Also, if different methods exclude different cases, how were the pairs constructed for the paired Wilcoxon test, and how were missing values handled?
- ET post-processing and its effect on the results.
- The supplied code removes the entire predicted ET region when its total voxel count is below 500, apparently to suppress false positives. However, this step is not described in the main text. Please clarify whether the same post-processing was applied to all methods.
- Ideally, report ET metrics both before and after this step for every method.
- Settings used for the efficiency comparison.
- How was inference efficiency measured? Please specify the numerical precision, such as FP32 or BF16, and the crop sizes and sliding-window settings. Was each method evaluated using the crop size reported in its original paper?
- For models with multiple CNN encoders processing 3D volumes, crop size and encoder width can substantially affect inference speed. Crop sizes vary across methods, for example, , , and . The base channel width also differs: mmFormer uses 8, whereas HGMamba uses 16. Parameter counts and FLOPs alone do not fully explain the resulting runtime differences. Please clarify these settings and report throughput at both the case level and the crop level.
- The supplied code appears to run inference entirely in FP32. Some methods, such as UniME, report using efficient kernels such as FlashAttention, whose commonly used GPU implementations require FP16 or BF16. Could the authors provide two separate throughput comparisons, one in BF16 and one in FP32, evaluating all methods in both settings under a consistent protocol?