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
I got two issues when visualizing bed files. My bed files contain information of SNPs, where end-start=1.
when the data is very sparse, like 15 rows, the GIVE browser would show nothing even when I zoom in to certain coordinate.
when the data is dense, like 50k rows, GIVE browser does show the data. but when I zoom in to a smaller coordinates range, the figure would just disappear. and when I zoom out, it would appear again.
Can I fix this?
The text was updated successfully, but these errors were encountered:
We didn't encounter this problem before. Could you please show us the screenshots of your problem? Could you share your sample data with us? Maybe we can have some test.
Hi, thank you for your reply. Here is the link to screenshots and test data.
Among all the bed files, gwas13.bed has 13 rows, and it can be seen as a "threshold". It means in a range of 1000 of coordinates, if the file has more than 13 rows, it can be shown in the panel. While if the file has less than 13 rows, there would be nothing in the panel.
Also, you can see gwas10+5.bed, it has 10 rows from 30000059 to 30000863 and 5 rows distributed in other coordinates. And this file cannot be shown in the panel.
As to the screenshots, I first set the coordinates as chr10: 29933189-30130094 and there is a visualization in the panel. But when I keep zooming in, the visualization would disappear. Please check the two screenshots for reference.
And I think the key point here can be explained as "why I cannot visualize the bed file which contains only one row and the difference between start and stop is only one". There should be one line on the screen.
Thanks for your help!
I got two issues when visualizing bed files. My bed files contain information of SNPs, where end-start=1.
Can I fix this?
The text was updated successfully, but these errors were encountered: