Thanks for your insights.I have also use make.config and flash with the default parameter. I find the result of both is similar in most cases.And in one case I used miseq 2X300 to sequence the 16s v4-v6(530-1100),I did not delete the last 50 base of R2 reads;and the result of mothur is:
raw reads <540 540~590 >590
M1 63792 6663 35127 22600
M2 116539 12847 64723 40096
M3 142317 15702 81105 46874
M4 134210 12796 70243 52208
M5 52356 4229 29066 19520
M6 44229 3917 24038 16620
and the result of flash almost all length is 598~599(I had to set the minoverlap 1),In some ways it seems mothur is better than flash in some case.But I just do it for one time.
Now I have some other questions.What should I do to deal with my stupid work about the v4-v6. It seems it's too long for miseq and I get so many OTUs. No doubt I get a real bed rarefaction curve.But the tops of the community multiplicity is similar to the result of R1 reads. What should I do? More stringent quality control? Delete the low abundance OTUs?Any suggestions?
The another problem is our boss try to sequence about 100 samples and 100000 PE reads per sample. As qiime is too hard to be installed and used for a flasher,And I am not sure about the result of UPARSE. So mothur is my choice. I can use cd-hit or USEARCH to generate OTU. But the classify.seq takes too much time with SILVA.And also the chimera.uchime. UPARSE recommends the gold database and not using a large 16S database like Greengenes. But I am not sure because it seems to have do Chimera filtering during clustering OTU and Chimera filtering again with reference database after clustering OTU.
Any better and faster ways? Thanks.
based on my experience FLASH beats make.config