-
Notifications
You must be signed in to change notification settings - Fork 36
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
Snakemake workflow makes Titan assume male gender regardless of how config.yaml file is configured. #72
Comments
Hi @d-henness You're correct - in the snakemake pipeline the I was in the middle of adding the feature to predict the gender from the ichorCNA analysis so that users can use For now, I will enable the user to use |
For now, assumes that sample set contains all males or all females but not both. #72 For sample sets with both, please use `male` so that chrX is excluded allelic CN analysis
Thank you @gavinha. It would be helpful to allow the workflow to run both of these. Perhaps something could be added to the
The gender field could be optional and default to male if not present so as not to interrupt workflows based on older versions. I can make up a pull request for this. |
As far as I can tell, changing the sex option in the config.yaml file does not actually change anything about the calculation. The --gender option does not appear in the shell command for runTitanCNA rule, so titanCNA.R will always use the default gender which is male. Was this intentional? Is there some reason we shouldn't be specifying the gender?
The text was updated successfully, but these errors were encountered: