fix: enforce ploidy in GATK gCNV ploidy calling wrapper #377
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
In particular for Agilent V8, the ploidy calls were very unreliable. We need to hard-fix this in the ploidy calling to get results at all. Complementary methods must be used for checking ploidy sanity.
holtgrewe
force-pushed
the
fix-gcnv-ploidy-calling
branch
from
5a1c5b6 to
cd0843a
Compare
1 similar comment
This was referenced Dec 9, 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.
In particular for Agilent V8, the ploidy calls were very unreliable. We need to hard-fix this in the ploidy calling to get results at all. Complementary methods must be used for checking ploidy sanity.