Protein annotation leaderboard

ProstT5 + Foldseek

Shape letters (3Di) predicted from the amino-acid sequence by the ProstT5 protein language model, then searched with Foldseek, so no AlphaFold model is needed.

Will it work for you?

  1. Is the closest same-family domain in the relative you will search at least 40% identical, for most of your proteins? If yes, Fmax here is 40–60% 0.139 (n = 563), 60–100% 0.209 (n = 1,289). If no, 20–30% 0.247 (n = 93), 30–40% 0.144 (n = 165). (Pfam truth set, raw calls, zebrafish (430 Mya) as the relative searched, setting shape letters from sequence; subsets with at least 30 true instances.)
  2. Do you have a GPU to predict the 3Di letters for your proteins? The run used one GPU for that step; its cost is not counted here.
  3. Can you spend about 0.109 core-hours per 1,000 proteins for each relative you search? That is the measured mean per relative; see "Cost per 1,000 queries" below.

Best Fmax and cost

Under the Pfam truth set, raw calls, zebrafish (430 Mya) as the relative searched, its best setting is shape letters from sequence (3di_from_seq): Fmax 0.223 over 2,435 true instances. Searching costs about $0.00486 per 1,000 queries (0.109 core-hours), for each relative searched.

Where it is strong and weak

Each line compares this setting with the best setting of any other tool on the same subset of the proteins, so the other tool's setting can change from line to line. Only subsets with at least 30 true instances are compared.

Where it is closest to, or furthest ahead of, the best other tool:

Where it is furthest behind the best other tool:

Swiss-Prot features, raw calls, zebrafish, setting shape letters from sequence: best feature type active site, Fmax 0.278 (n = 176); worst membrane-spanning, Fmax 0.000 (n = 1,124).

Figure 2. Where ProstT5 + Foldseek is ahead and behind: its Fmax on each subset of the proteins, against the best other tool on that subset (Pfam truth set, raw calls, zebrafish as the relative; its best setting, shape letters from sequence). Left out, under 30 true instances: 0–20%.
ProstT5 + Foldseek best other tool on that subset, named at the right
% identity to the closest same-family domain20–30%best other tool: phmmer, default options, Fmax 0.359phmmerProstT5 + Foldseek: Fmax 0.247, n = 9330–40%best other tool: MMseqs2, three rounds, sensitivity 7, 3 rounds, Fmax 0.209MMseqs2, three roundsProstT5 + Foldseek: Fmax 0.144, n = 16540–60%best other tool: phmmer, default options, Fmax 0.252phmmerProstT5 + Foldseek: Fmax 0.139, n = 56360–100%best other tool: phmmer, default options, Fmax 0.308phmmerProstT5 + Foldseek: Fmax 0.209, n = 1,289none in relativebest other tool: HH-suite (hhsearch), single-protein profiles, Fmax 0.032HH-suite (hhsearch)ProstT5 + Foldseek: Fmax 0.020, n = 321length of the annotated region16–30 aabest other tool: kmerseek, wwmj5, k = 11, Fmax 0.330kmerseekProstT5 + Foldseek: Fmax 0.000, n = 27131–60 aabest other tool: kmerseek, gbmr4, k = 21, Fmax 0.232kmerseekProstT5 + Foldseek: Fmax 0.032, n = 42061–120 aabest other tool: phmmer, default options, Fmax 0.250phmmerProstT5 + Foldseek: Fmax 0.157, n = 963121–250 aabest other tool: jackhmmer, 3 rounds, Fmax 0.333jackhmmerProstT5 + Foldseek: Fmax 0.226, n = 504251 aa or morebest other tool: phmmer, default options, Fmax 0.477phmmerProstT5 + Foldseek: Fmax 0.365, n = 27700.10.20.30.40.5Fmax (higher is better)

What it compares

Shape letters (3Di) predicted from the amino-acid sequence by the ProstT5 protein language model, then searched with Foldseek, so no AlphaFold model is needed.

What it needs

Reference searched

3Di letters predicted by ProstT5 for the relative's proteome (Quest for Orthologs reference proteomes, release 2020_04), as a Foldseek database.

How to read its score

Bit score: higher ranks first. The E-value cutoff was 10.

Known failure modes

Cost per 1,000 queries

Setting 3di_from_seq, searching one relative (mean over the 15 relatives it searched): 0.109 core-hours reserved per 1,000 queries (16 cores for the task's wall time), measured on Sherlock. Peak memory 1.5 GB. That is about $0.00486 at $0.044625 per CPU-hour. Building its databases took 5.31 core-hours over 3 databases, plus 0.664 GPU-hours (1 GPU via --gres=gpu:1 (model not recorded)). A database is built once and reused, so this is not in the per-query cost. This covers the 3 database builds the task records hold; the search used 15 relatives.

The per-query cost counts the search only. The run recorded cost per tool and setting, summed over all relatives, so the cost for one relative is the mean.

Licence

Settings in the table

Version, container, command

foldseek createdb filtered.fasta zebrafish_prostt5/db \
    --prostt5-model weights --gpu 1 --threads 8

foldseek search \
    human-38fdd87d_prostt5/db zebrafish_prostt5/db result tmp \
    --threads 16 \
    -e 10.0 \
    --max-seqs 1000

The first command (one per proteome, on a GPU) predicts the 3Di letters. The second is the search the cost columns measure.

Tool id prostt5. Numbers from seanome/2024-kmerseek-analysis commit 4a4b1171.

All tool cards · this card as Markdown · as JSON