Fix documentation for AT_DROPOUT and GC_DROPOUT in PanelMetricsBase.java #1977
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.
The metrics
AT_DROPOUT
andGC_DROPOUT
are calculated in a pretty much identical manner in two different places in Picard. One isTargetMetricsCollector.java
which will perform this functionality forCollectHsMetrics.java
if a reference sequence is provided and the other isGcBiasMetricsCollector.java
. A user has highlighted an inconsistency with the documentation in #1973 . If we look atGcBiasSummaryMetrics.java
, we see:However, in
PanelMetricsBase.java
, we have:which is inconsistent with the previous definition and contains confusing notation.
The implementation inside
GcBiasMetricsCollector.java
although is consistent with its definition above:TargetMetricsCollector.java doesn't have a separate function for this, but the implementation is as follows:
The proposed change here tries to make the documentation for the functionality above more consistent across Picard and easier to read.