Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Daniel
    Junior Member
    • Jul 2010
    • 7

    #1

    Cufflinks error - nonsense gene merge

    Hello All,
    I am new to bioinformatics and am (trying to) use Cufflinks for the first time. My input to Cufflinks is an accepted_hits.sam file with ~19 million reads - generated (apparently without error) from Tophat. When I run cufflinks (cufflinks -o Results accepted_hits.sam) I first get a "Counting hits in map" message, and then "Error:nonsense gene merge. Exiting". By an iteriative process of truncating my input file, I find that Cufflinks apparently does not like a line (~ 4 millionth) in the input file.

    My accepted_hits.sam file at the error point looks like this (below). Shown are 9 reads - Cufflinks seems to generate the error message with 6th read shown. I have tried just eliminating this one line from the accepted_hits.sam file - I still get the same error (perhaps from some later line.) I have also tried Cufflinks with output from different files coming from Tophat - I consistently get this same error. (Cufflinks does run fine with the test file supplied...)

    Thanks for any help with this

    HWI-EAS288_8_2_20_941_1818_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111450969 255 64M * 0 0 ATAGCATCTTCCC
    AGCTTCCATCTCCCTACAGTCCATCNTATTCAAGTCTTTAGCTATTTTGGA B@BBBB@BBBBABABA@@@A@@AA@??B;=7:=@?>A;%;>AB@?6?:?==?=@?@>?=@?>>8 NM:i:2
    HWI-EAS288_8_2_117_405_131_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111450982 255 42M * 0 0 AGCTTCCATCTCC
    CTACAGTCCATCATATTCAAGTCTTTAGC <:A>9=,/8;297=;=;1208778=:2-2650'462-3586? NM:i:0
    HWI-EAS288_8_1_9_672_1871_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111530035 255 62M * 0 0 GGGAAACATGGTG
    AAACCCTGTTTCTACTAAAAATACAAAAATTAGCCAGCTGTGGTGGCAA 6CCBBCCCCCB>BBBCCBAC@BCCCBBBCB@A>BCBBB@BACBAB<ABBB>B<>@??;%8@; NM:i:1
    HWI-EAS288_8_2_79_444_2024_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111637724 1 22M17834N536870911M * 0 0 GCAGCAACAGCGGCAGCGGCA ABAAAB@@@>AAABAB?ABAA NM:i:2 XS:A:+ NS:i:2
    HWI-EAS288_8_2_79_444_2024_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111637724 1 22M17840N536870911M * 0 0 GCAGCAACAGCGGCAGCGGCA ABAAAB@@@>AAABAB?ABAA NM:i:2 XS:A:+ NS:i:2
    HWI-EAS288_8_2_79_444_2024_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111637724 1 22M5744N536870911M * 0 0 GCAGCAACAGCGGCAGCGGCA ABAAAB@@@>AAABAB?ABAA NM:i:2 XS:A:+ NS:i:2
    HWI-EAS288_8_2_56_390_1555_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111643298 255 42M * 0 0 CAGCAAACCACCA
    TGGCCCACATTTACCTATGTAACAAATCA BCBCCCCCCCBBCA;>C73-?CCBC@CBBBBCACBCCACBCC NM:i:1
    HWI-EAS288_8_2_50_1601_1261_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111809773 255 53M * 0 0 CTATTCTATACCA
    TTCCATTCCATTCCATTCCATTCCATTCCATGCCATTCCA BCBBCCBAC:CCCCBBACCBCBBBBBB@BBBBBB?BAAB@BA6>ABBAAABB1 NM:i:2
    HWI-EAS288_8_1_100_1688_1517_0 16 gi|51511724|ref|NC_000008.9|NC_000008 111829914 255 76M * 0 0 AGCCTTCAGTCTG
    TGGCCAAAGGCCCAAGGGTCCCCAGCGAACCACTGGTGTAAGTCCAAGAGTCCGAAGGCTGAG =+,:9===?9;AAA>?B=??A=>9>?A>A?A@BAAABBAAA?ABABBBAABABBBABBBBBBBBBABBBBBBBBBB NM:i:
    0
  • Xi Wang
    Senior Member
    • Oct 2009
    • 317

    #2
    I think the CIGAR field in the 3 lines below caused the problem.

    HWI-EAS288_8_2_79_444_2024_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111637724 1 22M17834N536870911M * 0 0 GCAGCAACAGCGGCAGCGGCA ABAAAB@@@>AAABAB?ABAA NM:i:2 XS:A:+ NS:i:2
    HWI-EAS288_8_2_79_444_2024_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111637724 1 22M17840N536870911M * 0 0 GCAGCAACAGCGGCAGCGGCA ABAAAB@@@>AAABAB?ABAA NM:i:2 XS:A:+ NS:i:2
    HWI-EAS288_8_2_79_444_2024_0 0 gi|51511724|ref|NC_000008.9|NC_000008 111637724 1 22M5744N536870911M * 0 0 GCAGCAACAGCGGCAGCGGCA ABAAAB@@@>AAABAB?ABAA NM:i:2 XS:A:+ NS:i:2
    Xi Wang

    Comment

    • celeste8
      Junior Member
      • Aug 2010
      • 2

      #3
      #!/usr/bin/perl

      use warnings;
      use strict;
      while (<>) {
      chomp;
      my @parts = split /\t/;
      if ( ( $parts[5]=~/(\d+)M\d+N(\d+)M/)&&($1>100)&&($2>100)) {
      next;
      }
      else {
      print "$_\n";
      }
      }

      I have ever faced this problem. You can use this perl code to process your reads.

      Comment

      Latest Articles

      Collapse

      • SEQadmin2
        Beyond CRISPR/Cas9: Understand, Choose, and Use the Right Genome Editing Tool
        by SEQadmin2



        CRISPR/Cas9 sparked the gene editing revolution for both research and therapeutics.1 But this system still showed severe issues that limited its applications. The most prominent were the heavy reliance on PAM sequences, delivery limitations, double-stranded breaks that prompt unintended edits and cell death, and editing inefficiency (both in targeting and in knock-in reliability).

        Despite this, “CRISPR helped turn genome editing from a specialized technique into
        ...
        07-31-2026, 11:01 AM
      • SEQadmin2
        Proteomic Platforms: How to Choose the Right Analytical Strategy to Improve Detection and Clinical Applications
        by SEQadmin2


        Proteomics platforms are evolving rapidly, with advances in mass spectrometry and affinity-based approaches expanding what researchers can detect and at what scale. As the field moves toward deeper proteome coverage and clinical applications, scientists face an increasingly complex landscape of tools. This article will explore how researchers are navigating these choices to find the right platform for their work.

        The systematic characterization of the human proteome has
        ...
        07-20-2026, 11:48 AM

      ad_right_rmr

      Collapse

      News

      Collapse

      Topics Statistics Last Post
      Started by SEQadmin2, 08-06-2026, 07:41 AM
      0 responses
      17 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 08-03-2026, 10:13 AM
      0 responses
      33 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 07-31-2026, 02:55 AM
      0 responses
      43 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 07-24-2026, 12:17 PM
      0 responses
      26 views
      0 reactions
      Last Post SEQadmin2  
      Working...