-
Notifications
You must be signed in to change notification settings - Fork 597
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
Update GVS sample QC to support multiple callsets per datasset [VS-177] #7451
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.
2 changes
@@ -66,7 +66,7 @@ SELECT "$NAME_OF_FILTER_SET" filter_set_name, | |||
CASE WHEN INSTR(call_GT, "0") > 0 THEN "het" ELSE "homvar" END as gt_type, -- if GT contains a zero, its a het | |||
titv(ref, alt) as titv, | |||
CASE WHEN gnomad.location IS NULL THEN false ELSE true END in_gnomad | |||
FROM `$FQ_DATASET.vet_all` v | |||
FROM `$FQ_VET_ALL` v |
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.
I think you either need to add FQ_VET_ALL to the README instructions or use a variable like: $FQ_PREFIX_vet_all
scripts/variantstore/callset_QC/filter_set_samples_create_metrics.example.sql
Outdated
Show resolved
Hide resolved
Thanks for catching those! Changed so that only $FQ_PREFIX and $NAME_OF_FILTER_SET are used in the SQL and README. |
Closes https://broadworkbench.atlassian.net/browse/VS-177