Seqanswers Leaderboard Ad

Collapse

Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • cedance
    replied
    rebrendi, About the tophat 1.2.0 and 1.3.3 version difference, are you working on a cluster? if so, the default "tophat" path (installed by your admin) maybe linked to version 1.2.0. This is a very silly thing, but happens more than one might think, as its often overlooked. If so, you'll have to add your tophat path before the default $PATH in your .bash_profile file.

    Leave a comment:


  • rebrendi
    replied
    just on case if someone else is getting this error,
    I found a similar thread. It seems that this issue
    has not been resolved yet, or the issue was different
    for different people.
    Discussion of next-gen sequencing related bioinformatics: resources, algorithms, open source efforts, etc

    In my case the disc space is not the problem for sure.

    Leave a comment:


  • rebrendi
    replied
    yeah, I have more than 4 GB memory.

    Leave a comment:


  • biznatch
    replied
    Ah ok the 1.2.0 must mean Bowtie then. I don't think it's a memory issue, I ran out of memory on a Tophat run and got a -6 error during "Searching for junctions via segment mapping", I think error 1 must be something else, but not sure. How much memory do you have and what species are you aligning to? You should be able to align to the mouse or human genome with under 4GB.

    Leave a comment:


  • rebrendi
    replied
    I am using the latest version of TopHat, 1.3.3.
    I just downloaded and installed it yesterday.
    I do not know why it lists version 1.2.0.
    My bowtie version is very outdated but it seems
    that this is not the problem with Bowtie,
    because bowtie has mapped the reads.
    Can it be because of the memory problem or something like this?

    Leave a comment:


  • biznatch
    replied
    Yes those are temp files created by Tophat that are usually automatically deleted after Tophat runs successfully. I'm not sure exactly what's causing your problem, there's just the error "Error: could not get read # 34344441 from stream". Are you using an old version of Tophat? It looks like you're using v1.2.0, maybe try the newest version 1.3.3. I don't know if that will solve the problem but it's the first thing I would try.

    Leave a comment:


  • rebrendi
    replied
    ...and it has also created a directory /tmp, with several large files, some of them seem to look similar to BED format, but none of them has a formal extension, so it seems that the program did not finish working, and these are really temporal files.

    Any suggestions?

    Leave a comment:


  • rebrendi
    replied
    Here is what was in the logs:
    # reads processed: 29130490
    # reads with at least one reported alignment: 23830715 (81.81%)
    # reads that failed to align: 4412560 (15.15%)
    # reads with alignments suppressed due to -m: 887215 (3.05%)
    Reported 89574818 alignments to 1 output stream(s)
    long_spanning_reads v1.2.0 (1752)
    --------------------------------------------
    Opening /dev/null for reading
    Opening /dev/null for reading
    Opening /dev/null for reading
    Opening ./tophat_out/tmp/left_kept_reads.bwtout for reading
    Loading reference sequences...
    Loading spliced hits...done
    Loading junctions...done
    Loading deletions...done
    Error: could not get read # 34344441 from stream
    prep_reads v1.2.0 (1752)
    ---------------------------
    13364 out of 29143854 reads have been filtered out
    /usr/local/bin/tophat -r 100 /bowtie-0.12.5/indexes/xxxx data/sequence.txt /usr/local/bin/prep_reads --min-anchor 8 --splice-mismatches 0 --min-report-intron 50 --max-report-intron 500000 --min-isoform-fraction 0.15 --output-dir ./tophat_out/ --max-multihits 40 --segment-length 25 --segment-mismatches 2 --min-closure-exon 100 --min-closure-intron 50 --max-closure-intron 5000 --min-coverage-intron 50 --max-coverage-intron 20000 --min-segment-intron 50 --max-segment-intron 500000 --sam-header ./tophat_out/tmp/stub_header.sam --max-insertion-length 3 --max-deletion-length 3 --inner-dist-mean 100 --inner-dist-std-dev 20 --no-microexon-search --fastq /sequence.txt
    bowtie -q --un ./tophat_out/tmp/left_kept_reads_missing.fq --max /dev/null -v 2 -p 1 -k 40 -m 40 bowtie-0.12.5/indexes/xxxx ./tophat_out/tmp/left_kept_reads.fq | /usr/local/bin/fix_map_ordering --fastq ./tophat_out/tmp/left_kept_reads.fq - > .//usr/local/bin/long_spanni/usr/local/bin/long_spanning_reads --min-anchor 8 --splice-mismatches 0 --min-report-intron 50 --max-report-intron 500000 --min-isoform-fraction 0.15 --output-dir ./tophat_out/ --max-multihits 40 --segment-length 25 --segment-mismatches 2 --min-closure-exon 100 --min-closure-intron 50 --max-closure-intron 5000 --min-coverage-intron 50 --max-coverage-intron 20000 --min-segment-intron 50 --max-segment-intron 500000 --sam-header ./tophat_out/tmp/stub_header.sam --max-insertion-length 3 --max-deletion-length 3 --inner-dist-mean 100 --inner-dist-std-dev 20 --no-microexon-search ./tophat_out/tmp/xxxx.fa ./tophat_out/tmp/left_kept_reads.fq /dev/null /dev/null /dev/null ./tophat_out/tmp/left_kept_reads.bwtout > ./tophat_out/tmp/file2SmeWx

    Leave a comment:


  • biznatch
    replied
    Look in the log files there may be more detailed errors.

    Leave a comment:


  • rebrendi
    replied
    still relevant...

    Leave a comment:


  • rebrendi
    started a topic TopHat ERROR: Segment join failed with err = 1

    TopHat ERROR: Segment join failed with err = 1

    Hello all,

    I am running TopHat for the first time, but but it gives error. Could you please have a look at the output?

    Preparing output location ./tophat_out/
    Checking for Bowtie index files
    Checking for reference FASTA file
    Warning: Could not find FASTA file /bowtie-0.12.5/indexes/xxxxa.fa
    Reconstituting reference FASTA file from Bowtie index
    Checking for Bowtie
    Bowtie version: 0.12.x.0
    Checking for Samtools
    Samtools Version: 0.1.16
    Checking reads
    min read length: 36bp, max read length: 36bp
    format: fastq
    quality scale: phred33 (default)
    Mapping reads against xxxx with Bowtie
    Joining segment hits
    [FAILED]
    Error: Segment join failed with err = 1

Latest Articles

Collapse

  • seqadmin
    Genetic Variation in Immunogenetics and Antibody Diversity
    by seqadmin



    The field of immunogenetics explores how genetic variations influence immune responses and susceptibility to disease. In a recent SEQanswers webinar, Oscar Rodriguez, Ph.D., Postdoctoral Researcher at the University of Louisville, and Ruben Martínez Barricarte, Ph.D., Assistant Professor of Medicine at Vanderbilt University, shared recent advancements in immunogenetics. This article discusses their research on genetic variation in antibody loci, antibody production processes,...
    11-06-2024, 07:24 PM
  • seqadmin
    Choosing Between NGS and qPCR
    by seqadmin



    Next-generation sequencing (NGS) and quantitative polymerase chain reaction (qPCR) are essential techniques for investigating the genome, transcriptome, and epigenome. In many cases, choosing the appropriate technique is straightforward, but in others, it can be more challenging to determine the most effective option. A simple distinction is that smaller, more focused projects are typically better suited for qPCR, while larger, more complex datasets benefit from NGS. However,...
    10-18-2024, 07:11 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by seqadmin, 11-08-2024, 11:09 AM
0 responses
57 views
0 likes
Last Post seqadmin  
Started by seqadmin, 11-08-2024, 06:13 AM
0 responses
37 views
0 likes
Last Post seqadmin  
Started by seqadmin, 11-01-2024, 06:09 AM
0 responses
34 views
0 likes
Last Post seqadmin  
Started by seqadmin, 10-30-2024, 05:31 AM
0 responses
23 views
0 likes
Last Post seqadmin  
Working...
X