mhcseqs

Structural decomposition

This page explains what mhcseqs returns for a sequence and how it decides: the domain grammar, the alignment-free scoring, the status codes that say how confident a decomposition is, and the literature the grammar is drawn from. Read it before treating a groove string as a complete domain.

The domain grammar

The parser materializes an explicit domain grammar:

Chain Grammar
Class I alpha signal_peptide? -> g_alpha1 -> g_alpha2 -> c1_alpha3 -> transmembrane? -> cytoplasmic_tail?
Class II alpha signal_peptide? -> g_alpha1 -> c1_alpha2 -> transmembrane? -> cytoplasmic_tail?
Class II beta signal_peptide? -> g_beta1 -> c1_beta2 -> transmembrane? -> cytoplasmic_tail?

The exported contiguous sequence fields are:

Column Class I alpha Class II alpha Class II beta
groove1 α1 domain (~80-95 aa typical) α1 domain (~75-95 aa typical) —
groove2 α2 domain (~80-100 aa typical) — β1 domain (~70-100 aa typical)
ig_domain α3 C-like support domain α2 C-like support domain β2 C-like support domain
tail linker + TM + cytoplasmic tail linker + TM + cytoplasmic tail linker + TM + cytoplasmic tail

domain_architecture and domain_spans expose the typed domain grammar directly, for example:

How parsing works

The parser is alignment-free and holistic. It does not rely on one absolute Cys position to define the mature start.

For each sequence it:

  1. Enumerates all plausible Cys-Cys pairs in the Ig/C-like separation range.
  2. Scores each pair as a candidate G-domain or C-like anchor using fold-topology evidence, especially the Trp41-like signal around c1+14.
  3. Enumerates candidate SP boundaries and whole domain parses, including partial parses when only fragment evidence is available.
  4. Chooses the best full parse using factored multiplicative scoring: three structural claims (SP grammar, domain architecture, completeness) each produce a [0,1] factor. Contradictory evidence in any factor gates the score down multiplicatively, while missing evidence is a softer penalty.

The strongest evidence types are:

The parser handles:

Groove status values

These are the important parser-facing statuses:

Status Meaning
ok Full decomposition from the main structural grammar
alpha1_only Class I fragment consistent with α1 / exon 2 only
alpha2_only Class I fragment consistent with α2 / exon 3 only
fragment_fallback Short fragment retained as the observable groove half
inferred_from_alpha3 Class I salvage parse using a downstream α3 C-like anchor
beta1_only_fallback Class II beta salvage parse using only the β1 groove pair
missing_groove No recoverable groove architecture from the available evidence
non_classical Non-classical class-I lineage flagged post-parse
short Groove half too short to look functionally peptide-binding

Pipeline-only statuses can still appear in CSV outputs:

Status Meaning
not_applicable Row intentionally excluded from groove functionality, mainly B2M in build outputs

Literature basis

The parser is built around conserved sequence grammar from the MHC literature:

Signal-peptide logic follows the standard SPase grammar: