-
Notifications
You must be signed in to change notification settings - Fork 27
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 mafft_and_snp_annotated.wdl #194
Conversation
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.
Cool -- two thoughts,
- what if we keep it in the main workflow and stick it in an
if
block (like the iqtree part) based on some workflow level input param? - or if not (and we keep it separate), don't forget to add a stub to
.dockstore.yml
or it won't show up there
Thanks for reminding me about the Yeah I considered making it a toggle—what would you want the conditional to be based on? The snpEff task currently uses the accessions in the reference fasta to fetch the annotations, unless a different list of accessions is specified as an override. What if we want to run the workflow without snpEff—do we provide an empty but not null override? |
So, this basically looks good, but what's weird is that I can't see it on dockstore.org under My Workflows -> github.com/broadinstitute -> Unpublished (or Published). Can you? The "See GitHub Apps Logs" look clean (no errors)... |
I do see it: https://dockstore.org/my-workflows/github.com/broadinstitute/viral-pipelines/mafft_and_snp_annotated |
Nope, I can't see it -- I wonder if dockstore is doing something interesting where it sees that your branch is owned by you and isn't showing it to me? Let's merge it and see what happens. |
Will do. A couple things to fix first. |
The vcf output by snp-sites usus "1" as the chromosome name for its output, while snpEff expects the chromosome name to match that of the reference. This renames the chr name in annotate_vcf_snpeff so snpEff succeeds. This will fail for multi-chr vcfs.
This adds a new workflow,
mafft_and_snp_annotated
, which is the same as mafft_and_snp, except it includes annotation of the vcf via snpEff. It is included as a separate workflow because snpEff may fail if the ref annotations cannot be found, its input does not match the ref provided, etc.