You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each table available via EnsemblDb (e.g. genes, promoters) we could rename the primary genomic coordinates to the format required by bioframe (e.g. chrom, start, end). This would (a) mimic the behaviour in bioconductor (where ranges make the IRange column) and (b) allow selecting columns with additional coordinates in the ibis query (e.g. add tx_seq_start column when running genes#9 ).
The text was updated successfully, but these errors were encountered:
ensembldb and GenomicFeatures both return a GRanges which contains seqnames, ranges, and strand, for the entity being queries (e.g. genes, transcripts). This is nice because it can be directly used with genomic range libraries.
We could also provide (maybe with opt-out) the main entity's features in a way that will automatically work with bioframe.
Description of feature
For each table available via EnsemblDb (e.g.
genes
,promoters
) we could rename the primary genomic coordinates to the format required bybioframe
(e.g.chrom
,start
,end
). This would (a) mimic the behaviour in bioconductor (where ranges make the IRange column) and (b) allow selecting columns with additional coordinates in the ibis query (e.g. addtx_seq_start
column when runninggenes
#9 ).The text was updated successfully, but these errors were encountered: