1-based or 0-based coordinates?
Refgenie follows one rule everywhere it reads a region of a genome:
- A region written as text is 1-based and inclusive, like samtools, UCSC and IGV.
chr17:43,044,295-43,044,394means base 43,044,295 through base 43,044,394, which is 100 bases. Commas are allowed. This is howrefgenie getseq -land the Extract tab on refgenie.org read a region. - Separate start and end numbers are 0-based and half-open, like the GA4GH refget API.
start=43044294, end=43044394is the same 100 bases: the first base is number 0, and the end base is not included. This is how the MCP toolget_sequenceand the Python API read a region. BED files are 0-based and half-open too.
To turn a text region into start and end numbers, subtract 1 from the start and keep the end.
The same 100 bases, four ways
Section titled “The same 100 bases, four ways”These all return the same 100 bases of hg38, at the 3' end of BRCA1 (a minus-strand gene), starting TGGAAGTGTTTGCTACCAAG.
On the command line:
refgenie getseq -g hg38 -l chr17:43,044,295-43,044,394If your text region is already 0-based, for example copied from a BED file, add --zero-based:
refgenie getseq -g hg38 -l chr17:43044294-43044394 --zero-basedEither way, getseq prints how it read the region on stderr, so you can check it: chr17:43,044,295-43,044,394 (1-based, inclusive): 100 bases.
From an AI assistant, over MCP:
get_sequence(alias="hg38", name="chr17", start=43044294, end=43044394)From Python, once the genome is registered (any refgenie getseq or refgenie pull does that):
from refgenie import Refgenie
rgc = Refgenie()rgc.sequence.get(rgc.alias.resolve("hg38"), "chr17", 43044294, 43044394)