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

Adding options for GATK #218

Closed
DrJCampbell opened this issue Jun 15, 2020 · 2 comments
Closed

Adding options for GATK #218

DrJCampbell opened this issue Jun 15, 2020 · 2 comments
Assignees

Comments

@DrJCampbell
Copy link

We noticed that using the default Mutect2 options, a large number of insertions were being called based solely on evidence from soft clipped bases. Adding the option '--dont-use-soft-clipped-bases true' got rid of these.

Is there a way to add specific options to parts of the pipeline whilst using the official version of sarek or do we need to fork the project, make changes and merge in future updates?

Thanks
James

@maxulysse
Copy link
Member

You can fork and make a PR for that now, we can then include that in the dev branch.
That could be a fast process.

I'm planning for a minor release in less than a month, so it could definitively be included into all that.

@szilvajuhos
Copy link
Contributor

Cool, I am just building a new PON for our new sequencing data and start testing the latest GATK - so, if you make a fork/PR it would help us also to check this indels issue. Furthermore, by using the -r dev option, your changes can be used by you and by others once the PR is accepted. Generally, the latest updates are in the dev branch, do not have to merge all the time, you can even abandon your fork. Merge only if you are actively adding a new feature/fix.
Cheers: Szilva

@pcantalupo pcantalupo self-assigned this Jul 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants