Papers › Metalic: Meta-Learning In-Context with Protein Language Models

Metalic: Meta-Learning In-Context with Protein Language Models

10 Oct 2024arXiv:2410.08355archive 2025-07-28

Jacob Beck, Shikha Surana, Manus McAuliffe, Oliver Bent, Thomas D. Barrett, Juan Jose Garau Luis, Paul Duckworth

Predicting the biophysical and functional properties of proteins is essential for in silico protein design. Machine learning has emerged as a promising technique for such prediction tasks. However, the relative scarcity of in vitro annotations means that these models often have little, or no, specific data on the desired fitness prediction task. As a result of limited data, protein language models (PLMs) are typically trained on general protein sequence modeling tasks, and then fine-tuned, or applied zero-shot, to protein fitness prediction. When no task data is available, the models make strong assumptions about the correlation between the protein sequence likelihood and fitness scores. In contrast, we propose meta-learning over a distribution of standard fitness prediction tasks, and demonstrate positive transfer to unseen fitness prediction tasks. Our method, called Metalic (Meta-Learning In-Context), uses in-context learning and fine-tuning, when data is available, to adapt to new tasks. Crucially, fine-tuning enables considerable generalization, even though it is not accounted for during meta-training. Our fine-tuned models achieve strong results with 18 times fewer parameters than state-of-the-art models. Moreover, our method sets a new state-of-the-art in low-data settings on ProteinGym, an established fitness-prediction benchmark. Due to data scarcity, we believe meta-learning will play a pivotal role in advancing protein engineering.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 10 ran (5 with no instrument failure; 5 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

instadeepai/metalic officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 11 samples, 10 ran (5 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
1ran · violated contract
5ran · our draft was wrong
2ran
1unverified

Licence: 0 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from instadeepai/metalic. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

instadeepai/metalic official repository 11 samples, 10 ran (5 instrument-failed) · 1 unverified
full_ranking_bce meta/models/losses.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 74701b1a5017757a · report fixture: signature preds:Tensor/1/float, targets:Tensor/1/float · returned Tensor · level recorded 2026-09-24
get_device in 101 papers meta/utils.py ran · our draft was wrong Apache-2.0 (permissive) · 99474d787c5c14b3 · report fixture: signature gpu_index:NoneType/0/?, force_cpu:bool/0/bool · returned device · level recorded 2026-09-24
label_smoothed_ranking_loss meta/models/losses.py ran Apache-2.0 (permissive) · cf6b0616253db16d · report fixture: signature ranking_loss:callable/0/?, preds:Tensor/2/float, targets:Tensor/2/float, label_smoothing:float/0/float · returned Tensor · level recorded 2026-09-24
load_json in 344 papers meta/io.py ran · our draft was wrong Apache-2.0 (permissive) · 800fbd05b709b1ff · report fixture: signature jsonfile:str/0/str · returned dict · level recorded 2026-09-24
load_yaml in 107 papers meta/io.py ran · our draft was wrong Apache-2.0 (permissive) · c0273d113af483cb · report fixture: signature yaml_file:str/0/str · returned dict · level recorded 2026-09-24
mse in 78 papers
census: 5 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
meta/tasks/metrics.py ran · violated contract fingerprinted Apache-2.0 (permissive) · d884cc8e472e6f1e · report fixture: signature predictions:ndarray/2/float, targets:ndarray/2/float · returned ndarray · level recorded 2026-09-24
norm_mse meta/tasks/metrics.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 61a7414ab0dba873 · report fixture: signature predictions:ndarray/2/float, targets:ndarray/2/float · returned ndarray · level recorded 2026-09-24
read_fasta meta/utils.py ran Apache-2.0 (permissive) · 35455700ee312018 · report fixture: signature filepath:str/0/str, encoding:NoneType/0/?, keep_insertions:bool/0/bool, keep_gaps:bool/0/bool, to_upper:bool/0/bool · returned tuple · level recorded 2026-09-24
read_msa meta/utils.py ran · our draft was wrong Apache-2.0 (permissive) · 361f81985b5d1c16 · report fixture: signature msa_file:str/0/str, msa_format:str/0/str · returned tuple · level recorded 2026-09-24
standard_mse meta/tasks/metrics.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 105f87deadc73752 · report fixture: signature predictions:ndarray/2/float, targets:ndarray/2/float · returned ndarray · level recorded 2026-09-24

Tasks

In-Context LearningMeta-LearningPredictionProtein Design

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections