Protein annotation leaderboard

MMseqs2

Amino-acid letters: it first keeps target proteins that share similar short words with the query, then aligns only those, which makes it much faster than aligning every pair.

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.249 (n = 563), 60–100% 0.297 (n = 1,289). If no, 20–30% 0.325 (n = 93), 30–40% 0.188 (n = 165). (Pfam truth set, raw calls, zebrafish (430 Mya) as the relative searched, setting sensitivity 7; subsets with at least 30 true instances.)
  2. Are the features you care about longer than 60 residues? If yes, Fmax here is 61–120 aa 0.243 (n = 963), 121–250 aa 0.305 (n = 504), 251 aa or more 0.462 (n = 277). If no, 16–30 aa 0.027 (n = 271), 31–60 aa 0.089 (n = 420). (Pfam truth set, raw calls, zebrafish (430 Mya) as the relative searched, setting sensitivity 7.)
  3. Can you spend about 0.0252 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 sensitivity 7 (s7): Fmax 0.327 over 2,435 true instances. Searching costs about $0.00113 per 1,000 queries (0.0252 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 sensitivity 7: best feature type active site, Fmax 0.312 (n = 176); worst short motif, Fmax 0.000 (n = 190).

Figure 2. Where MMseqs2 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, sensitivity 7). Left out, under 30 true instances: 0–20%.
MMseqs2 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.359phmmerMMseqs2: Fmax 0.325, n = 9330–40%best other tool: MMseqs2, three rounds, sensitivity 7, 3 rounds, Fmax 0.209MMseqs2, three roundsMMseqs2: Fmax 0.188, n = 16540–60%best other tool: phmmer, default options, Fmax 0.252phmmerMMseqs2: Fmax 0.249, n = 56360–100%best other tool: phmmer, default options, Fmax 0.308phmmerMMseqs2: Fmax 0.297, n = 1,289none in relativebest other tool: HH-suite (hhsearch), single-protein profiles, Fmax 0.032HH-suite (hhsearch)MMseqs2: Fmax 0.003, n = 321length of the annotated region16–30 aabest other tool: kmerseek, wwmj5, k = 11, Fmax 0.330kmerseekMMseqs2: Fmax 0.027, n = 27131–60 aabest other tool: kmerseek, gbmr4, k = 21, Fmax 0.232kmerseekMMseqs2: Fmax 0.089, n = 42061–120 aabest other tool: phmmer, default options, Fmax 0.250phmmerMMseqs2: Fmax 0.243, n = 963121–250 aabest other tool: jackhmmer, 3 rounds, Fmax 0.333jackhmmerMMseqs2: Fmax 0.305, n = 504251 aa or morebest other tool: phmmer, default options, Fmax 0.477phmmerMMseqs2: Fmax 0.462, n = 27700.10.20.30.40.5Fmax (higher is better)

What it compares

Amino-acid letters: it first keeps target proteins that share similar short words with the query, then aligns only those, which makes it much faster than aligning every pair.

What it needs

Reference searched

The relative's proteome (Quest for Orthologs reference proteomes, release 2020_04), as an MMseqs2 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 s7, searching one relative (mean over the 15 relatives it searched): 0.0252 core-hours reserved per 1,000 queries (16 cores for the task's wall time), measured on Sherlock. Peak memory 1.1 GB. That is about $0.00113 at $0.044625 per CPU-hour. Building its databases took 0.00889 core-hours over 7 databases. A database is built once and reused, so this is not in the per-query cost. This covers the 7 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

mmseqs search \
    human-38fdd87d_mmdb/db zebrafish_mmdb/db result mmseqs_tmp \
    --threads 16 \
    -s 7 \
    --max-seqs 1000 \
    -e 10.0

Followed by mmseqs convertalis to write the table of hits.

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

All tool cards · this card as Markdown · as JSON