ProtFIM: Fill-in-Middle Protein Sequence Design via Protein Language Models

Youhan Lee, Hasun Yu
3/29/2023
cs.LGcs.AIq-bio.BM

No confident code implementation found for this paper.

Abstract

Protein language models (pLMs), pre-trained via causal language modeling on protein sequences, have been a promising tool for protein sequence design. In real-world protein engineering, there are many cases where the amino acids in the middle of a protein sequence are optimized while maintaining other residues. Unfortunately, because of the left-to-right nature of pLMs, existing pLMs modify suffix residues by prompting prefix residues, which are insufficient for the infilling task that considers the whole surrounding context. To find the more effective pLMs for protein engineering, we design a new benchmark, Secondary structureE InFilling rEcoveRy, SEIFER, which approximates infilling sequence design scenarios. With the evaluation of existing models on the benchmark, we reveal the weakness of existing language models and show that language models trained via fill-in-middle transformation, called ProtFIM, are more appropriate for protein engineering. Also, we prove that ProtFIM generates protein sequences with decent protein representations through exhaustive experiments and visualizations.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{lee2023protfim,
  title  = {ProtFIM: Fill-in-Middle Protein Sequence Design via Protein Language Models},
  author = {Youhan Lee and Hasun Yu},
  year   = {2023},
  eprint = {2303.16452},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2303.16452v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2303.16452.svg)](https://codeofpaper.com/paper/2303.16452)

Discussion