-
Notifications
You must be signed in to change notification settings - Fork 5
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
add options to stop filtering by PASS
#18
Conversation
|
Also added the version bump to prepare the next release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Daniel Straub <42973691+d4straub@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't filtering by PASS much more standard than skipping the filtering?
Depends, TCGA never filtered their results by PASS. Usability wise it probably does not matter. Decided to set it to not filter per standard because Leon ran into these issues. |
In my experience you just get a ton of noise with the clinical data if you don't filter. This has at least tripped me up many times. |
PR checklist
Related to #9
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).We want to stop assuming that everybody just wants the
PASS
variants in the final MAF file. This is now an optional input :)