Generate a PharmCAT pharmacogenomic report from raw VCF and BAM sequencing files.
Avoid Docker Hub image-pull failures by running PharmCAT with plain Java instead.
Automatically call CYP2D6 genotype from a BAM file using Aldy.
Batch process genomic data from services like sequencing.com into readable reports.
| excellent-push2883/war_cat | ayush-sk-pathak/claude-code-starter-pack | bitman-sachs/minimax-m3-tp3-rtx6000 | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Shell | Shell | Shell |
| Setup difficulty | hard | easy | hard |
| Complexity | 4/5 | 2/5 | 5/5 |
| Audience | researcher | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires Java 17+, several genomics command line tools, and on Windows a WSL environment, not a clinical tool.
WAR_CAT is a script that automates running a genetics analysis tool called PharmCAT, which produces a pharmacogenomic report, meaning a report about how a person's genetic makeup might affect how they respond to certain medications. It takes raw genomic sequencing files, such as VCF or gVCF files and optionally BAM files, and turns them into a finished PharmCAT report without requiring the user to run each step of the pipeline by hand. A notable design choice is that it runs PharmCAT using plain Java rather than Docker, specifically to avoid Docker Hub network failures that can happen when pulling container images. It installs PharmCAT by downloading a specific pinned version directly from GitHub instead. The pipeline detects the input files, figures out whether they are gVCF or plain VCF format and checks the chromosome naming convention used, downloads a matching reference genome, builds a working VCF file by either re-calling from a BAM file or expanding the gVCF, and removes a particular data field that would otherwise cause the normalization step to crash. If a BAM file is present, it also calls a specific gene called CYP2D6 using a tool named Aldy. It then runs PharmCAT's own preprocessing step and finally generates an HTML report. Running it requires Java 17 or newer along with several genomics command line tools, and on Windows the whole process is meant to run inside WSL rather than through Docker Desktop. The first run downloads PharmCAT itself along with two reference genome files, each around 0.9 gigabytes, but these are cached so later runs are much faster. Several environment variables let you override details like which PharmCAT version to use or force a specific CYP2D6 result. The README explicitly states this is not a clinical tool and that anything important produced by the report should be confirmed before being acted on. It also notes the pipeline has been verified against genomic data from sequencing.com and that patches may still be needed.
A script that automates running PharmCAT on raw genomic sequencing files to produce a pharmacogenomic report, without needing Docker.
Mainly Shell. The stack also includes Shell, Java, Python.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly researcher.
This repo across BitVibe Labs
Verify against the repo before relying on details.