Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ercfrtz
    Member
    • Aug 2010
    • 23

    #1

    Tophat Error

    I have been using tophat and it has been running fine, but I recently started receiving the following error. I checked my install version and saw it was a version behind and installed the newest version and get the same error.

    File "/shared/local/tophat-1.4.1.Linux_x86_64/tophat", line 650
    except getopt.error, msg:
    ^
    SyntaxError: invalid syntax


    Does anyone know what would be causing this issue?
  • peromhc
    Senior Member
    • Sep 2009
    • 108

    #2
    Can you provide us with the command you supplied to tophat? the getopt.error suggests to me that something abut your command is wrong.

    Comment

    • ercfrtz
      Member
      • Aug 2010
      • 23

      #3
      Code:
      /shared/local/tophat-1.4.1.Linux_x86_64/tophat -r 100 -o /storage/isu/reecy_lab/tmp_eric/new.Lee.data/kph /storage/isu/reecy_lab/tmp_eric/index/b_taurus/umd3.1/mitoy/bos_taurus_all /storage/isu/reecy_lab/tmp_eric/new.Lee.data/kph/all.animals_1.fq /storage/isu/reecy_lab/tmp_eric/new.Lee.data/kph/all.animals_2.fq
      That is the command I used. I was using it just a few days ago and it worked fine.

      Edit:

      I also tried just calling tophat with no options or input to get the help to display and I get the same error.
      Last edited by ercfrtz; 02-08-2012, 12:22 PM.

      Comment

      • ercfrtz
        Member
        • Aug 2010
        • 23

        #4
        I discovered what the issue was. It appears that when we upgraded our python instance from 2.X to 3.X, tophat no longer worked. We re-installed python 2.X as /usr/local/bin/python2 and then I edited the tophat code itself on the line that has
        #!/usr/bin/env python

        to

        #!/usr/bin/env python2

        It appears to be working again after making these adjustments.

        Comment

        • blancha
          Senior Member
          • May 2013
          • 367

          #5
          I just had exactly the same problem.
          Luckily, I found this post immediately, and was able to fix the problem in just a few seconds.

          How is the bioinformatics community going to move on from Python 2 to Python 3 if these problems keep occurring?

          I have moved on. I now write all my pipelines in Python 3.
          I'd just switched my environment to Python 3 when this initially perplexing problem occurred.

          We should all agree to dump Python 2 and move on to Python 3.
          (Or just give up on Python 3 and stick to Python 2)
          Otherwise, these #!!?? bugs will keep on popping up.

          Comment

          • blancha
            Senior Member
            • May 2013
            • 367

            #6
            I don't know if Cole, Daehwan or Geo read this forum.
            If any of you do, you should just add a 2 to the shebang line for the tophat script as ercfrtz suggested.

            #!/usr/bin/env python2
            instead of
            #!/usr/bin/env python

            I think there is a larger problem between Python 2 and Python 3, but I'm sure this simple temporary fix will avoid many frustrations as more and more users switch their default environment from Python 2 to Python 3.

            Comment

            Latest Articles

            Collapse

            • SEQadmin2
              Multiomic Liquid Biopsy: What DNA/RNA Panels Reveal That DNA Alone Can’t
              by SEQadmin2



              Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?

              Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating
              ...
              10-14-2026, 09:55 AM
            • SEQadmin2
              New Genomics Technologies Take Aim at Long-Standing Limits
              by SEQadmin2


              Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.

              We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing
              ...
              09-28-2026, 10:25 AM

            ad_right_rmr

            Collapse

            News

            Collapse

            Topics Statistics Last Post
            Started by SEQadmin2, Yesterday, 11:13 AM
            0 responses
            16 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, Yesterday, 10:48 AM
            0 responses
            15 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 10-15-2026, 10:52 AM
            0 responses
            35 views
            0 reactions
            Last Post SEQadmin2  
            Started by SEQadmin2, 10-14-2026, 05:39 AM
            0 responses
            42 views
            0 reactions
            Last Post SEQadmin2  
            Working...