Don't Retrain, Just Reuse: Recovering Dual-Target Molecules from Single-Target Diffusion Models

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2605.25681v2 Announce Type: replace-cross Abstract: Designing a single molecule that modulates two targets is a promising strategy for polypharmacology, but it remains substantially harder than standard single-target generation because one candidate must satisfy two binding requirements while preserving drug-likeness and synthesizability. Existing dual-target generative methods typically introduce dual-target capability by either retraining the generator or intervening in the diffusion process during sampling. The former can be costly and difficult to stabilize when dual-target supervision is sparse, while the latter may be sensitive to denoising-time target balancing and competing update directions. These limitations motivate a generator-preserving alternative that keeps the pretrained prior intact: can dual-target candidates instead be recovered from the input space of a frozen single-target diffusion model, without modifying its parameters or denoising dynamics? We formulate this task as a constrained multi-objective optimization problem and propose REUSE, which evolves the input noise of a frozen diffusion generator rather than molecular structures. Each input is decoded multiple times and scored by the collective quality of the generated molecular family. Candidates are then screened progressively: lower-cost evaluations prioritize molecules satisfying chemical-feasibility criteria, full docking is reserved for a reduced frontier, and the survivors are jointly selected as a diverse panel with strong affinity to both targets. Experiments show that REUSE achieves …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2605.25681
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.