-
Notifications
You must be signed in to change notification settings - Fork 72
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
Make LocalizeReads Optional in GatherSampleEvidence #620
Conversation
…eReads should be run with default value of true; if false, the task will be skipped.
…/bam from LocalizeReads if itis called only
…/bam from LocalizeReads if itis called only
… the original file
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.
This is looking good! I have a minor suggestion on the organization of the new input parameter. Also, can you describe your testing in more detail? (ie. did you test with run_localize_reads = true and false, and did you verify whether LocalizeReads was run/not run accordingly?)
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.
Thanks for running the additional test and for reorganizing the inputs! Looks good to merge
This pull request addresses issue #585. The LocalizeReads task was introduced to GatherSampleEvidence to simplify cases for CRAMs sourced from requester-pays and multi-regional buckets to simplify the code, but could be skipped in some cases for some cost and time savings. An optional boolean variable set to a default value of true to run LocalizeReads was added. When set to false, the LocalizeReads task is skipped.
This passed validation with both womtool and cromshell against the reference panel. The input in the json was changed to both True and False and ran as expected in both scenarios.