Open data: which markers are on the chip your DNA file came from

Coverage across the five published arrays

Of the 70 markers in the dataset, this is how many each published array carries:

Read "missing" as: this array has no probe for that locus. A consumer chip built on one of these arrays may add custom probes of its own, so a gap in the backbone is not automatically a gap in the chip — and no consumer vendor publishes a per-chip manifest.

What the data shows

Five findings, each worked through case by case in notable-gaps.md.

Where a call comes from

Not every row rests on the same kind of evidence, and the evidence column says which. In descending order of what it settles:

• manifest — read directly from a published array manifest. Definitive for that array.
• public_file_observation — the marker was seen, or not seen, in files produced by the product itself. Definitive for what the product ships, including custom content a manifest cannot describe.
• backbone_manifest_family — inherited from a backbone family whose revisions all agree.
• no_public_manifest, family_revisions_disagree — nothing public settles it; the call is unknown and the notes say why.

Cite it

Each release is archived on Zenodo with a DOI. The DOI below always resolves to the latest version.

DOI

https://doi.org/10.5281/zenodo.21708539

Attribution string

dna-chip-coverage by Andrey Soloviev, CC BY 4.0 — https://github.com/AndreySoloviev/dna-chip-coverage

BibTeX

@dataset{dna_chip_coverage,
  title     = {dna-chip-coverage: SNP marker coverage across
               consumer DNA genotyping arrays},
  author    = {Soloviev, Andrey},
  year      = {2026},
  publisher = {Zenodo},
  doi       = {10.5281/zenodo.21708539},
  url       = {https://doi.org/10.5281/zenodo.21708539}
}

The repositories

Licence

Data and documentation are CC BY 4.0; the code in scripts/ is MIT. Use it commercially, modify it, redistribute it — attribution is the only condition.

The array manifests the dataset is derived from remain the property of their publishers and are not redistributed; the build script downloads them from the original source. Coverage tells you whether a question can be asked of a file, not what the answer means — for clinical interpretation of any marker, consult ClinVar, PharmGKB or CPIC, and a clinician.