Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Sataree
    Junior Member
    • Apr 2014
    • 2

    cufflinks/cuffdiff-segmentation error: 11

    Hi, I need your help.

    I'm very new to this pipeline. I have just finished mapped my reads using tophat2 without any problems according to Alternate protocols for "Quantification of reference annotation only" from Nature Protocols paper (2012). I'm now trying to perform differential expression analysis and I keep getting the "segmentation error:11" almost immediately. I see other threads but they seem to have a different problem from me.

    For example:
    $ cufflinks -o test_clout 2064NIC51_thout/accepted_hits.bam
    You are using Cufflinks v2.2.0, which is the most recent release.
    [23:17:27] Inspecting reads and determining fragment length distribution.
    Segmentation fault: 11

    I am getting this message for both cufflinks and cuffdiff. I don't know what I'm doing incorrectly. I have run the test data and it seems fine.

    $ cufflinks test_data.sam.txt
    You are using Cufflinks v2.2.0, which is the most recent release.
    [bam_header_read] EOF marker is absent. The input is probably truncated.
    [bam_header_read] invalid BAM binary header (this is not a BAM file).
    File test_data.sam.txt doesn't appear to be a valid BAM file, trying SAM...
    [23:18:37] Inspecting reads and determining fragment length distribution.
    Processed 1 loci. [*************************] 100%
    Warning: Using default Gaussian distribution due to insufficient paired-end reads in open ranges. It is recommended that correct parameters (--frag-len-mean and --frag-len-std-dev) be provided.
    Map Properties:
    Normalized Map Mass: 102.50
    Raw Map Mass: 102.50
    Fragment Length Distribution: Truncated Gaussian (default)
    Default Mean: 200
    Default Std Dev: 80
    [23:18:37] Assembling transcripts and estimating abundances.
    Processed 1 loci. [*************************] 100%

    I currently running the analysis on Mac OS X with 8 GB of RAM.

    I will really appreciate any help I can get.
  • therr
    Junior Member
    • Apr 2014
    • 2

    #2
    I'm getting the same problem -- I'm also following the Nature Protocols paper and running OSX with 8 GB RAM.

    I'm getting this error on a .BAM file that I obtained from ArrayExpress. If I run through the protocol using the demo data the paper references, it works properly with the .BAM that TopHat outputs. So, I suspect there's something wrong with the file.

    Were you able to figure it out?

    Comment

    • Sataree
      Junior Member
      • Apr 2014
      • 2

      #3
      I downloaded Cufflinks 2.1.1 and that version ran fine for me. I used Tophat2. I don't have experience with ArrayExpress, sorry.

      Comment

      • therr
        Junior Member
        • Apr 2014
        • 2

        #4
        Originally posted by Sataree View Post
        I downloaded Cufflinks 2.1.1 and that version ran fine for me. I used Tophat2. I don't have experience with ArrayExpress, sorry.
        Thanks! I just tried 2.1.1, and it's working for me, too. I guess there's a bug in 2.2.0?

        Oh, and ArrayExpress is a repository that has array and sequence data from published papers, so I was trying to analyze pre-prepared data. That's why it was strange to me that it didn't work!

        Comment

        Latest Articles

        Collapse

        • 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
        • SEQadmin2
          From Collection to Sequencing: Why Sample Preparation and Preservation Define Sequencing Data
          by SEQadmin2


          Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.


          The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
          ...
          06-02-2026, 10:05 AM

        ad_right_rmr

        Collapse

        News

        Collapse

        Topics Statistics Last Post
        Started by SEQadmin2, 06-17-2026, 06:09 AM
        0 responses
        30 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-09-2026, 11:58 AM
        0 responses
        96 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-05-2026, 10:09 AM
        0 responses
        115 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-04-2026, 08:59 AM
        0 responses
        108 views
        0 reactions
        Last Post SEQadmin2  
        Working...