You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sequence resolved insertions (INS) have no span over the reference since they're placed between two bases in the reference. This makes it impossible to measure reciprocal overlap. Truvari now inflates INS SVs' positions by ± their SVLEN // 2, which gives their coordinates a span and allows reciprocal overlap to be calculated.
Figure 1 below is a diagram illustrating what this position inflation looks like.
In addition to this new measurement, Truvari's TruScore has been recalibrated to no-longer put more weight into the PctSeqSimilarity. These two changes allow better consideration of a variant-pair's distance as well as a more uniform distribution of TruScore between DEL/INS SV types. Figure 2A shows the TruScore distribution of version 3.0.1 using data provided by ticket #91. Figure 2B shows the same data's distribution with v3.1.
For this dataset, these changes don't affect the number of matching calls (e.g. same number of TPs). However, because --multimatch wasn't used here, at least 3 variants' "best" matching variant changed. These are at loci where the comparison calls had multiple representations near a base call. This is evident by looking at the number of TP-call_TP_gt calls and seeing that 3 more pairs now have a matching genotype, which speaks to the quality of this caller. However, it should be noted that there are no guarantees that every comparison SV set will have improved or identical results between v3.0.1 and v3.1. I can only say it probably shouldn't be worse.
You may have noticed that in plotting this, we subsetted v3.0.1 results to only the comparison's true positives with state == 'tp'. A new feature of v3.1 is that Truvari will annotate false positives/negatives with their closest matching call. This enables further analysis of benchmarking results to explore how the thresholds affect some calls with respect to flipping between TP/FP. See this discussion and this post for details
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sequence resolved insertions (INS) have no span over the reference since they're placed between two bases in the reference. This makes it impossible to measure reciprocal overlap. Truvari now inflates INS SVs' positions by ± their SVLEN // 2, which gives their coordinates a span and allows reciprocal overlap to be calculated.
Figure 1 below is a diagram illustrating what this position inflation looks like.
In addition to this new measurement, Truvari's
TruScore
has been recalibrated to no-longer put more weight into thePctSeqSimilarity
. These two changes allow better consideration of a variant-pair's distance as well as a more uniform distribution ofTruScore
between DEL/INS SV types. Figure 2A shows theTruScore
distribution of version 3.0.1 using data provided by ticket #91. Figure 2B shows the same data's distribution with v3.1.For this dataset, these changes don't affect the number of matching calls (e.g. same number of TPs). However, because
--multimatch
wasn't used here, at least 3 variants' "best" matching variant changed. These are at loci where the comparison calls had multiple representations near a base call. This is evident by looking at the number of TP-call_TP_gt calls and seeing that 3 more pairs now have a matching genotype, which speaks to the quality of this caller. However, it should be noted that there are no guarantees that every comparison SV set will have improved or identical results between v3.0.1 and v3.1. I can only say it probably shouldn't be worse.You may have noticed that in plotting this, we subsetted v3.0.1 results to only the comparison's true positives with
state == 'tp'
. A new feature of v3.1 is that Truvari will annotate false positives/negatives with their closest matching call. This enables further analysis of benchmarking results to explore how the thresholds affect some calls with respect to flipping between TP/FP. See this discussion and this post for detailsBeta Was this translation helpful? Give feedback.
All reactions