feat(qannotate): allow the homCutoff option to be used in IndelConfidenceMode #397
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.
This pull request enhances the configurability and test coverage of the
IndelConfidenceModeclass, improves code clarity, and fixes minor typos. The most significant change is the introduction of a configurable homopolymer cutoff, which is now tested in the unit tests. Additionally, the code and comments have been improved for readability and maintainability.Configurability and Logic Improvements:
homopolymerCutoffparameter toIndelConfidenceMode, allowing users to specify the cutoff via options or command line (--homCutoff). The logic for determining high-confidence indels now uses this parameter instead of a hardcoded value. [1] [2] [3]Documentation and Code Quality:
loadMaskandisRepeat, to clarify their purpose and usage. [1] [2]DESCRITPION_INFO_CONFIDENCEtoDESCRIPTION_INFO_CONFIDENCE, and improved code formatting and consistency. [1] [2] [3]Testing Enhancements:
homopolymerOptionTest) to verify that the configurable homopolymer cutoff is correctly applied, including new helper methods to generate appropriate test VCF files. [1] [2]assertSameandassertEqualsfor better assertion semantics, and updated test method names to follow Java conventions. [1] [2]General Code Cleanup: