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
VCFs aren't always created with a strong adherence to the format's specification.
8
-
9
-
Truvari expects input VCFs to be valid so that it will only output valid VCFs.
10
-
11
-
We've developed a separate tool that runs multiple validation programs and standard VCF parsing libraries in order to validate a VCF.
12
-
13
-
Run [this program](https://github.com/acenglish/usable_vcf) over any VCFs that are giving Truvari trouble.
14
-
15
-
Furthermore, Truvari expects 'resolved' SVs (e.g. DEL/INS) and will not interpret BND signals across SVTYPEs (e.g. combining two BND lines to match a DEL call). A brief description of Truvari bench methodology is linked below.
16
-
17
-
Finally, Truvari does not handle multi-allelic VCF entries and as of v4.0 will throw an error if multi-allelics are encountered. Please use `bcftools norm` to split multi-allelic entries.
18
-
19
6
# Index
20
7
21
8
-[[Updates|Updates]]
22
9
-[[Installation|Installation]]
23
-
- Truvari Commands:
24
-
-[[anno|anno]]
25
-
-[[bench|bench]]
26
-
-[[collapse|collapse]]
27
-
-[[consistency|consistency]]
28
-
-[[divide|divide]]
29
-
-[[ga4gh|ga4gh]]
30
-
-[[phab|phab]]
31
-
-[[refine|refine]]
32
-
-[[segment|segment]]
33
-
-[[stratify|stratify]]
34
-
-[[vcf2df|vcf2df]]
35
10
-[[Development|Development]]
36
-
-[[Citations|Citations]]
11
+
12
+
Truvari Commands:
13
+
- Benchmarking
14
+
-[[bench|bench]] - Performance metrics from comparison of two VCFs
15
+
-[[refine|refine]] - Automated bench result refinement with phab
Copy file name to clipboardExpand all lines: docs/bench.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,6 +242,8 @@ This VCF makes different results depending on the `--pick` parameter
242
242
| ac | TP | TP | FP |
243
243
| multi | TP | TP | TP |
244
244
245
+
Note that multi-matching should be used with care. By allowing SVs to match multiple times, performance metrics become inflated in a way that’s misleading. Recall can exceed the number of calls made. Precision can be skewed if one baseline event explains many false calls. For example, if a single comparison SV matches to two baseline SVs, the caller only made one prediction, yet it’s getting credit for finding two events, thus inflating recall.
0 commit comments