Run reproducible workflows for GWAS, polygenic scores, TWAS, fine-mapping,
Mendelian randomization, and genomic selection across human, animal, and plant research.
Build, compare, and connect polygenic scores, transcriptome-wide
associations, credible sets, causal estimates, and genomic
predictions—without rebuilding the workflow for every method.
Detect formats, align alleles and genome builds, validate IDs, and register reusable LD and omics resources.
02
Compose analyses
Mix prediction, association, fine-mapping, causal inference, and multi-omics engines in a single project manifest.
03
Interpret together
Compare methods, connect variant-to-gene-to-trait evidence, and export dashboards, models, logs, and provenance.
Analysis workspace
OmniGenet analysis
Configure input data, select statistical-genetics methods, review
the generated job, and submit it to the OmniGenet server.
OmniGenet analysis
PRS · Single-trait
Upload and validate summary statistics, then select methods and run the analysis.
Inputs and species registry
Upload input file
Files are saved under the backend resources folder and can be used by the paths below.
No file uploaded yet.
Evidence-based upload diagnosticsAfter upload, OmniGenet will check file structure, missingness, identifiers, and supported genetics-specific fields.
Universal QC and harmonization
Method engines
Genomic prediction · Single-traitCompare statistical, machine-learning, and deep-learning prediction engines for one target trait.
Upload GWAS
Upload summary statistics directly. OmniGenet detects the format, checks scientific fields, and inserts the stored path into the selected workflow.
Upload once for plots, PRS, TWAS, fine-mapping and MR
Target cohortUsed by the standard PRSice-2 workflow.
Independent validation data (optional)
Upload a non-overlapping cohort only when using independent tuning + target validation.
For PLINK data, upload the matching .bed, .bim, and .fam files one at a time under the same genotype role.
Column identifiers are suggested after inspection. Review the mapping before building the analysis plan.
No summary-statistics file uploaded.
Summary-statistics readiness checkAfter upload, OmniGenet will inspect identifiers, effect columns, allele fields, missingness, and basic format consistency.
Loaded automatically · blupSUP phenotype.txt
Phenotype summary
Method readinessUpload the required summary-statistics files to see which selected methods can run now and which need an LD panel, expression model, or additional dataset.
Fields marked with an asterisk (*) are required; all others are optional.
GS / genomic selection
Configure breeding-value and genomic-prediction engines for local, server-side, or HPC runs.
PRS
Choose polygenic-risk-score engines and scoring strategies for human, animal, or plant prediction studies.
Summary-first mode: target genotype and phenotype are optional. With summary statistics alone, OmniGenet produces downloadable SNP-weight files. Upload a target cohort only when individual scoring or accuracy evaluation is required.
GWAS visualization
Create publication-ready diagnostic figures directly from uploaded summary statistics—no target genotypes or phenotypes are required.
TWAS / omics
Select transcriptome-wide or omics-association engines for expression, protein, or methylation data.
LDSC
Estimate SNP heritability and optional pairwise genetic correlation from GWAS summary statistics.
Fine mapping
Specify credible-set, cross-population, and colocalization engines for locus-level interpretation.
MR
Choose Mendelian-randomization engines and sensitivity methods for causal-inference workflows.
Result integration
Outputs and reports
Choose methods and run
Analysis summary
Review the selected methods, resolved inputs, expected figures, and output location. OmniGenet validates all requirements automatically before analysis.
BackendGS / ML-DL
Selected method
TraitGY1
Outputgs_wheat_lightgbm
Resolved inputsAwaiting uploaded data
Automatic outputFigures, tables, and an HTML report
Advanced · Reproducibility filesManifest, command, and local/HPC runnerExpand
TSV task rows remain available inside the downloaded bundle and are submitted to the backend automatically.
Server execution
OmniGenet automatically validates the workflow first. Analysis starts immediately after all preflight checks pass.
OmniGenet creates a job manifest, validates inputs, launches the
selected method engines, records logs, and keeps the generated
runner script for reproducible local or HPC execution.
1
Define the workflow
Select datasets, QC modules, method engines, integration modules, and requested result products.
2
Run through the server
The backend writes job-specific configuration, starts a dry-run, streams logs, and can launch the real analysis.
3
Export reproducibly
Download model lists, manifests, logs, result files, and runner scripts for local reruns or auditing.
6Reproducible runner scripts for local machines, servers, and HPC environments.
Local and server execution
Run the same analysis through the web or command line
The included FastAPI backend accepts uploads, builds job-specific
manifests, runs validation and Snakemake dry-runs, streams logs, and
exposes result files for download.