Overview
***************************************
We want an extremely fast, lightweight way to access gene data stored in GTF format.
The parsed data is held in an intuitive
Gene
-> transcript
-> transcript
with exons being stored as intervals
Our aim is to
* cache data in binary format, which can be
* re-read in < 10s for even the largest genomes
Currently initial parsing Ensembl Homo sapiens release 56 takes around 4.5 minutes.
The binary data can be reloaded in < 10s.
This contains *all* of the data structure in the original GTF file
Note that we sacrifice memory usage for speed. This is seldom a problem for modern computers
and genome sizes (There are around ~400,000 exons but there are stored as intervals / int pairs)
***************************************
A Simple example
***************************************
::
gene_structures = t_parse_gtf("Mus musculus")
#
# used cached data for speed
#
ignore_cache = False
#
# get all protein coding genes only
#
genes_by_type = gene_structures.get_genes(gtf_file, logger, ["protein_coding"], ignore_cache = ignore_cache)
#
# print out gene counts
#
t_parse_gtf.log_gene_types (logger, genes_by_type)
return genes_by_type
Metadata
Release files for gtf_to_genes 1.40
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gtf_to_genes-1.40.tar.gz | 35.6 kB | Without provenance | Details for gtf_to_genes-1.40.tar.gz |
Release files / gtf_to_genes-1.40.tar.gz
| Download URL | gtf_to_genes-1.40.tar.gz |
|---|---|
| Size | 35.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2b74884aebfcd58d786e5c6af9af19723a1864b2ac2544bf8d008aac31d96b8
|
|
BLAKE2b-256 checksum How to use checksums |
351deb9f5d711ee1b9717f8cfc41eadd0086066a08b99e35da95a0a42a1ae266
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gtf_to_genes 1.40
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.