chimera.vsearch log

Hi,

I noticed that the mothur.*.log doesn’t keep the same level of detail as chimera.vsearch in interactive mode. Is there a way to keep that?

I get this, for each sample in my screen

vsearch v2.4.0_linux_x86_64, 31.4GB RAM, 8 cores
https://github.com/torognes/vsearch

Reading file v1v3testre.trim.good.unique.good.filter.unique.precluster.temp 100%  
4045887 nt in 9231 seqs, min 399, max 507, avg 438
Masking 100%  
Sorting by abundance 100%
Counting unique k-mers 100%  
Detecting chimeras 100%  
Found 6761 (73.2%) chimeras, 2348 (25.4%) non-chimeras,
and 122 (1.3%) borderline sequences in 9231 unique sequences.
Taking abundance information into account, this corresponds to
11786 (36.0%) chimeras, 20735 (63.4%) non-chimeras,
and 206 (0.6%) borderline sequences in 32727 total sequences.

It took 18 secs to check 9231 sequences from group 35355_1_16S_UNSW_AGGCATCT_AAGCAGCA_BJTVW_S1.

but only this is what is kept in the mothur log file

It took 19 secs to check 9231 sequences from group 35355_1_16S_UNSW_AGGCATCT_AAGCAGCA_BJTVW_S1.

Thanks for the suggestion! I will add it to our list. You can follow the progress on the change here, https://github.com/mothur/mothur/issues/419.