You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
dada2-paired appears to drop samples which have 0 sequences after filtering, or perhaps denoising, but keeps samples which have zero sequences from merging and beyond.
This leads to samples being dropped from the table, though they remain in the denoising stats.
I've not checked the behavior with the dada2 paired or dada2 pyro or with older versions of dada2.
Steps to reproduce the behavior
Run a dataset including samples with no reads that pass the filtering step, I had a sample with 0 reads and a sample with 6 poor quality reads that were both dropped.
Expected behavior
The samples should be retained with 0 frequency in the table.
Computation Environment
OS: Linux
QIIME 2 Release 2021.2
Questions
Is this a qiime2 issue or a dada2 issue?
Comments
Ideally blanks should be blank, so discarding them in dada2 means the user has to actively notice that they are missing.
A trivial fix is something like: for i in set(denoising_stats.index) - set(table.index): table.loc[i] = 0
Though there may be a more clear way of getting the dropped samples.
I can have a go at implementing that, but I wanted options on if this is something to change in dada2, or here?
It's sort of a dada2 issue, in that we haven't robustly implemented processing zero-read samples through the whole pipeline, therefore they need to be removed from the processing before entering the post-filtering denoising workflow.
That said, it is probably an easy fix on the Q2 side by just adding those zero-read samples back into whatever final table where they are still wanted, as it seems like you are suggesting.
Bug Description
dada2-paired appears to drop samples which have 0 sequences after filtering, or perhaps denoising, but keeps samples which have zero sequences from merging and beyond.
This leads to samples being dropped from the table, though they remain in the denoising stats.
I've not checked the behavior with the dada2 paired or dada2 pyro or with older versions of dada2.
Steps to reproduce the behavior
Run a dataset including samples with no reads that pass the filtering step, I had a sample with 0 reads and a sample with 6 poor quality reads that were both dropped.
Expected behavior
The samples should be retained with 0 frequency in the table.
Computation Environment
Questions
Comments
for i in set(denoising_stats.index) - set(table.index): table.loc[i] = 0
Though there may be a more clear way of getting the dropped samples.
I can have a go at implementing that, but I wanted options on if this is something to change in dada2, or here?
Here is the data I noticed this behavior in: https://unh.box.com/s/pyz250peix6hiyrcye2fnwycidx171sz
The text was updated successfully, but these errors were encountered: