Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • bbm
    Member
    • Sep 2011
    • 38

    tophat job killed by run time limit

    I got my tophat running, and then it was killed after a few minutes.


    My output file said the job was killed after reaching LSF run time limit.
    Exited with exit code 140.


    This is the error file:
    [2014-09-12 16:32:42] Beginning TopHat run (v2.0.12)
    -----------------------------------------------
    [2014-09-12 16:32:42] Checking for Bowtie
    Bowtie version: 2.2.1.0
    [2014-09-12 16:32:42] Checking for Samtools
    Samtools version: 0.1.19.0
    [2014-09-12 16:32:42] Checking for Bowtie index files (genome)..
    [2014-09-12 16:32:42] Checking for reference FASTA file
    [2014-09-12 16:32:42] Generating SAM header for /gpfs_share/hlibyar/tophat/Am_genome
    [2014-09-12 16:33:03] Preparing reads
    left reads: min. length=12, max. length=100, 35244255 kept reads (1989 discarded)
    Warning: short reads (<20bp) will make TopHat quite slow and take large amount of memory because they are likely to be mapped in too many places
    [2014-09-12 16:49:20] Mapping left_kept_reads to genome Am_genome with Bowtie2
    User defined signal 2


    --

    I appreciate any insights you can give!

    Regards,
    bbm
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    You need to request more time from the scheduler. Tophat takes hours to run, so try requesting a day to be safe.

    Comment

    • Brian Bushnell
      Super Moderator
      • Jan 2014
      • 2709

      #3
      You could also switch to something faster, such as BBMap or Star. A few minutes would probably still be way too short, depending on the input size.

      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
      24 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-30-2026, 05:37 AM
      0 responses
      23 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-26-2026, 11:10 AM
      0 responses
      23 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-17-2026, 06:09 AM
      0 responses
      55 views
      0 reactions
      Last Post SEQadmin2  
      Working...