Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • peromhc
    Senior Member
    • Sep 2009
    • 108

    samtools pileup error @ [fai_build_core]

    Hello,

    I am trying to use samtools pile up for SNP detection.

    I am getting this error with samtools pileup:

    [fai_build_core] line length exceeds 65535 in sequence tucosnp

    'tucosnp' is what I used as my ref sequence to build a bowtie index to which I aligned ~100million Illumina reads. 'tucosnp' is not a whole genome, but instead the product of concatenation of all my contigs generated from a de novo ABySS assembly. The reference is one big fasta file of about 150million bases.

    I'm not sure what I should do here... Splitting up the ref sequence into files of 65,000 bases seems absurd. Maybe I am missing something silly here..

    in $samtools pileup -f ref.fasta aln.sorted.bam

    I assume ref.fasta refers to the reference sequence (reference genome), but maybe I am wrong..

    Any help appreciated!
  • kmcarr
    Senior Member
    • May 2008
    • 1181

    #2
    It doesn't look like samtools is complaining that the sequence is too long; it says that the line is too long. When you concatenated your contigs into your fasta file did your wrap the sequence into multiple lines or write it as a single, ginormous line? It could also be an line break issue of you created the fasta file on one type of system (Mac, Linux, Win) and are running samtools on a different type.

    Comment

    • Mansequencer
      Member
      • Jul 2010
      • 16

      #3
      Hi peromhc,
      I am getting the same error in samtools faidx command ([fai_build_core] line length exceeds 65535 in sequence). Looked at all the scaffolds in my fasta file and nothing seems out of place. Could you please tell how you resolved your issue.
      Thanks,

      Comment

      • nilshomer
        Nils Homer
        • Nov 2008
        • 1283

        #4
        Originally posted by Mansequencer View Post
        Hi peromhc,
        I am getting the same error in samtools faidx command ([fai_build_core] line length exceeds 65535 in sequence). Looked at all the scaffolds in my fasta file and nothing seems out of place. Could you please tell how you resolved your issue.
        Thanks,
        What is the length of your longest line?

        Comment

        • brentp
          Member
          • Apr 2010
          • 72

          #5
          if you're on linux, a quick way to fix is to do:
          fold some.fasta > some.folded.fasta
          which will wrap any lines longer than 80 (or you can specify a length on the command-line).

          Comment

          • Mansequencer
            Member
            • Jul 2010
            • 16

            #6
            Hi Brentp,
            Thanks for your advice. It worked.

            Comment

            • Mamoon Rashid
              Junior Member
              • Feb 2011
              • 8

              #7
              I faced the same problem during "samtools faidx".
              [fai_build_core] line length exceeds 65535 in sequence 'Chromosome1'.
              I realised all bases (~4MB) are in one line. BWA index this without any problem. Then i used Linux "fold" command. AFter that samtools gives me following error--
              [fai_build_core] different line length in sequence 'Chromosome1'.
              In fact i had a reference containing two chromosomes, and i wanted to concatenate these two before indexing. Ultimately i solved this issue as follow--
              1. Removed the fasta header of the second chromosome (file1)
              2. seqret file1 file2
              This file2 is properly handled by samtools faidx.
              PS: Each line in fasta file should be equal in length in order to faidx work AND a single string must not greater than 65535 character.
              Curious to know other's comment.
              Thanks

              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, 07-02-2026, 11:08 AM
              0 responses
              18 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-30-2026, 05:37 AM
              0 responses
              19 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-26-2026, 11:10 AM
              0 responses
              21 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-17-2026, 06:09 AM
              0 responses
              54 views
              0 reactions
              Last Post SEQadmin2  
              Working...