-
Notifications
You must be signed in to change notification settings - Fork 3
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
[ld prune] ld_pruning task is hardcoded to not work on chrX #8
Comments
To do: Test if the CWL errors out. I'm not sure if CWL will error out or just skip chrX. If it errors then the two are equivalent, if it skips, that's a divergence and the divergence label is appropriate. |
The CWL does indeed error out. Seven Bridges job.error.log
Seven Bridges job.out.log The fact the error seems to occur in the R script due to variants selected, instead of in the CWL due to lack of an expected output, has me wondering... does the original pipeline, which by default takes in chr1-23 where chr23 is parsed as chrX, might break if passed into the LD pruning task with all 23 chromosomes. That being said, LD pruning has autosome_only on by default, but also by default skips chr23! |
autosome_only has been added to the CWL, but it seems a little confusing. Iff SB does not treat tooldefaultvalue as something to actually be passed in, ie it's just for the user's information, then:
|
Tested on SB and it confirms what I guessed from looking over the code. Setting nothing should default to true but the config prints false. Setting false sets config to false. Setting to true does not appear in config. This will be added to the WDL once CWL is modified to clarify what the default actually should be. |
It appears that neither the Python pipeline nor the CWL have arguments to change autosome_only. Therefore it is effectively hardcoded in the R script to True. When chrX is run on in the pipeline, it understandably skips it, but this causes Cromwell to panic as the expected RData output is never generated.
The text was updated successfully, but these errors were encountered: