Utilities
Check contig naming before combining genomic files
genomic-contig-check is an offline contig-naming and assembly-compatibility checker.
overview
What genomic-contig-check does
Identify the genome assembly and contig naming behind BED/GTF/GFF3/VCF/FASTA-index/sizes files and check that they can be joined (chr-prefix and assembly mismatches) with K-Dense's genomic-coordinates check_contigs. JSON report; offline.
Compare 1 to 10 BED, GTF, GFF3, VCF, FASTA-index or chromosome-size files, optionally against reference genome sizes. Return JSON with per-file contig information, naming styles, assembly hints, incompatibilities and the script log.
Paths must stay within the supplied folder; the limit is 1 GiB per file. Assembly hints use a built-in primary-chromosome length table. Interval coordinates alone are often ambiguous. Incompatible or unidentifiable inputs are successful report data with compatible false; invalid paths and usage fail.
Packaged version: 065b734. Upstream license: MIT.
use cases
Where genomic-contig-check fits
Catch chromosome-name mismatches
Compare plain 1 and chr1 naming before a join.
Check reference compatibility
Include chromosome sizes or a FASTA index as the reference.
Keep uncertain assembly hints visible
Distinguish a recognizable length table from ambiguous interval-only evidence.
reference
genomic-contig-check inputs and flags
| Name | Type | Flag | Description |
|---|---|---|---|
| source | FOLDER | --source | Folder holding the genomic files to compare. |
| files | STRING | --files | Comma-separated paths inside the folder (1–10), e.g. variants.vcf,annotation.gtf,ref.fa.fai; each at most 1 GiB. |
| genome | STRING | --genome | Optional chrom.sizes or .fai path inside the folder to compare every file against. |
Showing key inputs. genomic-contig-check exposes 3 inputs in total.
example
Run genomic-contig-check
python3 /app/run.py --source ./source --files nochr.bed,chr.bed --genome hg38.sizes ./outputguidance
Choosing genomic-contig-check
Use genomic-contig-check before joining files that may mix chr-prefixed and plain contigs. It does not rewrite names, lift coordinates between assemblies or prove the correct assembly for an arbitrary interval file. Interval validation and set arithmetic are separate jobs.
faq
genomic-contig-check questions
related
More Utilities tools
browser-fetch
Headless Chromium render: requested URL, final URL, status, and title next to the page.
cewl
Spider a URL and return a wordlist for password crackers.
csvkit
SQL on one CSV. The table name is the file stem.
dnsgen
Wordlist and mined-word subdomain permutation.
duckdb
In-process SQL on CSV, JSON, and Parquet. No server.
edge-tts
Microsoft Edge neural speech from text or a script file. No API key.
Run genomic-contig-check yourself
The saved fixture verifier confirmed GRCh38/hg38 from reference lengths and a mismatch between plain and chr-prefixed BED contigs. The complete native JSON was not retained. The command shows the container entrypoint with example paths.
Facts on this page come from the live Trickest tool library.