Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • kerhard
    replied
    limit to bowtie-build fasta input files?

    Hi all,

    I've been trying to make a bowtie index using a long list of annotated transposons as the input fasta files rather than reference chromosome files and bowtie-build does not seem to like it very much.

    If I try to use ALL of the fasta files (which is a lot, probably around ~1000), I get the error message:

    Error: could not open <fileX.fa>

    But if I use only a subset of the fasta files (including fileX.fa), it works just fine.

    I'm assuming that it's a memory issue, but the total contents of all of these fasta files is much less than the fasta files containing the full reference genome sequences, and I can make an index with them just fine.

    Has anyone had any experience doing something similar? Is there some limit to the number of input files bowtie-build can take? I imagine that I can just split these files up into smaller groups and make several index files, but it would be nice to be able to have all of them in one index.

    Thanks for any help/advice!

    Leave a comment:


  • gntc
    replied
    mismatches

    Originally posted by droog_22 View Post
    Dear All,
    I am using bowtie to align reads to the dm3 genome. I just read that the SAM specifications allow for tags such as H0, H1, etc. which counts the number of 0-differences, 1-difference hits, and so on. I know how to do ass these tags using awk, I was just wondering if it would be straightforward to modify bowtie so that it outputs these values.
    Bowtie does this automatically. The tag is XA:i:0 (for a read with 0 mismatches).

    Leave a comment:


  • droog_22
    replied
    Counting Hits in a BAM file

    Dear All,

    I am using bowtie to align reads to the dm3 genome. I just read that the SAM specifications allow for tags such as H0, H1, etc. which counts the number of 0-differences, 1-difference hits, and so on. I know how to do ass these tags using awk, I was just wondering if it would be straightforward to modify bowtie so that it outputs these values.

    Cheers D.

    Leave a comment:


  • biznatch
    replied
    Originally posted by gntc View Post
    The files in chromFa.tar.gz each start out with a large number of 'N's. Is this due to uncertainty near the ends of chromosomes in sequencing?
    I think yes, it is because of uncertainty near the ends of the chromosomes. If you look at hg19 in the UCSC Genome Browser and turn on the Gap track you can see where there are gaps in sequencing on each chromosome. Anywhere there is a gap will be N's in the sequence. There are gaps at the ends of each chromosome because telomeres and subtelomeres are repetitive and difficult to sequence and assemble. There are also large gaps at the centromeres for the same reason.

    Leave a comment:


  • ewels
    replied
    Originally posted by gntc View Post
    The files in chromFa.tar.gz each start out with a large number of 'N's. Is this due to uncertainty near the ends of chromosomes in sequencing?
    What good timing - I was just searching out the answer to this exact question for that exact file... Does anyone know the answer?

    Leave a comment:


  • gntc
    replied
    repeats

    Originally posted by biznatch View Post
    Depends whether the index was made from the masked version of hg19 or not. I'm pretty sure the pre-made index from the Bowtie website is made from the non-masked genome. Both masked and non-masked are available here:



    "chromFa.tar.gz - The assembly sequence in one file per chromosome.
    Repeats from RepeatMasker and Tandem Repeats Finder (with period
    of 12 or less) are shown in lower case; non-repeating sequence is
    shown in upper case.

    chromFaMasked.tar.gz - The assembly sequence in one file per chromosome.
    Repeats are masked by capital Ns; non-repeating sequence is shown in
    upper case."
    The files in chromFa.tar.gz each start out with a large number of 'N's. Is this due to uncertainty near the ends of chromosomes in sequencing?

    Leave a comment:


  • biznatch
    replied
    Originally posted by gntc View Post
    Does the hg19 index mask repeats in the genome?

    I have illumina data that has a large number of repeats. The sequences have been mapped using ELAND and found that ~30% had >10 matches. When using bowtie about 10% have >10 matches. What accounts for this difference? Does the hg19 index mask repeats?

    Depends whether the index was made from the masked version of hg19 or not. I'm pretty sure the pre-made index from the Bowtie website is made from the non-masked genome. Both masked and non-masked are available here:



    "chromFa.tar.gz - The assembly sequence in one file per chromosome.
    Repeats from RepeatMasker and Tandem Repeats Finder (with period
    of 12 or less) are shown in lower case; non-repeating sequence is
    shown in upper case.

    chromFaMasked.tar.gz - The assembly sequence in one file per chromosome.
    Repeats are masked by capital Ns; non-repeating sequence is shown in
    upper case."

    Leave a comment:


  • gntc
    replied
    Repeats

    Does the hg19 index mask repeats in the genome?

    I have illumina data that has a large number of repeats. The sequences have been mapped using ELAND and found that ~30% had >10 matches. When using bowtie about 10% have >10 matches. What accounts for this difference? Does the hg19 index mask repeats?

    Leave a comment:


  • nashp
    replied
    question about bowtie's handling of long reads

    Hey guys,
    I have a question about bowtie's performance when we increase the length of the reads. Initially i used to run bowtie for reads length = 35. Now I am running the exps with reads length 51.

    When I read bowtie's manual, I noticed they say bowtie's performance decreases as the read length increases. On the contrary, i am seeing its performance become better when I shifted from 35 to 51. Could you guys please tell me why? is it normal for bowtie to behave this way??

    how short is short reads and how long is long reads (in terms of base pairs) ?

    Leave a comment:


  • Xi Wang
    replied
    Nowadays, spliced read mappers first split reads into segments, then apply mappers such as Bowtie to map those segments onto the reference genome. The segments belong to a read can be mapped with a long distance between, so that the splice junctions can be detected.
    What Nishomer mentioned is an old version of Tophat, when the read length is short.

    Leave a comment:


  • nilshomer
    replied
    Originally posted by tonge View Post
    Hi XiWang,
    Could you please tell me why is bowtie not suitable for RNA seq? Especially since Bowtie is utilised by tophat software.
    Thanks, Pete
    It is not able to handle spliced reads, as biznatch mentioned.

    Originally posted by biznatch View Post
    I think it's because Bowtie doesn't recognize splice junctions. Ie. when you sequence your RNA is often aligns across introns so there is a large gap in the alignment. Tophat uses the Bowtie alignment algorithm but can align across splice junctions. ...or something like that.
    Just to be clear, Tophat doesn't align anything by itself. Tophat creates a junction reference, where possible splice junctions are represented as contiguous sequences in the FASTA reference, allowing bowtie to map properly to these putative junctions. Take a look at the Tophat paper for more information.

    Leave a comment:


  • biznatch
    replied
    Originally posted by tonge View Post
    Hi XiWang,
    Could you please tell me why is bowtie not suitable for RNA seq? Especially since Bowtie is utilised by tophat software.
    Thanks, Pete
    I think it's because Bowtie doesn't recognize splice junctions. Ie. when you sequence your RNA is often aligns across introns so there is a large gap in the alignment. Tophat uses the Bowtie alignment algorithm but can align across splice junctions. ...or something like that.

    Leave a comment:


  • tonge
    replied
    Originally posted by Xi Wang View Post
    Generally, there is not a tool simply better than the others. It depends on what your scientific questions are, what kind of data you have, what the purpose is to analyze the data. For example, Bowtie is not suitable to deal with RNA-seq data.
    Hi XiWang,
    Could you please tell me why is bowtie not suitable for RNA seq? Especially since Bowtie is utilised by tophat software.
    Thanks, Pete

    Leave a comment:


  • gntc
    replied
    hg19 and allocation issues

    I am new to bowtie and I am having a couple problems. First, I downloaded the hg19 ebwt files and attempted to transfer them to the server where I will be running bowtie but received errors for 5 of the 6 files. Despite the errors the file names still appeared on the server and to check if they were functional I tried a trial run:

    ./bowtie -c -t hg19 CTGAGCTTGACGCTTTGCTAATATNGTAAGAAGAGAAACTATTAATTATGGCTTTCTAAAATTGAATATCCTTGTACACA

    this was the response:

    Out of memory allocating plen[] in Ebwt::read() at ebwt.h:3153
    Overall time: 00:00:00

    What can I do?

    Thanks, Greg

    Leave a comment:


  • david2
    replied
    Hi jyoshna,
    What kind of application do you have in mind? All machines and software packages have advantages and disadvantages depending on what you want to do (re-sequencing? De novo? SNP detection? Indels?Whole genome or targeted?)

    Leave a comment:

Latest Articles

Collapse

  • SEQadmin2
    Multiomic Liquid Biopsy: What DNA/RNA Panels Reveal That DNA Alone Can’t
    by SEQadmin2



    Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?

    Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating
    ...
    10-14-2026, 09:55 AM
  • SEQadmin2
    New Genomics Technologies Take Aim at Long-Standing Limits
    by SEQadmin2


    Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.

    We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing
    ...
    09-28-2026, 10:25 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by SEQadmin2, 10-22-2026, 11:13 AM
0 responses
34 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 10-22-2026, 10:48 AM
0 responses
25 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 10-15-2026, 10:52 AM
0 responses
41 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 10-14-2026, 05:39 AM
0 responses
45 views
0 reactions
Last Post SEQadmin2  
Working...