Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BED tracks don't show gene names #90

Open
rikrdo89 opened this issue Feb 17, 2019 · 5 comments
Open

BED tracks don't show gene names #90

rikrdo89 opened this issue Feb 17, 2019 · 5 comments

Comments

@rikrdo89
Copy link

rikrdo89 commented Feb 17, 2019

The browsers does not show the gene names when a bed file its uploaded. It only shows the regions as boxes of different colors, but the gene names are not shown neither inside of the boxes or next to them. is there a way to configure this feature?

Sample bed I used in the Genome Browser v46.1
chr5 61337895 61338733 Gm43382 . - ENSMUSG00000106370.2
chr5 61602569 61603038 Gm43383 . - ENSMUSG00000105675.1
chr5 61717029 61717666 Gm43384 . - ENSMUSG00000105573.2
chr5 61808815 61811163 G6pd2 . + ENSMUSG00000089992.3

@lidaof
Copy link
Member

lidaof commented Feb 18, 2019

Hi @rikrdo89 , possible you can use bed format? bed format will display the 4th column as name and also indicate the direction. See http://wiki.wubrowse.org/Simple_bed for more information please.

@rikrdo89
Copy link
Author

I'm sorry, I meant to say BED. I edited the question.

@rikrdo89 rikrdo89 changed the title BAM tracks don't show gene names BED tracks don't show gene names Feb 18, 2019
@lidaof
Copy link
Member

lidaof commented Feb 18, 2019

@rikrdo89 , ha, i see, sorry for that. can you refresh the web browser and re-try? is should show up now.

image

@rikrdo89
Copy link
Author

Hi @lidaof
I just tried and the issue doesn't seem to have been resolved. I am attaching the screenshot of what I get in the browser using the same dataset I posted earlier and uploading the track locally.

image

@lidaof
Copy link
Member

lidaof commented Feb 22, 2019

I see, could you please refresh your web browser until see v46.2 and test? just want to check not a cache issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants