Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • scamiolo
    Junior Member
    • May 2018
    • 3

    Trinity segmentation fault

    Hi there,

    I would like to use the transcript assembler Trinity to assemble RNAseq data while using a reference genome as a guide. I aligned my reads on the reference genome with Tophat, sorted the obtained bam file and then used the following command:

    Code:
    ~/Software/Trinityrnaseq-v2.6.6/Trinity --genome_guided_bam accepted_hits_sorted.bam --genome_guided_max_intron 32000 --max_memory 10G --CPU 10 &
    The command returns a Segmentation fault error without any further details
    Can someone help me with this please?
    thanks!
  • GenoMax
    Senior Member
    • Feb 2008
    • 7142

    #2
    That 10G is a guide (I assume you took that from the example command line). What size is your BAM file? You may need to assign more RAM for this job.

    Comment

    • scamiolo
      Junior Member
      • May 2018
      • 3

      #3
      Originally posted by GenoMax View Post
      That 10G is a guide (I assume you took that from the example command line). What size is your BAM file? You may need to assign more RAM for this job.
      Hi there,

      thanks for your e-mail. I do not think it is a matter of amount of memory. The bam file is under 100 Mb, very small actually. Also Trinity version I am using is the latest. I really can not understand what is going on. Any ideas?
      thanks a lot

      Comment

      • GenoMax
        Senior Member
        • Feb 2008
        • 7142

        #4
        Have you run trinity with other data successfully? if not test it with something else. Did you compile the program yourself?

        Comment

        • scamiolo
          Junior Member
          • May 2018
          • 3

          #5
          Yes it returns a segmentation fault also with other paired end data. I compiled directly with the make command as stated in the manual. It fails also if I provide only arguments --left and --right.
          Actually I just checked the installation with make test_trinity and this failed with the following message

          Code:
          #######################################################
          ##  Run Trinity to Generate Transcriptome Assemblies ##
          #######################################################
          
          ../../Trinity --seqType fq --max_memory 2G \
                        --left reads.left.fq.gz \
                        --right reads.right.fq.gz \
                        --SS_lib_type RF \
                        --CPU 4 
          ./runMe.sh: line 11: 42124 Segmentation fault      ../../Trinity --seqType fq --max_memory 2G --left reads.left.fq.gz --right reads.right.fq.gz --SS_lib_type RF --CPU 4
          make[1]: *** [test] Error 139
          make[1]: Leaving directory 
          make: *** [test_trinity] Error 2

          thanks

          Comment

          • GenoMax
            Senior Member
            • Feb 2008
            • 7142

            #6
            Ok. So it is your compiler that may be the problem. What version of GCC did you use to compile this? You may need to use a newer version.

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