Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • behoward
    Member
    • Mar 2009
    • 13

    cufflinks hangs

    Problem: cufflinks hangs/freezes during processing with the terminal showing the following messages:

    Inspecting reads and determining fragment length distribution.
    > Processing Locus chr12:69154464-69154707 [*** ] 13%

    The data is paired end RNA seq data from mouse. I used the mm10 index files available on the cufflinks website and the following tophat and cufflinks commands:

    > tophat
    -p 8
    -G genes.gtf
    -o tophat_output_directory
    /mm10/Sequence/BowtieIndex/genome
    /Working/WT_PE1.fastq
    /Working/WT_PE2.fastq

    >cufflinks
    -p 8
    -o cufflinks_output_directory
    tophat_output_directory/accepted_hits.bam

    I have read various related posts on this site including the following:
    http://seqanswers.com/forums/showthread.php?t=12458
    Application of sequencing to RNA analysis (RNA-Seq, whole transcriptome, SAGE, expression analysis, novel organism mining, splice variants)

    http://seqanswers.com/forums/showthread.php?t=7169

    Using the suggestions from these posts, I created a 'Masks.gtf' file which includes all the rRNA, tRNA and mitochondrial regions. I then added the following to the cufflinks parameters:
    -M Masks.gtf

    Unfortunately the problem remained. I double checked the format of the masks file, used verbose mode make sure there were no hidden error messages, etc.

    Next, I uploaded read coverage data to the UCSC browser and examined the read coverage near the offending region (chr12:69154464-69154707) and found that there two were large spikes in coverage in two subsequent regions on chr12, roughly at positions 69158856...69160012 and 69360961...69361955. So, I added the following three lines to the top of my Masks.gtf file, to see if I could force these regions to be excluded.

    chr12 BEH exon 69155265 69159154 . + . gene_id "beh0"; transcript_id "beh0_region";
    chr12 BEH exon 69158856 69160012 . + . gene_id "beh1"; transcript_id "beh1_region";
    chr12 BEH exon 69360961 69361955 . + . gene_id "beh2"; transcript_id "beh2_region";

    This did not have any noticeable effect; the program hangs in the exact same position, with the same messages.

    The last thing I tried, was to try to make the program skip all 'bundles' with large numbers of aligned reads, by using the "--max-bundle-frags" flag. I tried the following scenarios, all with no noticeable effect:
    --max-bundle-frags 10000
    --max-bundle-frags 1000
    --max-bundle-frags 100

    In fact, when I examined the output using the -v flag, cufflinks gave no indication that it was skipping bundles with out-of-range read counts. E.g. the output contained messages such as the following even when --max-bundle-frags was equal to 100:
    Inspecting bundle chr12:67510720-67511387 with 20394 reads

    All of the above were tried on two different versions of cufflinks (v2.0.2 and v1.3.0) on a 64 bit linux computer.

    Does anyone have any other advice for me? It seems like cufflinks simply won't work on my data set.
  • fburdet
    Junior Member
    • Oct 2013
    • 2

    #2
    Hello,

    I am having exactly the same problem, also stops at chr12.

    Did you find a solution eventually?

    Thanks in advance,

    Cheers,

    Fred

    Comment

    • smowton
      Junior Member
      • Sep 2014
      • 2

      #3
      Hi,

      Obviously this thread is quite old, but if experiencing a similar problem you might want to try the patch (and patched binaries) described here: https://groups.google.com/forum/#!to...rs/UzLCJhj3lUE

      Please let me know if this resolves the situation!

      Chris

      Comment

      • SrCardgage
        my other car is a limozeen
        • Feb 2012
        • 23

        #4
        Thank you, Chris, for this info. I'm not sure this is my problem, but it's nice to know there is a probable fix.

        Cheers

        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, Today, 11:05 AM
        0 responses
        7 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 07-02-2026, 11:08 AM
        0 responses
        28 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-30-2026, 05:37 AM
        0 responses
        25 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-26-2026, 11:10 AM
        0 responses
        25 views
        0 reactions
        Last Post SEQadmin2  
        Working...