Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • zjrouc
    Member
    • Sep 2010
    • 25

    Htseq question

    Hi, all,

    i just got a result from ht-seq. It showed that my interesting gene has 7 counts in the alignment. However, from the view of IGV, i could easily identify much more counts than 7 on this gene. My alignment is from STAR, and i used more stringent parameters to control the multiple alignment, which means there should not be any multiple aligned reads in the output. I am really confused about this.

    Any suggestion?
    Attached Files
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    Just use the -o option to track how the reads are being categorized. Then you can simply look and see why they're not being counted.

    Comment

    • zjrouc
      Member
      • Sep 2010
      • 25

      #3
      Originally posted by dpryan View Post
      Just use the -o option to track how the reads are being categorized. Then you can simply look and see why they're not being counted.
      Dear dpryan,

      Thank you for your reply. I have checked the results, It showed htseq classified most of the reads of this region into "ambiguous" condition, and they belong to ENSG00000198211.8 + ENSG00000258947.3. However, i checked these two genes. Both of them are TUBB3 gene. One is Chromosome 16: 89,921,392-89,938,761 and the other is Chromosome 16: 89,919,165-89,936,092. I understand this problem is not caused by the Htseq software. However, if we discard these reads, it will have a huge impact on expression of this TUBB3 gene (Htseq count 7, but there are dozens).

      Do you have any ideas about this?


      Thanks

      Comment

      • dpryan
        Devon Ryan
        • Jul 2011
        • 3478

        #4
        This seems to be an interesting edge-case. So, TUBB3 and MC1R can form fusion transcripts and fusion proteins. So ENSG00000198211 isn't a mistake and htseq-count isn't doing anything incorrect. However, cases like this are really annoying for read counting. The simplest solution would be to just remove the entries for ENSG00000198211 in your GTF file. The actual correct solution would require a different annotation format that can account for non-novel fusion events of genes that are properly annotated and analyzed as separate in many cases. Such a format will probably get created someday, but I imagine it'll take a while.

        Comment

        • fanli
          Senior Member
          • Jul 2014
          • 197

          #5
          A (sort-of) workaround would be to count ambiguous reads for both genes:
          Discussion of next-gen sequencing related bioinformatics: resources, algorithms, open source efforts, etc

          Comment

          Latest Articles

          Collapse

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, 06-09-2026, 11:58 AM
          0 responses
          15 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-05-2026, 10:09 AM
          0 responses
          26 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-04-2026, 08:59 AM
          0 responses
          37 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-02-2026, 12:03 PM
          0 responses
          61 views
          0 reactions
          Last Post SEQadmin2  
          Working...