hildebra / lotus2

Amplicon sequencing pipelines suitable for SSU (16S, 18S), LSU (23S, 28S) and ITS.
http://lotus2.earlham.ac.uk/
GNU General Public License v3.0
52 stars 17 forks source link

Regarding the fate of reads passed through each step of Lotus2 #39

Closed ShailNair closed 1 year ago

ShailNair commented 1 year ago

Hi, thank you for this easy-to-use amplicon read analysis pipeline. I was wondering if there is a way to get the number of reads passed through each step. DADA2 provides read counts across samples for each step of processing through:

getN <- function(x) sum(getUniques(x))
track <- cbind(out, sapply(dadaFs, getN), sapply(mergers, getN), rowSums(seqtab), 
rowSums(seqtab.nochim))
# If processing a single sample, remove the sapply calls: e.g. replace sapply(dadaFs, getN) with getN(dadaFs)
colnames(track) <- c("input", "filtered", "denoised", "merged", "tabled", "nonchim")
rownames(track) <- sample.names
head(track)

It would be very nice if lotus2 could do that.

ozkurt commented 1 year ago

Thank you for your question. In the log file LotuS_runlog.txt, you can find information about the number of reads passed/filtered. Here's an example:

Screenshot 2023-04-20 at 16 30 42
ShailNair commented 1 year ago

Got it. thanks