-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix running without any MELT inputs #6
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.
Other than the typo I found, this looks straightforward.
My only other suggestion is that if we want to run without ref_std_melt_vcfs, I suppose it's possible we might want to do the same without manta or wham, so logically, similar changes could be made e.g. on line 582 and 583. In actuality, I don't think we'll ever do that, but I figured it's worth considering and explicitly rejecting (or explicitly punting for now).
wdl/GATKSVPipelineSingleSample.wdl
Outdated
runtime_attr_override=runtime_attr_filter_vcf_by_id | ||
} | ||
} | ||
if (use_melt) { |
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.
if (use_melt) { | |
if (use_delly) { |
Typo?
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.
Whoops, thanks for pointing that out!
At this point I don't think we envision turning off manta or wham inputs, so I'm inclined not to add extra complexity around handling that, until it becomes a thing. |
Update Dockerfile
This fixes some points in the WDL which were failing when run with
use_melt
set to false and no melt inputs provided for the reference panel.Also added an input JSON file to demonstrate how to run without MELT, which will likely be the most frequent use case when the pipeline is deployed to Terra.