Tweet
After a struggle to get samtools successfully installed and working on my windows machine, I'm now having trouble (I think) indexing a bam file. I'm using cygwin to use samtools. I'm planning on visualizing a metagenomic sequence for SNP screening in IGV but the bam file format isn't supported. A message pops up saying that the bam file needs to be indexed. In samtools I'm using ./samtools sort <file.bam> <file.sorted> and a sorted file is successfully made. However when I go to index the file using ./samtools index file.sorted.bam a 24kb file is made. Is there something I'm doing wrong here? Thank you all for your help so far.
-
-
IGV supports .bam files. I look at indexed .bam files all the time on IGV. It woud be rather useless software if it didn't handle .bams. 24 kb sounds about right for the index. Make the index, then try to load the .bam into IGV. -
IGV will also index them for you if you do not have one.Comment
-
When I try to load a .bam file it tells me it needs to be indexed. Do I have to load both the .bam and the index simultaneously?Comment
-
No, just load the .bam. IGV will lok for a .bam.bai with the same name in the directory with the .bam, and when it finds it, it will work.Comment
-
Thank you for your help guys, I got it to work.Comment
-
Hi,
I'd like to make a slight correction for the benefit of future googlers. IGV will not create an index for a BAM file, although we might add this in the future. Use samtools or Picard to create such an index. It will index a SAM file for you, that is an IGV specific index created before the BAM index spec and implementation were finished, i.e. a long time ago. We keep it for backward compatibility, but it is not the same index as the BAM file index.
JimComment
-
Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.07-01-2026, 11:43 AM
-
I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.
Here are nine questions we think about, in roughly the order they matter, before...
Comment