- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper presents a sequence-conditioned ligand generator that connects frozen ESM3 residue embeddings to an autoregressive SMILES transformer through a learned projection and mean pooling over 16 contiguous sequence segments. A separate token specifies a requested negative-log affinity proxy. The 6.85M-parameter generator is trained by next-token prediction on approximately 1.84M protein–ligand records partitioned using 30% sequence-identity clusters. Generated candidates are ranked by DeepPurpose AttentiveFP/CNN and adapted ConPLex regressors, then evaluated using RF3 complex confidence. On 42 targets, matched protein prefixes produce higher mean ipTM than mismatched prefixes (0.920 versus 0.829). An additional 82-target comparison places generated ligands between measured target binders and molecular-weight-matched off-target ligands. Comparisons with PCMol and ProtoBind-Diff show similar observed ipTM, higher yields of distinct valid molecules, and 4.3-6.1x faster generation with cached protein features. My reading is that the contribution is a compact implementation of protein-conditioned molecular generation, with computational evidence that the prefix carries useful target information; binding affinity and selectivity of the generated candidates remain unmeasured.
Critical strengths
-
The compact decoder offers a practical advantage for repeated sampling. The reported reductions in generation time and allocated GPU memory are substantial within the cached-feature setting, which could make this approach useful for building larger candidate pools.
-
The higher yield of distinct valid, connected molecules is a meaningful result independent of predicted binding scores. Table 16 reports 90.95% versus 86.10% for PCMol and 88.95% versus 65.33% for ProtoBind-Diff under a common validity procedure.
Critical weaknesses
-
There aren't very many methodological advancements here and also incomplete comparison with closely related work. Frozen protein embeddings, projection, segment averaging, and a standard next-token objective form a pretty standard architecture. Prot2Drug (Creanza et al., 2025) already connects pretrained protein representations to a two-layer transformer decoder, while DrugGPT and ZeroGEN are also missing from the discussion and experiments. The proposed regional pooling could still be useful, but Table 7 changes affinity fusion and training alongside pooling, and both confidence intervals include zero. This does not establish what the 16-token representation contributes.
-
Unfortunatley, the authors don't establish strong ligand design. The final affinity oracles achieve test Spearman correlations of only 0.395 and 0.321, and their average selects the candidates evaluated downstream. RF3 provides a separate structural prediction, but neither ipTM nor contact-restricted PAE establishes binding or selectivity, and the off-target controls are not verified non-binders. The docking results provide limited support, as native-ligand redocking succeeds within 2 Å on only 3/12 targets. I would need stronger validation against measured binding data to judge whether the computational improvements translate into useful candidates.
-
Generalization and comparative performance are difficult for me to assess. Appendix B.2 states that the nominal test split informed model development, and the 42-target prefix panel comes from targets selected in earlier candidate screens. The Pocket2Mol/TargetDiff panel contains nine training and three validation targets. These choices substantially weaken the evidence on unseen targets. Moreover, Table 2 reports ipTM differences of -0.0108 against PCMol and +0.0083 against ProtoBind-Diff, with both intervals crossing zero.
Questions for authors
-
The authors should compare against Prot2Drug (Creanza et al., 2025), DrugGPT (Li et al., 2023), and ZeroGEN (Chen et al., 2025) on a common target panel. I'd prioritize Prot2Drug because its pretrained protein representation plus small decoder directly tests the proposed contribution. Please match generation and selection budgets, and document training overlap.
-
Can the authors provide an explanaiton for benefit comes specifically from contiguous regional pooling in Eq. 2? Please compare fully trained models using global mean pooling, 16 learned queries, and 16 randomly assigned residue groups, holding ESM3 features, decoder size, affinity conditioning, and training budget fixed.
-
Which decisions used the nominal test split? Please evaluate on protein clusters unused during development, with targets selected before generating candidates, and report nearest training-protein similarity and generated-ligand similarity to the full training set, including scaffold overlap. To me, exact-SMILES novelty alone does not establish substantial chemical novelty.
-
How well does the ensemble average of the DeepPurpose and ConPLex predictions rank measured ligands within each held-out protein? Please report within-target correlations and top-ranked enrichment, then compare ensemble, single-oracle, and random selection from identical candidate pools.
-
How should a user interpret the requested affinity proxy, , when assay endpoint types were discarded? Table 13 gives a fitted response of only 0.0749 predicted pAff per requested unit, and Table 14 shows no clear RF3 benefit. Please evaluate an endpoint-consistent subset and a model trained without the affinity token.
-
Can RF3 ipTM distinguish experimentally measured actives from measured inactives on unseen targets? Please test this with chemically matched controls and report discrimination and enrichment to help me see this.
-
Could you repeat timing with models already resident on the GPU, comparable precision, and consistent output-length limits? ProtoBind-Diff currently incurs Trainer creation and device placement inside the timer. If you can report distinct valid molecules per second and separately include protein-feature extraction and downstream scoring, it would show the practical cost of the full workflow.