Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • drea11
    Junior Member
    • Aug 2014
    • 9

    Extracting Regions of Zero Coverage

    I am looking for a quick and simple way to identify regions of zero coverage in a sequencing set. My ultimate goal is to try and determine whether there might be genomic features which contribute to this.

    I've used both GATK and Samtools depth to identify the depth of coverage at each base position across my genome. What I'd like is to have the base positions for each REGION which are not covered (ie. 2307-2412). I have depth of coverage on many samples, and would like to have a quick way of getting this information across all of them. Are there any functions out there which could do this? Am I better off just sticking with some sort of bash command?

    Below is a sample of what the output of GATK is (depthofcoverage) as an example.

    Locus Total_Depth Average_Depth_sample Depth_for_s1 Depth_for_s2 Depth_for_s3
    genome:1 283 94.33 82 111 90
    genome:2 284 94.67 82 111 91
    genome:3 285 95.00 82 112 91
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    I imagine that tabix indexing/fetching would be useful here. That's the basis for things like indexing VCF files.

    Comment

    • drea11
      Junior Member
      • Aug 2014
      • 9

      #3
      Thanks for the speedy reply. Could you perhaps elaborate on your answer a bit? I'm not familiar with tabix, and the online documentation seems somewhat unspecific.

      Comment

      • piet
        Member
        • Aug 2014
        • 21

        #4
        Originally posted by drea11 View Post
        I'd like is to have the base positions for each REGION which are not covered (ie. 2307-2412)
        Maybe the 'genomecov' subcommand from 'bedtools' with option '-bga' is useful for you.

        Comment

        • dpryan
          Devon Ryan
          • Jul 2011
          • 3478

          #5
          Originally posted by drea11 View Post
          Thanks for the speedy reply. Could you perhaps elaborate on your answer a bit? I'm not familiar with tabix, and the online documentation seems somewhat unspecific.
          If we modify your file slightly so that the contig and position are in different columns and replace spaces with tabs:
          Code:
          Locus	Pos	Total_Depth	Average_Depth_sample	Depth_for_s1	Depth_for_s2	Depth_for_s3
          genome	1	283	94.33	82	111	90
          genome	2	284	94.67	82	111	91
          genome	3	285	95.00	82	112	91
          Then we can:
          Code:
          bgzip foo.tab
          tabix -b 2 -e 2 -f -s 1 -S 1 foo.tab.gz #This will index the file
          tabix foo.tab.gz genome:2-3
          The last command will output the last 2 lines. Of course if you have a LOT of lines and multiple contigs/chromosomes/genomes, then this is more useful than the small example. The biggest benefit to this method is that you can randomly ask for ranges without needing to process everyline until you get to that range (if you've ever dealt with indexed VCF or BAM files, it's the same underlying principle). This is actually how IGV and many other tools randomly access VCF and BED files.

          Note that the bgzip utility is really just a special version of gzip, so you can view the resulting files with zcat or even just gunzip them.

          Comment

          Latest Articles

          Collapse

          • GATTACAT
            Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by GATTACAT
            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
          • SEQadmin2
            Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by SEQadmin2


            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...
            06-18-2026, 07:11 AM

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, Yesterday, 11:08 AM
          0 responses
          6 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          11 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          19 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-17-2026, 06:09 AM
          0 responses
          53 views
          0 reactions
          Last Post SEQadmin2  
          Working...