Closed jashapiro closed 3 years ago
Could be useful for training too. It takes the challenge of picking a threshold for dead cell / debris removal and reframes it as a mixture model. The cases where it doesn't work well are samples where there is not a mixture (i.e., no dead cells/debris or no live ones).
Can this be closed?
Yes, I suppose it is largely superseded by our current QC reports.
I would say yes.
The current Alevin workflow does not perform any particular QC steps; we have been doing this by hand so far.
We should implement some automated QC!
The simplest version of this would be adding alevinQC to the
run-alevin.nf
workflow. For this to work, the current alevin workflow will need to be modified to include the--dumpFeatures
flagWhile this is pretty easy, it isn't always as robust as we might like, and does not support cross-library summarization (like MultiQC?), which we might like to add in the future.
To allow for future flexibility, we should make sure to output the entire AlevinQC report directory, not just the
html
files, so that we may be able to process them later after reading in data tables withreadAlevinQC()
or similar.