Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • haiwan
    Junior Member
    • Nov 2013
    • 6

    how do you describe the sequencing depth of your sequencing data

    Hello everyone,

    i am a junior research. I have worked on the deep sequencing for human miRNA profiling in human plasma samples. I recently prepared the manuscript relating to miRNA profiling obtained by Solexa sequencing.

    During the preparation, i have encounter an issue about the sequencing depth. I already looked up the literature. Though i understood what the depth is, i am still confused with this concept.

    The common description of coverage is shown as 30X, for example.

    So, my question is like that:
    How do you depict the coverage of miRNA sequencing data? Is it according to the equation referring to C=LN/G was used to calculate the coverage, where C stands for coverage, G means the haploid genome length, L is the read length, N is the number of reads?


    thanks a lot for help.

    sincerely,
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    Just use the number of reads and percentage uniquely aligned. Coverage only makes sense in the context of DNA.

    Comment

    • haiwan
      Junior Member
      • Nov 2013
      • 6

      #3
      thank you for your reply.
      i am still confused. how do you specify the coverage if the reviewer ask you this question?

      with best,

      Comment

      • dpryan
        Devon Ryan
        • Jul 2011
        • 3478

        #4
        You tell them that what they're asking is meaningless and they should learn to stop making stupid requests. Of course, you don't phrase it like that.

        Something of the form: "We thank the reviewer for his/her helpful remarks. Regarding reporting coverage, there is unfortunately no straight-forward way to do so with miRNA profiling (or RNAseq in general). A single coverage metric is quite meaningful in many high-throughput sequencing applications, since relatively uniform coverage is expected. Common forms of RNAseq, however, do not and should not produce even remotely uniform coverage of known or unknown transcripts. This is due to the vast concentration range that various RNAs can assume. A coverage metric, then, can be quite misleading in this context, particularly since many transcripts are simply not expressed in a given context."

        Something along those lines will work. The thing is just that the reviewer doesn't know much about NGS, but has just read enough papers to know a bit of the lingo.

        Comment

        • GenoMax
          Senior Member
          • Feb 2008
          • 7142

          #5
          I wonder if the choice of the word "coverage" by haiwan was not precise enough in the original post.

          Perhaps the metric should have been "depth" observed in the actual data collected for this experiment.

          Comment

          • dpryan
            Devon Ryan
            • Jul 2011
            • 3478

            #6
            The two are often synonyms, so I would try to avoid them both.

            Comment

            • haiwan
              Junior Member
              • Nov 2013
              • 6

              #7
              thank you for reply.

              it is more and more confusing. I understood there is a bit difference existing between coverage and depth.
              if yes,
              How do you know depth for your data? Can you calculate according to some sort of the equation? The technician would know the sequencing depth because she/he sets the parameters for the specific aims?





              Originally posted by GenoMax View Post
              I wonder if the choice of the word "coverage" by haiwan was not precise enough in the original post.

              Perhaps the metric should have been "depth" observed in the actual data collected for this experiment.

              Comment

              • GenoMax
                Senior Member
                • Feb 2008
                • 7142

                #8
                Some additional points of view.







                Based on the data at hand "how many times a particular base has been covered by a sequence read" is a real observable entity. Whether to call it depth/coverage or something else (Picard HsMetrics uses the X coverage for a target base) is open for discussion.
                Last edited by GenoMax; 11-19-2013, 05:02 AM.

                Comment

                • dpryan
                  Devon Ryan
                  • Jul 2011
                  • 3478

                  #9
                  @GenoMax, nice examples! Of course, they all apply to DNA sequencing. I object to using "coverage" and "depth" here only because I don't think they're useful in the context of miRNA profiling (or RNAseq in general).

                  Comment

                  • CofactorGenomics_Natalie
                    Junior Member
                    • May 2013
                    • 1

                    #10
                    Haiwan-

                    Thanks for initiating a thoughtful discussion. At Cofactor Genomics, we generally avoid using the terminology "depth" and "coverage" for RNA-sequencing as well. Reporting the number of reads sequenced is an acceptable practice.

                    The other option you have is to perform a saturation analysis, where you evaluate the number of known miRNA that you've sequenced in your experiment. Reporting this add additional insight to your data. If you have questions regarding this type of analysis, please let me know and I'd be happy to discuss.
                    Natalie LaFranzo, Ph.D. | Project Scientist | Cofactor Genomics
                    4044 Clayton Ave | St. Louis, MO 63110 | tel. (314) 531-4647

                    Comment

                    • haiwan
                      Junior Member
                      • Nov 2013
                      • 6

                      #11
                      Thank you very much indeed.

                      i learned more from all of you. It is quite complex for sequencing data. I think it is very important from start to learn.
                      I am going to send samples for 16s sequencing. So, it would be quite different from miRNA sequencing? Another story again?

                      Comment

                      • dpryan
                        Devon Ryan
                        • Jul 2011
                        • 3478

                        #12
                        Well, for the whole "reporting depth/coverage" thing, I would say that's the same for 16s profiling. The amount of sequence you need will depend on the complexity of the underlying sample. Consider the saturation analysis suggested by Natalie@CofactorGenomics, that's an excellent way to go about this (and should shut-up any reviewer and put your mind at ease regarding having sufficient signal).

                        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...