VelvetOptimizer always chooses 31 as the kmer length and never looks further than that?
Hello!
I run this line:
VelvetOptimiser.pl -d 'outputfolder' -s 21 -e 91 -f '-fasta -shortPaired ./myfile.fasta'
and velvetoptimizer always gives me a result of 31 as my ideal Kmer. it doesnt even test beyond that.
I dont really understand what I am doing wrong can anyone help me or explain my VelvetOptimizer always goes to its default parameter for kmer length to test?
Thank you!
• 1,960 views
•
link
written
by
katherine.lavoie •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Cochran–Armitage test results
written by Eliza •
-
vcf file has an empty sample id
written by yh362 •
-
Ximmer running error
written by S AR
-
Forum: discosnp output on OSX 10.10.1
written by rob.lanfear •
-
VelvetOptimiser: optimum cov_cutoff, PE insert stats, 2 Insert Size Libraries, N's without scaffold…
written by drtamermansour •
-
How is this blastresult possible?
written by ronaldnieuwenhuis •
-
How to run velvetoptimiser on paired-end FASTQ datasets
written by whatup •
-
Genomecoveragebed - Bedtool For Reporting Per Base Genome Coverage
written by Varun Gupta
-
Bl2Seq/Blastall And The E Value Help
written by Gturco •
-
Biopython Ncbistandalone Blastall Gives Different Result Than Calling Blastall Directly From Cmd
written by Niek De Klein
By default velvet uses a maxkerlength of 31 which is what you are seeing. You need to re-compile
velvetif you want to use longerkmers. Do you have a reason to believe velvet could benefit from using longer k-mers?I will link these threads on how to make the necessary change: Velvet can't handle k-mers as long as X! We'll stick to 32 if you don't mind. and Question: Can't change MAXKMERLENGTH on Velvet