Skip to content

Tuna Birgun

omicau (Omics Audit) is a reproducible, leakage-safe command-line tool, with an optional no-code web interface, that audits a multi-omic dataset before anyone trusts a predictive result.

Core trick

Group-aware cross-validation benchmarks fused omics layers against shuffled-label controls, and a control scoring above chance blocks certification.

Tags

Description

omicau (Omics Audit) is a reproducible, leakage-safe command-line tool, with an optional no-code web interface, that audits a multi-omic dataset before anyone trusts a predictive result. Given one matrix per omic layer (RNA, protein, methylation, and so on) plus a clinical outcome, it aligns the layers, locks them with a value-level SHA-256 provenance hash, and tests for the failure modes that make omics machine learning non-reproducible: information leakage, batch confounding, target-linked missingness, and modality redundancy. It then benchmarks whether combining layers beats the best single layer, under group-aware cross-validation that keeps every subject's samples on one side of the split, and runs three shuffled-label control baselines that gate the result — when a control scores above chance, omicau flags leakage and refuses to certify the score. It writes a one-page executive verdict for clinicians and a research tab with confidence intervals, calibration, and per-layer diagnostics, alongside a DOME methods block and a model card; it runs fully offline, installs from PyPI, and was built with Claude Code. I validated omicau on eight public datasets spanning human, mouse, zebrafish, yeast, and Arabidopsis, across classification, regression, and survival, and checked every result against the published literature. On TCGA-BRCA (PAM50 subtype, RNA+CNV, n=493) it reached AUROC 0.953 with controls at chance and certified the result, while its leave-one-layer-out test put the gain of fusion over RNA alone at +0.006 with a 95% confidence interval spanning zero, so it reported that one layer suffices; on an Arabidopsis Botrytis-infection set (n=12) it reached a perfect AUROC of 1.000, yet the shuffled-target control also beat chance (0.89), so it declined to certify — the correct call when the sample is far smaller than the feature count. This matters because leakage, batch effects, and redundant layers are a documented cause of irreproducible omics machine learning; integration methods (MOFA, MOGONET) and reporting checklists (DOME, TRIPOD+AI) exist, but no tool audits a dataset before modeling for these failures and then declines to certify a score it cannot trust. omicau fills that gap: it tells a researcher — a genomics postdoc, a lab, a clinic — when not to trust their own model, backed by a provenance hash anyone can recompute.
tunabirgun/omicau★ 00 forksPythonMITCreated Jul 7, 2026 · last push Oct 18, 2026

README excerpt

# omicau

`omicau` v0.6.0 is a local command-line and browser-based workflow for multi-omics data auditing and fusion evaluation. It aligns molecular layers, examines missingness and batch information, compares single-layer and fusion models with group-aware resampling, and writes a self-contained HTML report with machine-readable results. The report distinguishes a layer's standalone predictive performance from its added contribution to a specified model and endpoint.

Source and release code: [github.com/tunabirgun/omicau](https://github.com/tunabirgun/omicau). Current aggregate [evaluation results](https://doi.org/10.5281/zenodo.23444757) and the [executed-study protocol](https://doi.org/10.5281/zenodo.23444777) are archived on Zenodo. They document the stable numerical Omicau 0.6.0 evaluation; the [versioned software release](https://github.com/tunabirgun/omicau/releases/tag/v0.6.0) and its assets remain separate.

Ordinary users run `omicau run` or the optional local browser interface. The repository's `benchmarks/` harness and `benchmark_record/` files are archived evaluation materials; they are not invoked by the ordinary run or UI paths.

Research use only. Predictive performance does not establish clinical utility, individual risk, treatment benefit, or causal biology.

## Scope

- Ingest CSV or TSV modality matrices and a clinical table, with orientation detection and sample alignment.
- Audit missingness, batch structure, group structure, and modality availability 

Team