- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper proposes LOCUS framework, which adds a supervised regional pathway to global sequence and structure predictors. A class-agnostic proposal network learns functional regions from residue annotations; their pooled representations contribute through label-specific gated residuals. The paper evaluates GO and EC prediction and uses pathway removal, fixed-gate decomposition, and proposal diagnostics to examine when regional information helps.
Critical strengths
Giving local evidence its own predictive pathway while retaining global information is a sensible design. I also appreciated the effort to understand the EC result rather than simply report the overall score: the ROI route contributes little there, and Appendix C checks its normalized geometry instead of interpreting tiny raw mask values as evidence of collapse. This distinction between learning regions and benefiting from them makes the paper more informative than a performance comparison alone.
Critical weaknesses
The comparison in Section 4.5 does not isolate the gate effect. Its fixed-gate gain of 0.020 is seq+ROI minus seq. Removing ROI from the complete model instead calls for full minus seq+str, approximately using Table 5’s rounded values. These are different comparisons, so the difference between 0.020 and the reported removal effect of 0.017 cannot be attributed to gate adaptation. This needs correcting before drawing the proposed distinction between pathway value and reliance.
Moreover, the source-recovery issue is my other concern. The reproducibility statement says that two central modules and the source for the shared site-pretraining run still require reconstruction. I appreciate the disclosure, but this is more than an unreleased repository. Since every reported model uses that warm start, I would need evidence that the restored implementation agrees with the saved checkpoints and outputs. Provenance hashes alone do not establish that agreement.
Questions for authors
- Using the same complete-model background, how do fixed-gate and recomputed-gate ROI removal compare? Does the Section 4.5 interpretation survive?
- Has the missing source been restored, and what output-level checks establish agreement with the original implementation?
- Could the authors provide an anonymized codebase for review, including the restored pretraining scripts and code verification to ensure the reproducibility of the warm-start checkpoints?