Optional blacklist VCF to for labeling artifacts in Permutect weak-labeling mode #9136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@LeeTL1220 Small change for Permutect data here, usually irrelevant. In most use cases, it will be possible to train with a GIAB truth VCF to label data. When there is not, this PR allows users to optionally specify a PoN as a hint that unlabeled data are probably actually artifacts.
This should not in any way be interpreted as Permutect using a PoN for variant calling. It has zero effect on our DREAM and Linseq evaluations, which use an NA12878 sample for training.