-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify infer strandedness from current subsampling + infer step #1095
Comments
To even complicate matters, the most recent release of BBTools (39.03) now also contains a new tool to infer strandedness called I have not done any comprehensive evaluation, but it has a |
@pinin4fjords thanks, yes, that looks ideal! Very clear. |
The new subway map is labeled (Salmon, fq) - I agree that the Salmon is more important than the fq, but fq happens before subsampling, so you may wish to switch the order in which they are written on the subway map depending on your goals. |
ping @maxulysse ! |
done in #1307 |
yeah, I saw the comment and modified my PR in accordance, and then said I've done it |
You were too fast for me, I didn't think you'd already have addressed the comment. All good now :-) |
Description of feature
The current nf-core/rnaseq (3.12.0) has initial steps to infer strandedness by first subsample fq, then Salmon to infer strandedness. This is an optional step and has led to some confusion as it's not actually subsampling all the reads.
On a nf-core slack discussion, @drpatelh suggested:
The suggestion is to combine into one station / one module or workflow step. That would clean up the metro diagram and avoid the confusion.
This could be called
The text was updated successfully, but these errors were encountered: