Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Simonli
    Member
    • Oct 2013
    • 14

    #1

    When running Bowtie in Chrysalis, unable to decipher reads

    Hi Guys,
    I`m a RNAseq beginner, I`m using ConDeTri to trim and filter the reads, and inchworm is running good, generate a both.fa file, however when I running the step two of Trinity, it shows my reads could not be deciphered as being /1 or /2 of a PE fragment.
    I googled a few related topics but nobody give out a solid answer or solution, anybody has experienced this before?

    Thanks,
    Simon

    ---- Chrysalis ----
    -------------------

    mkdir: cannot create directory `/local_scratch/pbs.6227496.pbs01/trinityoutput/chrysalis': File exists
    ###########################################################
    ## Running Bowtie to map fragment ends to Inchworm Contigs
    ## to use pairing info for Chrysalis' clustering
    ###############################################################

    CMD: ln -sf /local_scratch/pbs.6227496.pbs01/trinityoutput/inchworm.K25.L25.DS.fa target.fa
    CMD: bowtie-build -q target.fa target
    CMD: bowtie -a -m 20 --best --strata --threads 16 --quiet --chunkmbs 512 -q -S --sam-nohead -f target both.fa > bowtie.out
    CMD: /local_scratch/pbs.6227496.pbs01/trinityrnaseq_r2013_08_14/Chrysalis//../trinity-plugins/coreutils/bin/sort --parallel=16 -T . -$
    CMD: rm bowtie.out
    CMD: /local_scratch/pbs.6227496.pbs01/trinityrnaseq_r2013_08_14/Chrysalis//../util/scaffold_iworm_contigs.pl bowtie.nameSorted.sam /l$
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:100038 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:100038 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:100652 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:100652 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:11363 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:11363 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:11363 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:15314 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:15314 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:21043 since cannot decipher if /1 or /2 of a pair.
    warning, ignoring read: HISEQ:190:C2L5LACXX:6:1101:10000:21043 since cannot decipher if /1 or /2 of a pair.
    number of read warnings exceeded 10. Turning off warning messages from here out.
    ERROR: note there were 326239257 reads that could not be deciphered as being /1 or /2 of a PE fragment. Hopefully, these were SE reads that should have been ignored. Otherwise, please research this further.

  • atcghelix
    Member
    • Jul 2013
    • 74

    #2
    What do the first few reads in the both.fa file look like?

    Comment

    • Simonli
      Member
      • Oct 2013
      • 14

      #3
      I see the problems now, check below, I don`t have the "/1" or "/2" in my both.fa file. How is that happening? Should I check the first step of the inchworm?

      >HISEQ:190:C2L5LACXX:7:1101:2055:1989 1:N:0:ATCATG
      AACAATTTCATCCTCGAATCCTACCACACGGGCGCTGGCACCGCCTACGCCGTCCTCGCTGAGAACACCACCGAAGCCAACCCTCGCACCTTCTACGTGA
      >HISEQ:190:C2L5LACXX:7:1101:3448:1999 1:N:0:ATCACG
      GTCGTATGCAAAGGATTCAACCCCACGCATTGTAAAATTGCAAGACGCCAGTTAGTCCTAAAGAGTTTCTTCAATAGGACCGTTACCAGCCAGCTAAGAT
      >HISEQ:190:C2L5LACXX:7:1101:3524:1986 1:N:0:ATCACG
      CTTGTCCTTCTTCTCTTTCCTCTCTTTGGTTTTATCTGACACAAGATCCTTCTCAATCTTATCGAGACTCGGCCTCTGCTTGAGTTTCTCAGAGTCATTA
      >HISEQ:190:C2L5LACXX:7:1101:4204:1996 1:N:0:ATCACG
      GTGTTAAAAGGGCTAGAGATCGAAATGTTAGACAAAGCGAAATGGAGCAAAGACTGGCAGATCCCAACCAATCCCAATCACGCCGAGAACAAACTTGGTC
      >HISEQ:190:C2L5LACXX:7:1101:4587:2000 1:N:0:ATCACG

      Comment

      • Simonli
        Member
        • Oct 2013
        • 14

        #4
        Check the reply above..

        Comment

        • atcghelix
          Member
          • Jul 2013
          • 74

          #5
          Sounds like Trinity is not properly recognizing the sequence names so that it can add the /1 and /2. Did you modify the read names after receiving the fastq files?

          Of potential interest: http://sourceforge.net/mailarchive/f...tyrnaseq-users

          You could manually rename the reads in the initial fastq files so that they say /1 and /2.
          Last edited by atcghelix; 10-22-2013, 05:31 PM.

          Comment

          • Simonli
            Member
            • Oct 2013
            • 14

            #6
            Originally posted by atcghelix View Post
            Sounds like Trinity is not properly recognizing the sequence names so that it can add the /1 and /2. Did you modify the read names after receiving the fastq files?

            Of potential interest: http://sourceforge.net/mailarchive/f...tyrnaseq-users

            You could manually rename the reads in the initial fastq files so that they say /1 and /2.
            Thanks atcghelix,

            When you say manually rename the reads, do you konw what kind of codes can do that?
            I`m new to bioinformatics as well as linux.
            Thanks.

            Comment

            • Simonli
              Member
              • Oct 2013
              • 14

              #7
              Manually put /1 or /2 in the headers, not work

              I have manually put /1 or /2 in the headers, still doesn`t work.....

              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, Today, 10:05 AM
              0 responses
              8 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 08-13-2026, 12:22 PM
              0 responses
              32 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 08-11-2026, 10:35 AM
              0 responses
              24 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 08-06-2026, 07:41 AM
              0 responses
              38 views
              0 reactions
              Last Post SEQadmin2  
              Working...