- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
They propose to learn residue-aligned surface embeddings with a self-supervised reconstruction framework. A local graph is formed by 32 surface triangles around each surface residue (with Masif features + position wrt to backbone), with adjacency given by relative positions. This surface graph is encoded as discrete tokens, a protein-level message passing happens, and the network aims to reconstruct the 32 input features. To do so, a permutation loss is used. Then, those surface tokens enrich GearBind for protein mutation stability prediction. They obtain sota results on this task. They vary model sizes from 10M to 650M, and pretrain on ~200k RCSB structures, ~440k chains extracted from complexes and 1.6M AFDB domain–domain interfaces, showing interesting scaling laws.
Critical strengths
S1. Strong SOTA results on an important task.
S2. Arguably the first large-scale pretraining of a surface network.
Critical weaknesses
W1. The scaling effect are clear but seem to dominate architectural effects. On a 35M model, with PDB data, is there a gain in including surfaces compared to GearBind+PT? What is the GearBind+PT baseline, how is Gearbind pretrained when it's not with ProtSurf embeddings? Current results suggests that scaling pre-training across model dimension and data size strongly helps for mutation stability prediction, but I am not fully convinced that surface was necessary.
W2. Comparison to existing pre-training approaches is sometimes faulty
- Pre-training Sequence, Structure, and Surface Features for Comprehensive Protein Representation Learning propose a surface-informed pretraining technique. It represents an important comparison.
- AtomSurf is presented as a supervised method in Table 1, and as a pre-trained method in Table 2. To my knowledge, it is not pretrained.
- Other pre-trained structural tokenizers exist (ESM3, SLAE, ISM...), but do not include surfaces. This would be an interesting ablation for W1, and at least worth mentioning in related work.
Questions for authors
Q1. Is there a reason to not use a non-equivariant point transformer in internal coordinates (using 3 points to define a backbone frame instead of just 2: distance and angle)?
Q2. Could you report on the computational aspects of you work? You mention that adding small tokens has limited impact on GearBind parameter count, but you still need to create a surface, patch it, and run you model on each residue. I think readers will want to know how costly this is.
Q3. Following Q2, could you use faster meshing methods? dMasif and AlphaSurf are compatible with on-the-fly processing, which would favor adoption for your method. The definition of a patch was confusing to me "As not all of the patches will be mapped to the residue (as per MaSIF calculation), we then categorized the patches into three groups: (1) Core — patches where all three vertices map to atoms from residue". There seems to be a confusion between patches and triangles here. If you only need points at the surface, dMasif is the most established tool. If you need meshes, AlphaSurf would be more adapted.