Skip to content
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

cookiecutter always adds unmatched normal to default config #50

Closed
rdmorin opened this issue Jun 15, 2020 · 1 comment
Closed

cookiecutter always adds unmatched normal to default config #50

rdmorin opened this issue Jun 15, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@rdmorin
Copy link
Collaborator

rdmorin commented Jun 15, 2020

Could the cookiecutter be modified to ask whether the user wants to analyze unpaired tumours with with unmatched normal? I don't think this is asked (or at least not in a way that is intuitive) so I keep ending up with this config.

            genome:
                run_paired_tumours: True
                run_unpaired_tumours_with: "unmatched_normal"
                run_paired_tumours_as_unpaired: False
            capture:
                run_paired_tumours: True
                run_unpaired_tumours_with: "unmatched_normal"
                run_paired_tumours_as_unpaired: False```
@BrunoGrandePhD
Copy link
Contributor

That can definitely be done. In fact, with the new generate_pairs() function, I think the same options should be available for the cookiecutter template, namely matched_only, allow_unmatched, and no_normal (in addition to omit). I can tackle this on the weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants