-
Notifications
You must be signed in to change notification settings - Fork 10
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
Consider changing from MEAN_TARGET_COVERAGE to MEDIAN_TARGET_COVERAGE for exome/panels #1719
Comments
Good suggestion! We have noticed a big difference for low quality samples, where the MEAN is not describing the true quality of the analysis. |
Sounds good! |
I would say TGA samples, @vwirta agreed? |
I always though TGA = panel and wes ;) |
feat(expected_coverage): use median coverage, fixes #1719
@annaengstrom, The changes has been merged to develop and will be a part of the next release of MIP |
done as of mip v9.1.2 |
Describe the bug
MIP threshold considers MEAN_TARGET_COVERAGE, however for a poor quality sample MEAN_TARGET_COVERAGE may be deviating a lot from MEDIAN_TARGET_COVERAGE.
MEDIAN_TARGET_COVERAGE is a much better measurement for covarage for poor quality samples. It also works well for good quality samples (not deviating much between MEAN_TARGET_COVERAGE and MEDIAN_TARGET_COVERAGE).
Therefore, considering changing from MEAN_TARGET_COVERAGE to MEDIAN_TARGET_COVERAGE in MIP.
The phenomenon has been observed for multiple samples/projects in BALSAMIC analysis.
The text was updated successfully, but these errors were encountered: