SEPIA  ·  ← roadmap  ·  all docs

Gene-network datasets inventory — `tinalasisi/pigmentation-gene-network`

Gene-network datasets inventory — tinalasisi/pigmentation-gene-network

Purpose. SEPIA item B1 prep: catalog every dataset the public repo tinalasisi/pigmentation-gene-network provides, so we can plan folding its richer, gene-level pigmentation data into SEPIA (the "bigger goal" beyond Lily's 222-SNP panel).

Provenance of this inventory. Cloned https://github.com/tinalasisi/pigmentation-gene-network at commit 7618746 (2026-07-13). Every count, column, DOI, and build below was read directly from the repo's committed DATA_SOURCES.md and by inspecting each file's header + rows. Where a figure below differs from DATA_SOURCES.md, the file-actual value is given and the difference noted. Nothing here is inferred beyond what was read; missing items are called out as missing.


Build reality (read this first — it is not "all hg38")

DATA_SOURCES.md and SEPIA plan.md §5 both describe the repo as "hg38." That is true for the two pieces SEPIA most cares about, but not uniform across the repo:

Implication for SEPIA's B2 bridge: rsID is the only field common to all SNP-level sources, which is exactly why the B2 plan keys the hg19↔︎hg38 map on rsID. Coordinate columns in these files cannot be trusted to be hg38 without checking the per-file coord_build tag.


Source index (what the repo provides)

# Dataset Level File(s) read Rows rsIDs / genes Build
1 GWAS Catalog pigmentation (deduplicated) SNP data/external/gwas_catalog/pigmentation_gwas_catalog.csv 1,072 1,072 unique rsIDs hg38
1b GWAS Catalog pigmentation (granular, per-association) SNP data/external/gwas_catalog/gwas_pigmentation_associations.csv 723 472 unique rsIDs · 723 gene–SNP assoc (rsID + gene)
2 Bajpai 2023 genome-wide CRISPR screen hits gene data/processed/bajpai2023_crispr_hits.csv 169 169 genes (Symbol+Ensembl) n/a
3 Baxter 2018/19 curated cross-species gene list gene data/processed/baxter2018_650_pigmentation_genes.csv 659 635 w/ human symbol n/a
4 HIrisPlex-S (Chaitanya 2018) forensic markers SNP data/processed/hirisplexs2018_markers.csv 36 36 rsIDs → 16 genes rsID only
5 Raghunath 2015 melanogenesis backbone gene/network data/processed/raghunath_nodes_typed.csv + ..._edges_typed_signed.csv 265 nodes / 429 edges 265 nodes (genes+metabolites) n/a
6 D'Arcy 2023 OMIM disease genes (Table S1) gene data/processed/darcy2023_S1_disease_genes.csv 278 243 unique genes n/a
6b D'Arcy 2023 STRING PPI network (Tables S4/S5) gene/network darcy2023_S4_string_edges.csv / _S5_string_nodes.csv 4,668 edges / 452 nodes 452 genes n/a
6c D'Arcy 2023 mass-spec expression (Table S6) + sys/GO (S2) gene darcy2023_S6_massspec_expression.csv / _S2_sysgo_annotation.csv 4,232 / 243 4,232 / 243 genes n/a
7 Assembled gene network (Notebook 2 output) gene/network data/processed/gene_network_nodes.csv + _edges.csv 168 nodes / 309 edges 168 genes (entrez/ensembl/chr) hg38 (gene coords)
— Additional SNP extractions (Martin, Kim, discordance/case studies) SNP see "Additional SNP-level sources" below — — hg19

The five SEPIA §5 "four datasets + prediction panel" map to rows above: GWAS Catalog (1/1b), CRISPR = Bajpai (2), cross-species = Baxter (3), melanogenesis network = Raghunath (5), PPI expansion = D'Arcy (6/6b/6c), prediction panel = HIrisPlex-S (4).


Per-dataset detail

1 · GWAS Catalog — pigmentation associations (SNP-level, hg38)

2 · Bajpai 2023 — genome-wide CRISPR screen (gene-level)

3 · Baxter 2018/19 — curated cross-species gene list (gene-level)

4 · HIrisPlex-S — Chaitanya 2018 forensic prediction markers (SNP-level) ★

5 · Raghunath 2015 — directed melanogenesis backbone (gene/network)

6 · D'Arcy 2023 — OMIM disease genes + STRING PPI + mass-spec (gene/network)

7 · Assembled gene network — Notebook 2 output (gene/network, hg38 gene coords)

Additional SNP-level sources (present, hg19 — beyond the SEPIA §5 five)

These are extra rsID-bearing tables the repo also ships. They are hg19/GRCh37 and are relevant to SEPIA only if the panel is extended beyond the §5 set:


Integration into SEPIA

SEPIA's plan (plan.md B1/B3/B6) already splits sources into SNP-level (feed the directional polygenic score B3 + panel PCA) vs gene-level (gene-region PCA B4-ii, layered coverage B1, functional interpretation B7). This inventory confirms and quantifies that split.

A. rsID SNP-lists → fold into the hg19↔︎hg38 panel map (B2), extend the panel (B1/B3)

These have rsIDs, so B2's rsID ↔︎ hg19 ↔︎ hg38 map can resolve them and we can pull archaic/SGDP genotypes at each locus and report on hg38:

Source rsIDs In SEPIA 222-panel already New to the panel Note
GWAS Catalog dedup 1,072 212 ~860 Panel is essentially a subset of this pull; carries or_beta/direction_raw for B3 signs
HIrisPlex-S 36 15 21 Adds the MC1R red-hair extras (rs1110400, rs2228479, rs3212355), OCA2 (rs1470608/rs1545397/rs12441727), TYR rs1393350, TYRP1 rs683, KITLG rs12821256, etc.
Martin 2017 (KhoeSan) 49 15 ~34 hg19 already — but African-ancestry axis; optional
Kim 2024 (East Asian) 26 1 ~25 hg19; almost entirely novel to the panel
GWAS granular assoc 472 43 — per-gene replication counts, not new loci

Overlap method / caveat: SEPIA's 222 panel positions (data/snps.txt, hg38) map cleanly to 222 rsIDs via data/skin_pigmentation.tsv (the panel's GWAS-Catalog source table, 226 unique rsIDs). Overlap counts above are rsID-set intersections against those 222 (identical whether measured against the 222-mapped set or the 226-rsID source table, ±1). So:

Build handling: fold these in by rsID, not by coordinate. Only the GWAS Catalog rows are natively hg38; HIrisPlex-S is rsID-only and Martin/Kim are hg19. B2's dual-coordinate dbSNP re-pull (keyed by rsID) is exactly the right mechanism, and nb4_unified_association_base.csv is a ready-made union to seed the map (it already stores rsid+pos_hg38+coord_build per row).

B. Gene-level → B6 (genes-vs-SNPs) / B4-ii (gene-region PCA) / B7 (functional)

No per-SNP genotype; used as gene-region sets (take each gene's Ensembl start/end, use all variants inside) or for network/functional interpretation — never in the +1/−1 directional score:

These need gene coordinates from Ensembl/BioMart on the matched build (SEPIA plan B4-ii/B6 already specify this); the repo supplies symbols/Ensembl IDs, not coordinates (except the 168-node assembled network's chr), so a coordinate join is required regardless.

C. What is NOT in the repo (do not assume)