Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • shilez
    Member
    • Jun 2010
    • 10

    DEXSeq python script error message

    When I try to run dexseq_prepare_annotation.py, I got a python error at line 29:
    exons[f.iv] += ( f.attr['gene_id'], f.attr['transcript_id'] )
    TypeError: unsupported operand type(s) for +=: 'StepVector' and 'tuple'
    Anyone has any idea how to fix it?
  • Jane M
    Senior Member
    • Aug 2011
    • 239

    #2
    I have no idea, but I managed to run this script, so there is no error in it. Nevertheless, if I remeber well, a certain version of python is needed...

    Comment

    • Simon Anders
      Senior Member
      • Feb 2010
      • 995

      #3
      Could it be that you have an outdated version of HTSeq installed?

      Comment

      • shilez
        Member
        • Jun 2010
        • 10

        #4
        Thank you, guys.
        Once I update the HTSeq, it works fine.
        However, I do got the error message "Same name found on two chromosomes".
        Does it mean we need to remove the duplicated genes from the annotation gtf file first before running dexseq_prepare_annotation.py?

        *and also an error from HTSeq
        ValueError: start is larger than end
        Last edited by shilez; 09-08-2011, 10:57 AM.

        Comment

        • areyes
          Senior Member
          • Aug 2010
          • 165

          #5
          The first error can be solved by adding an additional ID tag to these genes. (e.g. if the gene is called A, you could write A_dup1 and A_dup2 foreach one so that the gene names become unique). They are usually not to many in the annotation files. (I have done it manually for the ensembl mouse gtf annotation).

          The second I have also seen it, for some genes, the start value is higher to the end value. I guess this is a mistake in the gtf files. Can be corrected just by shifting the columns in this cases. Also, there are usually not to many.

          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
          7 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          12 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...