Skip to main content

    Humatch outputs and interpretation

    Humanness scores, flagged positions, and closest germline from Humatch.

    humatchoutputs

    Humatch returns, per sequence, an overall humanness score, a pass/fail against your threshold, per-V-gene and per-position scores, the closest human germline V gene, and a list of the positions that pull the score down. Read the flagged positions alongside the overall score: the score tells you whether to humanize, the flagged positions tell you where.

    Per-sequence result

    Each scored sequence carries these fields:

    FieldTypeWhat it tells you
    sequence_namestringThe name you gave the sequence.
    humanness_scorefloatOverall humanness (0–1).
    is_humanboolWhether the score clears your threshold.
    chain_typestringThe chain type scored (H or L).
    v_gene_scoresmap gene→floatPer-V-gene humanness scores.
    top_human_germlinestring | nullClosest human germline V gene.
    positional_scoresmap position→floatPer-position humanness, on the numbering scheme used.
    flagged_positionsstring[]Positions with low humanness — the humanization targets.

    Paired result

    A request that used chain_pairs also returns paired_results, one entry per pair. For a single-chain request the list is empty.

    FieldTypeWhat it tells you
    pair_namestringThe name you gave the pair.
    paired_scorefloat | nullThe paired classifier's score for this heavy/light combination (0–1). null when the pair failed, with error saying why.
    paired_score_classstring | nullWhich class paired_score is the probability of.
    heavyobject | nullThe full per-chain result for the heavy chain, in the shape above.
    lightobject | nullThe same for the light chain.
    errorstring | nullWhy this pair has no paired score.

    Reading the paired score

    paired_score is the probability Humatch's paired CNN assigns to its true class — the classifier's two classes are fake and true. The returned paired_score_class names which one the number refers to, so read it rather than assuming.

    ⚠ Humatch publishes no interpretation bands for the paired score, so none are applied. There is no pass/fail on it, and no threshold: score_threshold governs the per-chain humanness classification only. The number is reported as measured, with no verdict attached, and inventing a cutoff for it means inventing a standard the model's authors did not set.

    Job-level summary

    FieldTypeMeaning
    failed_sequencesstring[]Sequences Humatch could not score.
    success_countintSequences scored successfully.
    fail_countintSequences that failed.
    paired_success_countint | nullPairs that produced a paired score. null — not 0 — when no pair was requested.
    paired_fail_countint | nullPairs that did not. null when no pair was requested.
    partialbooleantrue when at least one sequence or pair failed. Check it before treating the run as complete.
    scheme_usedstringNumbering scheme applied.
    requested_schemestring | nullThe scheme you asked for. Recorded, not applied.
    threshold_usedfloatClassification threshold used.
    paired_score_methodstring | nullHow paired_score was computed. null when no pair was requested.

    Humatch always aligns to IMGT

    numbering_scheme reports the numbering that was actually used, and it is always IMGT. A chothia or kabat request is recorded in requested_scheme and not applied, so position numbers in the result are IMGT whatever you asked for. Compare the two fields before reading a position number across tools.

    Reading the result card

    The Humatch result renders on the canvas as an antibody-structure card, surfacing the humanness score and per-chain read so you can judge the candidate at a glance.

    What to do next

    • Take the flagged_positions to BioPhi and humanize them — Humatch scores, BioPhi rewrites.
    • Cross-check the flagged positions against the paratope so you humanize away from binding residues.
    • Run antibody developability before committing a candidate.

    Was this page helpful?

    On this page

    On this page

    Loading...