Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • polarise
    Member
    • Jan 2011
    • 13

    Pysam pileup working unpredictably

    Hi,

    I'm trying to count allelic frequencies at SNPs and Pysam seems to be the best solution to do that. However, when I make a call to get the number of reads that occur at a single site I get many more sites than expected.

    Example:
    len(list(f.pileup(reference='chr1',start=1756880,end=1756881)))

    gives a result of 135 as opposed to the expected value of 1

    and

    len(list(f.pileup(reference='chr1',start=1756870,end=1756881)))

    gives a result of 146 as opposed to 10.

    Can anyone please explain what is going on?

    Regards,

    P. Korir
  • ffinkernagel
    Senior Member
    • Oct 2009
    • 110

    #2
    I suspect that pileup givess you pileups for every base covered by a read that was within the query range.

    edit: You might want to print the pos of each PileupColumn. for p in f.pileup(...): print p.pos, p.n ...

    Comment

    • polarise
      Member
      • Jan 2011
      • 13

      #3
      Thanks for your reply ffinkernagel.

      Well, I'm surprised that when I give it a query range of 1 it gives more than one result. Anyway, I have used the for loop like in your suggestion though the solution is not as clean as I wanted it to be.

      f.pileup() returns an iterator. I'm not proficient in the use of iterators.

      P. Korir

      Comment

      • ffinkernagel
        Senior Member
        • Oct 2009
        • 110

        #4
        you simply do
        for something in my_iterator:
        do_something_with(something)

        no difference to a list there.

        The for loop should tell you if my hunch is correct.

        Comment

        • polarise
          Member
          • Jan 2011
          • 13

          #5
          OK. I'll give it a shot.

          Thank you.

          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, 07-02-2026, 11:08 AM
          0 responses
          11 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          14 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          20 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-17-2026, 06:09 AM
          0 responses
          54 views
          0 reactions
          Last Post SEQadmin2  
          Working...