Exclusion Mismatch Tolerance

Count exact diploid STR genotype mismatches against a caller-defined tolerance; not a paternity conclusion.

Description

Exact diploid genotype agreement can be audited across STR loci.

Exact diploid genotype agreement can be audited across STR loci. Allele ordering within an unphased pair should not create a mismatch.

Count exact diploid STR genotype mismatches against a caller-defined tolerance; not a paternity conclusion.

When to use Exclusion Mismatch Tolerance

Use this for the following task: Count exact diploid STR genotype mismatches against a caller-defined tolerance; not a paternity conclusion.

Prepare the observed records or explicit model parameters requested below. Keep probabilities as fractions and paired records aligned.

How to use Exclusion Mismatch Tolerance and understand its results

  1. Prepare the observed records or explicit model parameters requested below. Keep probabilities as fractions and paired records aligned.
  2. Enter locusNames, firstAlleles, secondAlleles, maximumMismatches using the field table, then run the tool.
  3. Read mismatchedLoci, mismatchCount, withinTolerance. Interpret flags, units, ordering and placeholder values using the rules below.
  4. Review any reported issue or failed check, correct the supplied values when appropriate, and verify the result in its intended context.
Input fieldMeaningValue type and boundsRequirement
locusNamesLocus nameslist of string; each entry: stringRequired
firstAllelesFirst alleleslist of string; each entry: stringRequired
secondAllelesSecond alleleslist of string; each entry: stringRequired
maximumMismatchesMaximum mismatchesintegerRequired

Align locus names and explicit two-allele slash-separated calls. Trim individual alleles, sort each pair and compare exact normalized strings.1

mismatch if sorted trimmed allele pairs differ; withinTolerance = mismatches ≤ maximum

This summarizes the declared operation. Units, indexing, inclusivity and exceptional cases are explained in the surrounding text.

Output fieldMeaningValue type
mismatchedLociMismatched locilist of string
mismatchCountMismatch countnumber
withinToleranceWithin toleranceboolean
json
{
  "input": {
    "locusNames": [
      "A",
      "B",
      "C"
    ],
    "firstAlleles": [
      "12/13",
      "10/11",
      "8/9"
    ],
    "secondAlleles": [
      "12/13",
      "10/10",
      "8/9"
    ],
    "maximumMismatches": 1
  },
  "output": {
    "mismatchedLoci": [
      "B"
    ],
    "mismatchCount": 1,
    "withinTolerance": true
  }
}

Limitations and assumptions

Different spellings remain distinct. This is genotype equality, not parent-child compatibility, a paternity conclusion or a probabilistic identity test.

The tool evaluates supplied observations or a declared model. It does not establish the biological cause of an observed pattern. Malformed requests produce input errors. A successfully evaluated request can still contain false flags, empty result lists or a result outside the supplied threshold; those outcomes have the meanings stated above.

Alternative or Complementary methods

Choose Multilocus Genotype Match for this operation: Calculate theta-adjusted genotype match probabilities and their independent-locus product and log score. For a complementary task, use STR Panel Completeness for this operation: Audit STR panel completeness against a caller-supplied locus set, not an embedded legacy policy.

The implementation reference documents the exact calculation, supported input shapes and returned fields.

References

  1. Exclusion Mismatch Tolerance — tool.io

Similar or alternative tools

  • Multilocus Genotype Match

    Calculate theta-adjusted genotype match probabilities and their independent-locus product and log score.

  • STR Panel Completeness

    Audit STR panel completeness against a caller-supplied locus set, not an embedded legacy policy.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies