feat: improve coverage stratification for datasets with high coverage #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nd change occurences of old coverages to choose coverage depending on parameter for benchmark.
…urrently only works when all benchmarks are high_coverage
BiancaStoecker
changed the title
johanneskoester
approved these changes
Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previous coverage stratification was only 1-10, 10-30 and >= 30. Whole exome sequencing datasets used for benchmarking somatic variant calling include much higher coverages. Therefore the coverage stratification for those datasets is expanded with categories 30-50 (instead of >=30), 50-100, 100-300 and >=300.
Currently coverage stratification is chosen via parameter in preset.yaml for each benchmark. This does not work with the expand statement in rule eval in the Snakefile.