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

Modules/slms 3/1.0 #167

Merged
merged 3 commits into from
Jan 18, 2021
Merged

Modules/slms 3/1.0 #167

merged 3 commits into from
Jan 18, 2021

Conversation

lkhilton
Copy link
Member

This PR fixes a problem with Mutect2 VCF sample name replacement that occurred when the sample ID pulled from the BAM header contains a space (shockingly not uncommon). It also incorporates the full all input from each sub-module to ensure all the final 99-outputs directories are properly populated.

I've also rolled in a patch to all the Manta modules (version 2.0 or higher) that moves the augment_manta_vcf.py script from an input to a parameter to prevent re-running if the lcr-scripts directory moves or changes (see #166).

@lkhilton lkhilton requested a review from rdmorin January 18, 2021 20:50
@rdmorin
Copy link
Collaborator

rdmorin commented Jan 18, 2021

Wow. How does someone even put a space into the sample ID field in the bam header?

Copy link
Collaborator

@rdmorin rdmorin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see updates to the default.yaml config file for versions 2.1 and 2.2. Can you confirm that you've applied this bug fix retroactively and to both the config and smk file for each?

@lkhilton
Copy link
Member Author

I can see it when I look at the files changed section...

@rdmorin
Copy link
Collaborator

rdmorin commented Jan 18, 2021

I see them now. I guess you used version 1.0 and 1.1 of the script consistently with what version was used in the Manta version?

@lkhilton
Copy link
Member Author

Right, I didn't change anything except how the script is called by the Snakemake rule and where it's specified in the config.

@rdmorin
Copy link
Collaborator

rdmorin commented Jan 18, 2021

Seeing as there's active development of Manta on another branch, could you also drop in the changes Lakshay has made to this module (just in version 2.3) so he doesn't get another conflict later? You should be able to paste them right from his PR. I'm specifically thinking of the oncopipe version check and updates to symlinking.

@lkhilton
Copy link
Member Author

I think this is going to result in a conflict for him anyway, but it will be trivial to fix. I can give him a heads up about it.

@rdmorin
Copy link
Collaborator

rdmorin commented Jan 18, 2021

It will auto-merge when it can. I just thought if you add in his changes the auto-merge might happen. It's hard to know

@lkhilton lkhilton merged commit e80e830 into master Jan 18, 2021
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

Successfully merging this pull request may close these issues.

2 participants