CLI command to view exons seems not working
See original GitHub issueCheck the command:
scout view exons
that returns just one exon:
{‘_id’: ObjectId(‘5f633f4f582d613b6c72dc65’), ‘build’: ‘37’, ‘chrom’: ‘19’, ‘end’: 58864804, ‘exon_id’: ‘19-58864770-58864804’, ‘hgnc_id’: 5, ‘rank’: 1, ‘start’: 58864770, ‘strand’: -1, ‘transcript’: ‘ENST00000263100’}
This command might be redundant since we already have scout export exons
, so check what’s the difference between the 2.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Retrieving Exon and Coding Region Sequences for Genes
You will also see how to retrieve all exon sequences at once and for multiple genes using the EDirect command line interface to...
Read more >Command-line interface for gffutils · Issue #2 - GitHub
I'm interested in: (1) an efficient library for parsing GFF files under the hood, from Python, which ideally is dependency-free (see more on ......
Read more >Gene Frequently Asked Questions - NCBI Bookshelf
The report of intron/exon organization in the Gene Table display is based on the placement of exons and CDS on the genomic sequence....
Read more >Genome Browser User's Guide
To prevent display problems, the Genome Browser imposes an upper limit on the number of alignments that can be viewed simultaneously within the...
Read more >PipTools: Program Reference - the Globin Gene Server
This program attempts to create an exons file from a GenBank entry, and usually does a pretty good job. However, because GenBank entries...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, great that it worked! The
view
vsexport
is a bit vague. The first idea was thatview
where supposed to be used when doing human inspections of stuff in the database, so readable format. Theexport
commands was more for serialising things. Since I guess none of them are used so much one could give it a thought and perhaps merge them.I think that if we merge them we should still keep the option to query just for the exons of one gene, instead of all exons from all genes.