Parts of tracks are not shown in IGV

28 views
Skip to first unread message

Katja Hebestreit

unread,
Aug 23, 2012, 9:43:26 AM8/23/12
to igv-...@googlegroups.com
Hello,

It seems that sometimes parts of tracks are not shown in the IGV although I can see the respective rows in the BED file. But when I create a small subset of this BED file the IGV DO show these parts. Thus, I assume that this problem might exist for big BED files only.
I am using IGV 2.1.21.

Since the BED file of question is 200MB of size I can not attach it here. Please contact me and I will provide it.

Thank you!
Best,
Katja

Jacob Silterra

unread,
Aug 23, 2012, 11:41:15 AM8/23/12
to igv-...@googlegroups.com
Hi Katja,

[Note: User has provided data file privately].

It looks like this is a problem with indexing. When the file is indexed several features in the neighborhood of chr1:145139645 do not appear, when it is not indexed they do. I've filed this in our issue tracker at https://github.com/broadinstitute/IGV/issues/14.

As a temporary fix, you can delete the bed index file and those features will show up. This can cause some serious usability problems as it will require a lot more memory by IGV.

-Jacob


--
 
 
 



--
Jacob Silterra
Software Engineer
Broad Institute

Jacob Silterra

unread,
Aug 27, 2012, 10:40:50 AM8/27/12
to igv-...@googlegroups.com
The problem was actually that the input BED file was not sorted. Attempting to create an index of an unsorted file should have thrown an error, but didn't. See GitHub issue #14 for details (resolved as of this writing).


On Thursday, August 23, 2012 11:41:15 AM UTC-4, Jacob Silterra wrote:
Hi Katja,

[Note: User has provided data file privately].

It looks like this is a problem with indexing. When the file is indexed several features in the neighborhood of chr1:145139645 do not appear, when it is not indexed they do. I've filed this in our issue tracker at https://github.com/broadinstitute/IGV/issues/14.

As a temporary fix, you can delete the bed index file and those features will show up. This can cause some serious usability problems as it will require a lot more memory by IGV.

-Jacob

Reply all
Reply to author
Forward
0 new messages