Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • flobpf
    Member
    • Apr 2010
    • 76

    Trinity Chrysalis died with exit code 9

    Hi, I'm running Trinity v 4.4.5 to perform some de novo assemblies using PE data. I get an error at the ReadsToTranscripts step, as follows:
    COMMAND: <path>/trinity/20130225--GCC-4.4.5/Chrysalis/ReadsToTranscripts -i both.fa -f <path>/chrysalis/bundled.fasta -o <path>/chrysalis -strand -max_mem_reads 1000000
    Died with exit code 9
    Exiting.
    core file size (blocks, -c) 0
    data seg size (kbytes, -d) unlimited
    scheduling priority (-e) 0
    file size (blocks, -f) unlimited
    pending signals (-i) 191873
    max locked memory (kbytes, -l) unlimited
    max memory size (kbytes, -m) 8097152
    open files (-n) 16384
    pipe size (512 bytes, -p) 8
    POSIX message queues (bytes, -q) 819200
    real-time priority (-r) 0
    stack size (kbytes, -s) unlimited
    cpu time (seconds, -t) 7200
    max user processes (-u) 1024
    virtual memory (kbytes, -v) unlimited
    file locks (-x) unlimited
    followed by:
    Error, the Chrysalis process failed:
    Error, cmd: <path>/Chrysalis -i both.fa -iworm <path>/inchworm.K25.L25.fa -o <path>/chrysalis -cpu 10 -min_glue 2 -min_iso_ratio 0.05 -glue_factor 0.05 -weldmer_size 48 -min 200 -dist 500 -max_reads 200000 -sort_buffer_size 20G -max_mem_reads 1000000 -strand 1 -paired -reads_for_pairs both.fa -butterfly<path>/Butterfly/Butterfly.jar -no_cleanup 2>&1 died with ret 65280 at <path>/trinity/20130225--GCC-4.4.5/Trinity.pl line 1476.

    at <path>/trinity/20130225--GCC-4.4.5/Trinity.pl line 1101
    main::run_chrysalis('<path>...', 'both.fa', 200, 500, 'RF', 'both.fa') called at <path>/trinity/20130225--GCC-4.4.5/Trinity.pl line 930
    Does anyone know what exit code 9 means, and what I can do to fix the issue?

    Thanks!
  • flobpf
    Member
    • Apr 2010
    • 76

    #2
    Solution?

    It may be that this error is related to memory usage. Doubling the memory seems to have fixed the problem. Trinity ran all the way through to the end.

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