Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • sfh838t
    Member
    • Apr 2014
    • 29

    velvet columbus reference errors

    I have seen some posts about using velvet with a reference, but they have not helped me........
    I am trying to assemble a plant genome using a related species as reference. Trying to use velvet columbus, but I don't seem to be able to get the command line right.
    following the manual, using:
    velveth dir_name 31 -reference ref.fasta -sam illumina_align.sam
    this way I get: -sam file cannot contain reference sequence.
    if I try to add -short or -long in front of the -sam switch, it seems to ignore the -reference switch and I get that my "read1" (which is supposed to be the reference) is too long.
    I have removed from the sam file anything that might have something to do with the reference, but still get the same error.
    I am not good with the linux command line and I am getting the impression i am forgetting some little space, comma, slash or something.
    I used bowtie2 for the alignment of the single end read Illumina reads. Does someone know if bowtie puts the reference sequence into it's sam output anywhere? Or, since all the posts about velvet columbus I have been able to find deal with PE input, can velvet with reference only be used with PE reads?
  • ctseto
    Member
    • Oct 2013
    • 44

    #2
    By its nature, SAM has the alignment in it (SAM=Sequence Alignment Map).

    First: Did you sort your SAM file? (will need samtools for this).

    Checking the manual again, it looks like it should be:

    Code:
    velveth $FOLDERNAME $KMER -reference ref.fasta -shortPaired -sam illumina_align.sam
    Can you post the first few lines of your sam file by using

    Code:
    head illumina_align.sam
    Since you already have to do the alignment of your reads to the reference, have you tried looking at the alignments? Are there dips in coverage or re-arrangements, things like that?

    Comment

    • mastal
      Senior Member
      • Mar 2009
      • 666

      #3
      Originally posted by sfh838t View Post
      velveth dir_name 31 -reference ref.fasta -sam illumina_align.sam
      If you have single end reads, you should also have '-short' before the '-sam' switch.

      Have a look at the Columbus manual.


      I would leave the header lines in the sam file.
      The sam file should be sorted by read name. The default with samtools is to sort the files by chromosome and alignment position.

      Also check the requirements for the reference.fasta file.
      Last edited by mastal; 05-09-2014, 12:15 PM.

      Comment

      • sfh838t
        Member
        • Apr 2014
        • 29

        #4
        thanks for any and all replies
        mastal: if I put -short before the sam, velvet seems to ignore the -reference switch. It then reads both files, puts them together into one file and like I said, I get "read 1" is too long" error.

        ctseto: I used both sorted and unsorted files. I used unsorted at first, then noticed that was wrong and then used the very same file(s) that someone else tried for me (and that ran perfectly fine for them) and I ALWAYS get the very same error. Since I want to do an assembly I used the same entire reference seq for velvet that I used for bwa.

        I have looked at the alignments (IGV) and yes, there are areas with lots of coverage, and then some without. I am working with a plant, and I do know that there will be lots and lots of repeat elements. but honestly, I do not see how that would stop velvet from even reading my sam file, because the error shows up as soon as the sam file is opening. takes about 3 secs flat .

        Any further suggestions anyone?

        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
        11 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-30-2026, 05:37 AM
        0 responses
        13 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-26-2026, 11:10 AM
        0 responses
        20 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...