Federated GWAS screening
Coordinate federated quality control, KING-based relatedness screening, and association screening across participating clients so that each site can shrink the set of loci that still need follow-up testing.
A lightweight federated pipeline for privacy-preserving GWAS screening across distributed genomic datasets. Clients keep genotype-level data local while coordinating federated quality control, relatedness screening, and association screening.
Clients exchange encrypted seed shares and other protocol payloads via the server, which forwards messages without decrypting them.
Harmonize sample missingness, SNP missingness, minor allele frequency, and Hardy–Weinberg equilibrium filters across participating clients.
Estimate pairwise kinship with KING and optionally remove related samples before association screening.
Run local logistic-regression filtering with privacy-preserving tokens, then federated case–control logistic regression, while keeping raw genotypes at each client.
Core documentation paths are split by workflow so setup, examples, and reference material stay easy to scan.
Set up Python, PLINK, Flower, and the required runtime tools.
Run the default tiny correctness experiment from data generation to evaluation.
Browse tiny correctness, performance small, and 1000 Genomes workflows.
Look up Flower run config, YAML schema, output files, and Python entry points.
The documentation follows the repository structure so researchers can move from setup to pipeline internals without switching mental models.
Coordinate federated quality control, KING-based relatedness screening, and association screening across participating clients so that each site can shrink the set of loci that still need follow-up testing.
Keep genotype-level computation local while using encryption, shuffling, anonymization, and lightweight secret-sharing. The server relays selected protocol messages without decrypting them.
Run repeatable Flower simulation and local-deployment experiments with scenario-specific configs, logs, and result directories.