forked from samtools/bcftools
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathbcftools.html
4742 lines (4700 loc) · 188 KB
/
bcftools.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="generator" content="Asciidoctor 2.0.15.dev">
<title>bcftools(1)</title>
<link rel="stylesheet" href="./docbook-xsl.css">
</head>
<body class="manpage">
<div id="header">
<h1>bcftools(1) Manual Page</h1>
<h2 id="_name">NAME</h2>
<div class="sectionbody">
<p>bcftools - utilities for variant calling and manipulating VCFs and BCFs.</p>
</div>
</div>
<div id="content">
<div class="sect1">
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="paragraph">
<p><strong>bcftools</strong> [--version|--version-only] [--help] [<em>COMMAND</em>] [<em>OPTIONS</em>]</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph">
<p>BCFtools is a set of utilities that manipulate variant calls in the Variant
Call Format (VCF) and its binary counterpart BCF. All commands work
transparently with both VCFs and BCFs, both uncompressed and BGZF-compressed.</p>
</div>
<div class="paragraph">
<p>Most commands accept VCF, bgzipped VCF and BCF with filetype detected
automatically even when streaming from a pipe. Indexed VCF and BCF
will work in all situations. Un-indexed VCF and BCF and streams will
work in most, but not all situations. In general, whenever multiple VCFs are
read simultaneously, they must be indexed and therefore also compressed.
(Note that files with non-standard index names can be accessed as e.g.
"<code>bcftools view -r X:2928329 file.vcf.gz##idx##non-standard-index-name</code>".)</p>
</div>
<div class="paragraph">
<p>BCFtools is designed to work on a stream. It regards an input file "-" as the
standard input (stdin) and outputs to the standard output (stdout). Several
commands can thus be combined with Unix pipes.</p>
</div>
<div class="sect2">
<h3 id="_version">VERSION</h3>
<div class="paragraph">
<p>This manual page was last updated <strong>2021-09-06 16:23 BST</strong> and refers to bcftools git version <strong>1.13-37-g4c71bfb+</strong>.</p>
</div>
</div>
<div class="sect2">
<h3 id="_bcf1">BCF1</h3>
<div class="paragraph">
<p>The BCF1 format output by versions of samtools <= 0.1.19 is <strong>not</strong>
compatible with this version of bcftools. To read BCF1 files one can use
the view command from old versions of bcftools packaged with samtools
versions <= 0.1.19 to convert to VCF, which can then be read by
this version of bcftools.</p>
</div>
<div class="listingblock">
<div class="content">
<pre> samtools-0.1.19/bcftools/bcftools view file.bcf1 | bcftools view</pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="_variant_calling">VARIANT CALLING</h3>
<div class="paragraph">
<p>See <em>bcftools call</em> for variant calling from the output of the
<em>samtools mpileup</em> command. In versions of samtools <= 0.1.19 calling was
done with <em>bcftools view</em>. Users are now required to choose between the old
samtools calling model (<em>-c/--consensus-caller</em>) and the new multiallelic
calling model (<em>-m/--multiallelic-caller</em>). The multiallelic calling model
is recommended for most tasks.</p>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_list_of_commands">LIST OF COMMANDS</h2>
<div class="sectionbody">
<div class="paragraph">
<p>For a full list of available commands, run <strong>bcftools</strong> without arguments. For a full
list of available options, run <strong>bcftools</strong> <em>COMMAND</em> without arguments.</p>
</div>
<div class="ulist">
<ul>
<li>
<p><strong><a href="#annotate">annotate</a></strong> .. edit VCF files, add or remove annotations</p>
</li>
<li>
<p><strong><a href="#call">call</a></strong> .. SNP/indel calling (former "view")</p>
</li>
<li>
<p><strong><a href="#cnv">cnv</a></strong> .. Copy Number Variation caller</p>
</li>
<li>
<p><strong><a href="#concat">concat</a></strong> .. concatenate VCF/BCF files from the same set of samples</p>
</li>
<li>
<p><strong><a href="#consensus">consensus</a></strong> .. create consensus sequence by applying VCF variants</p>
</li>
<li>
<p><strong><a href="#convert">convert</a></strong> .. convert VCF/BCF to other formats and back</p>
</li>
<li>
<p><strong><a href="#csq">csq</a></strong> .. haplotype aware consequence caller</p>
</li>
<li>
<p><strong><a href="#filter">filter</a></strong> .. filter VCF/BCF files using fixed thresholds</p>
</li>
<li>
<p><strong><a href="#gtcheck">gtcheck</a></strong> .. check sample concordance, detect sample swaps and contamination</p>
</li>
<li>
<p><strong><a href="#index">index</a></strong> .. index VCF/BCF</p>
</li>
<li>
<p><strong><a href="#isec">isec</a></strong> .. intersections of VCF/BCF files</p>
</li>
<li>
<p><strong><a href="#merge">merge</a></strong> .. merge VCF/BCF files files from non-overlapping sample sets</p>
</li>
<li>
<p><strong><a href="#mpileup">mpileup</a></strong> .. multi-way pileup producing genotype likelihoods</p>
</li>
<li>
<p><strong><a href="#norm">norm</a></strong> .. normalize indels</p>
</li>
<li>
<p><strong><a href="#plugin">plugin</a></strong> .. run user-defined plugin</p>
</li>
<li>
<p><strong><a href="#polysomy">polysomy</a></strong> .. detect contaminations and whole-chromosome aberrations</p>
</li>
<li>
<p><strong><a href="#query">query</a></strong> .. transform VCF/BCF into user-defined formats</p>
</li>
<li>
<p><strong><a href="#reheader">reheader</a></strong> .. modify VCF/BCF header, change sample names</p>
</li>
<li>
<p><strong><a href="#roh">roh</a></strong> .. identify runs of homo/auto-zygosity</p>
</li>
<li>
<p><strong><a href="#sort">sort</a></strong> .. sort VCF/BCF files</p>
</li>
<li>
<p><strong><a href="#stats">stats</a></strong> .. produce VCF/BCF stats (former vcfcheck)</p>
</li>
<li>
<p><strong><a href="#view">view</a></strong> .. subset, filter and convert VCF and BCF files</p>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_list_of_scripts">LIST OF SCRIPTS</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Some helper scripts are bundled with the bcftools code.</p>
</div>
<div class="ulist">
<ul>
<li>
<p><strong><a href="#plot-vcfstats">plot-vcfstats</a></strong> .. plots the output of <strong><a href="#stats">stats</a></strong></p>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="_commands_and_options">COMMANDS AND OPTIONS</h2>
<div class="sectionbody">
<div class="sect2">
<h3 id="common_options">Common Options</h3>
<div class="paragraph">
<p>The following options are common to many bcftools commands. See usage for
specific commands to see if they apply.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><em>FILE</em></dt>
<dd>
<p>Files can be both VCF or BCF, uncompressed or BGZF-compressed. The file "-"
is interpreted as standard input. Some tools may require tabix- or
CSI-indexed files.</p>
</dd>
<dt class="hdlist1"><strong>-c, --collapse</strong> <em>snps</em>|<em>indels</em>|<em>both</em>|<em>all</em>|<em>some</em>|<em>none</em>|<em>id</em></dt>
<dd>
<p>Controls how to treat records with duplicate positions and defines compatible
records across multiple input files. Here by "compatible" we mean records which
should be considered as identical by the tools. For example, when performing
line intersections, the desire may be to consider as identical all sites with
matching positions (<strong>bcftools isec -c</strong> <em>all</em>), or only sites with matching variant
type (<strong>bcftools isec -c</strong> <em>snps</em>  <strong>-c</strong> <em>indels</em>), or only sites with all alleles
identical (<strong>bcftools isec -c</strong> <em>none</em>).</p>
<div class="dlist">
<dl>
<dt class="hdlist1"><em>none</em></dt>
<dd>
<p>only records with identical REF and ALT alleles are compatible</p>
</dd>
<dt class="hdlist1"><em>some</em></dt>
<dd>
<p>only records where some subset of ALT alleles match are compatible</p>
</dd>
<dt class="hdlist1"><em>all</em></dt>
<dd>
<p>all records are compatible, regardless of whether the ALT alleles
match or not. In the case of records with the same position, only
the first will be considered and appear on output.</p>
</dd>
<dt class="hdlist1"><em>snps</em></dt>
<dd>
<p>any SNP records are compatible, regardless of whether the ALT
alleles match or not. For duplicate positions, only the first SNP
record will be considered and appear on output.</p>
</dd>
<dt class="hdlist1"><em>indels</em></dt>
<dd>
<p>all indel records are compatible, regardless of whether the REF
and ALT alleles match or not. For duplicate positions, only the
first indel record will be considered and appear on output.</p>
</dd>
<dt class="hdlist1"><em>both</em></dt>
<dd>
<p>abbreviation of "<strong>-c</strong> <em>indels</em>  <strong>-c</strong> <em>snps</em>"</p>
</dd>
<dt class="hdlist1"><em>id</em></dt>
<dd>
<p>only records with identical ID column are compatible.
Supported by <strong><a href="#merge">bcftools merge</a></strong> only.</p>
</dd>
</dl>
</div>
</dd>
<dt class="hdlist1"><strong>-f, --apply-filters</strong> <em>LIST</em></dt>
<dd>
<p>Skip sites where FILTER column does not contain any of the strings listed
in <em>LIST</em>. For example, to include only sites which have no filters set,
use <strong>-f</strong> <em>.,PASS</em>.</p>
</dd>
<dt class="hdlist1"><strong>--no-version</strong></dt>
<dd>
<p>Do not append version and command line information to the output VCF header.</p>
</dd>
<dt class="hdlist1"><strong>-o, --output</strong> <em>FILE</em></dt>
<dd>
<p>When output consists of a single stream, write it to <em>FILE</em> rather than
to standard output, where it is written by default.</p>
</dd>
<dt class="hdlist1"><strong>-O, --output-type</strong> <em>b</em>|<em>u</em>|<em>z</em>|<em>v</em></dt>
<dd>
<p>Output compressed BCF (<em>b</em>), uncompressed BCF (<em>u</em>), compressed VCF (<em>z</em>), uncompressed VCF (<em>v</em>).
Use the -Ou option when piping between bcftools subcommands to speed up
performance by removing unnecessary compression/decompression and
VCF←→BCF conversion.</p>
</dd>
<dt class="hdlist1"><strong>-r, --regions</strong> <em>chr</em>|<em>chr:pos</em>|<em>chr:beg-end</em>|<em>chr:beg-</em>[,…​]</dt>
<dd>
<p>Comma-separated list of regions, see also <strong>-R, --regions-file</strong>. Overlapping
records are matched even when the starting coordinate is outside of the
region, unlike the <strong>-t/-T</strong> options where only the POS coordinate is checked.
Note that <strong>-r</strong> cannot be used in combination with <strong>-R</strong>.</p>
</dd>
<dt class="hdlist1"><strong>-R, --regions-file</strong> <em>FILE</em></dt>
<dd>
<p>Regions can be specified either on command line or in a VCF, BED, or
tab-delimited file (the default). The columns of the tab-delimited file
can contain either positions (two-column format) or intervals (three-column
format): CHROM, POS, and, optionally, END, where positions are 1-based
and inclusive. The columns of the tab-delimited BED file are also
CHROM, POS and END (trailing columns are ignored), but coordinates
are 0-based, half-open. To indicate that a file be treated as BED rather
than the 1-based tab-delimited file, the file must have the ".bed" or
".bed.gz" suffix (case-insensitive). Uncompressed files are stored in
memory, while bgzip-compressed and tabix-indexed region files are streamed.
Note that sequence names must match exactly, "chr20" is not the same as
"20". Also note that chromosome ordering in <em>FILE</em> will be respected,
the VCF will be processed in the order in which chromosomes first appear
in <em>FILE</em>. However, within chromosomes, the VCF will always be
processed in ascending genomic coordinate order no matter what order they
appear in <em>FILE</em>. Note that overlapping regions in <em>FILE</em> can result in
duplicated out of order positions in the output.
This option requires indexed VCF/BCF files. Note that <strong>-R</strong> cannot be used
in combination with <strong>-r</strong>.</p>
</dd>
<dt class="hdlist1"><strong>--regions-overlap</strong> <em>0</em>|<em>1</em>|<em>2</em></dt>
<dd>
<p>This option controls how overlapping records are determined:
set to <strong>0</strong> if the VCF record has to have POS inside a region
(this corresponds to the default behavior of <strong>-t/-T</strong>);
set to <strong>1</strong> if also overlapping records with POS outside a region
should be included (this is the default behavior of <strong>-r/-R</strong>); or set
to <strong>2</strong> to include only true overlapping variation (compare
the full VCF representation "<code>TA>T-</code>" vs the true sequence variation "<code>A>-</code>").</p>
</dd>
<dt class="hdlist1"><strong>-s, --samples</strong> [^]<em>LIST</em></dt>
<dd>
<p>Comma-separated list of samples to include or exclude if prefixed
with "^".
The sample order is updated to reflect that given on the command line.
Note that in general tags such as INFO/AC, INFO/AN, etc are not updated
to correspond to the subset samples. <strong><a href="#view">bcftools view</a></strong> is the
exception where some tags will be updated (unless the <strong>-I, --no-update</strong>
option is used; see <strong><a href="#view">bcftools view</a></strong> documentation). To use updated
tags for the subset in another command one can pipe from <strong>view</strong> into
that command. For example:</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> bcftools view -Ou -s sample1,sample2 file.vcf | bcftools query -f %INFO/AC\t%INFO/AN\n</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-S, --samples-file</strong> <em class="^">FILE</em><a id="samples_file"></a></dt>
<dd>
<p>File of sample names to include or exclude if prefixed with "^".
One sample per line. See also the note above for the <strong>-s, --samples</strong>
option.
The sample order is updated to reflect that given in the input file.
The command <strong><a href="#call">bcftools call</a></strong> accepts an optional second
column indicating ploidy (0, 1 or 2) or sex (as defined by
<strong><a href="#ploidy">--ploidy</a></strong>, for example "F" or "M"), for example:</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> sample1 1
sample2 2
sample3 2</pre>
</div>
</div>
<div class="paragraph">
<p>or</p>
</div>
<div class="listingblock">
<div class="content">
<pre> sample1 M
sample2 F
sample3 F</pre>
</div>
</div>
<div class="paragraph">
<p>If the second column is not present, the sex "F" is assumed.
With <strong><a href="#call">bcftools call</a> -C</strong> <em>trio</em>, PED file is expected.
The program ignores the first column and the last indicates sex (1=male, 2=female), for example:</p>
</div>
<div class="listingblock">
<div class="content">
<pre> ignored_column daughterA fatherA motherA 2
ignored_column sonB fatherB motherB 1</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-t, --targets</strong> [^]<em>chr</em>|<em>chr:pos</em>|<em>chr:from-to</em>|<em>chr:from-</em>[,…​]</dt>
<dd>
<p>Similar as <strong>-r, --regions</strong>, but the next position is accessed by streaming the
whole VCF/BCF rather than using the tbi/csi index. Both <strong>-r</strong> and <strong>-t</strong> options
can be applied simultaneously: <strong>-r</strong> uses the index to jump to a region
and <strong>-t</strong> discards positions which are not in the targets. Unlike <strong>-r</strong>, targets
can be prefixed with "^" to request logical complement. For example, "^X,Y,MT"
indicates that sequences X, Y and MT should be skipped.
Yet another difference between the <strong>-t/-T</strong> and <strong>-r/-R</strong> is that <strong>-r/-R</strong> checks for
proper overlaps and considers both POS and the end position of an indel, while <strong>-t/-T</strong>
considers the POS coordinate only. Note that <strong>-t</strong> cannot be used in combination with <strong>-T</strong>.</p>
</dd>
<dt class="hdlist1"><strong>-T, --targets-file</strong> [^]<em>FILE</em></dt>
<dd>
<p>Same <strong>-t, --targets</strong>, but reads regions from a file. Note that <strong>-T</strong>
cannot be used in combination with <strong>-t</strong>.</p>
<div class="paragraph">
<p>With the <strong>call -C</strong> <em>alleles</em> command, third column of the targets file must
be comma-separated list of alleles, starting with the reference allele.
Note that the file must be compressed and indexed.
Such a file can be easily created from a VCF using:</p>
</div>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> bcftools query -f'%CHROM\t%POS\t%REF,%ALT\n' file.vcf | bgzip -c > als.tsv.gz && tabix -s1 -b2 -e2 als.tsv.gz</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>--targets-overlap</strong> <em>0</em>|<em>1</em>|<em>2</em></dt>
<dd>
<p>Same as <strong>--regions-overlap</strong> but for <strong>-t/-T</strong>.</p>
</dd>
<dt class="hdlist1"><strong>--threads</strong> <em>INT</em></dt>
<dd>
<p>Use multithreading with <em>INT</em> worker threads. The option is currently used only for the compression of the
output stream, only when <em>--output-type</em> is <em>b</em> or <em>z</em>. Default: 0.</p>
</dd>
</dl>
</div>
</div>
<div class="sect2">
<h3 id="annotate">bcftools annotate <em>[OPTIONS]</em> <em>FILE</em></h3>
<div class="paragraph">
<p>Add or remove annotations.</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-a, --annotations</strong> <em>file</em></dt>
<dd>
<p>Bgzip-compressed and tabix-indexed file with annotations. The file
can be VCF, BED, or a tab-delimited file with mandatory columns CHROM, POS
(or, alternatively, FROM and TO), optional columns REF and ALT, and arbitrary
number of annotation columns. BED files are expected to have
the ".bed" or ".bed.gz" suffix (case-insensitive), otherwise a tab-delimited file is assumed.
Note that in case of tab-delimited file, the coordinates POS, FROM and TO are
one-based and inclusive. When REF and ALT are present, only matching VCF
records will be annotated. If the END coordinate is present in the annotation file
and given on command line as "<code>-c ~INFO/END</code>", then VCF records will be matched also by the INFO/END coordinate.
If ID is present in the annotation file and given as "<code>-c ~ID</code>", then VCF records will be matched
also by the ID column.
 <br>
 <br>
When multiple ALT alleles are present in the annotation file (given as
comma-separated list of alleles), at least one must match one of the
alleles in the corresponding VCF record. Similarly, at least one
alternate allele from a multi-allelic VCF record must be present in the
annotation file.
 <br>
 <br>
Missing values can be added by providing "." in place of actual value
and using the missing value modifier with <strong>-c</strong>, such as ".TAG".
 <br>
 <br>
Note that flag types, such as "INFO/FLAG", can be annotated by including
a field with the value "1" to set the flag, "0" to remove it, or "." to
keep existing flags.
See also <strong>-c, --columns</strong> and <strong>-h, --header-lines</strong>.</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> # Sample annotation file with columns CHROM, POS, STRING_TAG, NUMERIC_TAG
1 752566 SomeString 5
1 798959 SomeOtherString 6</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>--collapse</strong> <em>snps</em>|<em>indels</em>|<em>both</em>|<em>all</em>|<em>some</em>|<em>none</em></dt>
<dd>
<p>Controls how to match records from the annotation file to the target VCF.
Effective only when <strong>-a</strong> is a VCF or BCF.
See <strong><a href="#common_options">Common Options</a></strong> for more.</p>
</dd>
<dt class="hdlist1"><strong>-c, --columns</strong> <em>list</em></dt>
<dd>
<p>Comma-separated list of columns or tags to carry over from the annotation file
(see also <strong>-a, --annotations</strong>). If the annotation file is not a VCF/BCF,
<em>list</em> describes the columns of the annotation file and must include CHROM,
POS (or, alternatively, FROM and TO), and optionally REF and ALT. Unused
columns which should be ignored can be indicated by "-".
 <br>
 <br>
If the annotation file is a VCF/BCF, only the edited columns/tags must be present and their
order does not matter. The columns ID, QUAL, FILTER, INFO and FORMAT
can be edited, where INFO tags can be written both as "INFO/TAG" or simply "TAG",
and FORMAT tags can be written as "FORMAT/TAG" or "FMT/TAG".
The imported VCF annotations can be renamed as "DST_TAG:=SRC_TAG" or "FMT/DST_TAG:=FMT/SRC_TAG".
 <br>
 <br>
To carry over all INFO annotations, use "INFO". To add all INFO annotations except
"TAG", use "^INFO/TAG". By default, existing values are replaced.
 <br>
 <br>
By default, existing tags are overwritten unless the source value is a missing value (i.e. ".").
If also missing values should be carried over (and overwrite existing tags), use ".TAG" instead of "TAG".
To add annotations without overwriting existing values (that is, to add tags that are absent or
to add values to existing tags with missing values), use "+TAG" instead of "TAG". These can be combined,
for example ".+TAG" can be used to add TAG even if the source value is missing but only if TAG does not
exist in the target file; existing tags will not be overwritten.
To append to existing values (rather than replacing or leaving untouched), use "=TAG"
(instead of "TAG" or "+TAG").
To replace only existing values without modifying missing annotations, use "-TAG".
To match the record also by ID or INFO/END, in addition to REF and ALT, use "~ID" or "~INFO/END".
If position needs to be replaced, mark the column with the new position as "~POS".
 <br>
 <br>
If the annotation file is not a VCF/BCF, all new annotations must be
defined via <strong>-h, --header-lines</strong>.
 <br>
 <br>
See also the <strong>-l, --merge-logic</strong> option.</p>
</dd>
<dt class="hdlist1"><strong>-C, --columns-file</strong> <em>file</em></dt>
<dd>
<p>Read the list of columns from a file (normally given via the <strong>-c, --columns</strong> option).
"-" to skip a column of the annotation file.
One column name per row, an additional space- or tab-separated field can
be present to indicate the merge logic (normally given via the <strong>-l, --merge-logic</strong> option).
This is useful when many annotations are added at once.</p>
</dd>
<dt class="hdlist1"><strong>-e, --exclude</strong> <em>EXPRESSION</em></dt>
<dd>
<p>exclude sites for which <em>EXPRESSION</em> is true. For valid expressions see
<strong><a href="#expressions">EXPRESSIONS</a></strong>.</p>
</dd>
<dt class="hdlist1"><strong>--force</strong></dt>
<dd>
<p>continue even when parsing errors, such as undefined tags, are encountered. Note
this can be an unsafe operation and can result in corrupted BCF files. If this
option is used, make sure to sanity check the result thoroughly.</p>
</dd>
<dt class="hdlist1"><strong>-h, --header-lines</strong> <em>file</em></dt>
<dd>
<p>Lines to append to the VCF header, see also <strong>-c, --columns</strong> and <strong>-a, --annotations</strong>. For example:</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> ##INFO=<ID=NUMERIC_TAG,Number=1,Type=Integer,Description="Example header line">
##INFO=<ID=STRING_TAG,Number=1,Type=String,Description="Yet another header line"></pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-I, --set-id</strong> [+]<em>FORMAT</em></dt>
<dd>
<p>assign ID on the fly. The format is the same as in the <strong><a href="#query">query</a></strong>
command (see below). By default all existing IDs are replaced. If the
format string is preceded by "+", only missing IDs will be set. For example,
one can use</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> bcftools annotate --set-id +'%CHROM\_%POS\_%REF\_%FIRST_ALT' file.vcf</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-i, --include</strong> <em>EXPRESSION</em></dt>
<dd>
<p>include only sites for which <em>EXPRESSION</em> is true. For valid expressions see
<strong><a href="#expressions">EXPRESSIONS</a></strong>.</p>
</dd>
<dt class="hdlist1"><strong>-k, --keep-sites</strong></dt>
<dd>
<p>keep sites which do not pass <strong>-i</strong> and <strong>-e</strong> expressions instead of discarding them</p>
</dd>
<dt class="hdlist1"><strong>-l, --merge-logic</strong> <em>tag:first</em>|<em>append</em>|<em>append-missing</em>|<em>unique</em>|<em>sum</em>|<em>avg</em>|<em>min</em>|<em>max</em>[,…​]</dt>
<dd>
<p>When multiple regions overlap a single record, this option defines how to treat multiple
annotation values when setting <em>tag</em> in the destination file: use the first encountered value ignoring
the rest (<em>first</em>); append allowing duplicates (<em>append</em>); append even if the appended value is missing,
i.e. is a dot (<em>append-missing</em>); append discarding duplicate values (<em>unique</em>);
sum the values (<em>sum</em>, numeric fields only); average the values (<em>avg</em>); use the minimum value (<em>min</em>) or
the maximum (<em>max</em>).
+
Note that this option is intended for use with BED or TAB-delimited annotation files only. Moreover,
it is effective only when either <em>REF</em> and <em>ALT</em> or <em>BEG</em> and <em>END</em> <strong>--columns</strong> are present .
+
Multiple rules can be given either as a comma-separated list or giving the option multiple times.
This is an experimental feature.</p>
</dd>
<dt class="hdlist1"><strong>-m, --mark-sites</strong> <em class="+-">TAG</em></dt>
<dd>
<p>annotate sites which are present ("+") or absent ("-") in the <strong>-a</strong> file with a new INFO/TAG flag</p>
</dd>
<dt class="hdlist1"><strong>--no-version</strong></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-o, --output</strong> <em>FILE</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-O, --output-type</strong> <em>b</em>|<em>u</em>|<em>z</em>|<em>v</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-r, --regions</strong> <em>chr</em>|<em>chr:pos</em>|<em>chr:from-to</em>|<em>chr:from-</em>[,…​]</dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-R, --regions-file</strong> <em>file</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>--rename-annots</strong> <em>file</em></dt>
<dd>
<p>rename annotations according to the map in <em>file</em>, with
"old_name new_name\n" pairs separated by whitespaces, each on a separate
line. The old name must be prefixed with the annotation type:
INFO, FORMAT, or FILTER.</p>
</dd>
<dt class="hdlist1"><strong>--rename-chrs</strong> <em>file</em></dt>
<dd>
<p>rename chromosomes according to the map in <em>file</em>, with
"old_name new_name\n" pairs separated by whitespaces, each on a separate
line.</p>
</dd>
<dt class="hdlist1"><strong>-s, --samples</strong> [^]<em>LIST</em></dt>
<dd>
<p>subset of samples to annotate, see also <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-S, --samples-file</strong> <em>FILE</em></dt>
<dd>
<p>subset of samples to annotate. If the samples are named differently in the
target VCF and the <strong>-a, --annotations</strong> VCF, the name mapping can be
given as "src_name dst_name\n", separated by whitespaces, each pair on a
separate line.</p>
</dd>
<dt class="hdlist1"><strong>--single-overlaps</strong></dt>
<dd>
<p>use this option to keep memory requirements low with very large annotation
files. Note, however, that this comes at a cost, only single overlapping intervals
are considered in this mode. This was the default mode until the commit
af6f0c9 (Feb 24 2019).</p>
</dd>
<dt class="hdlist1"><strong>--threads</strong> <em>INT</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-x, --remove</strong> <em>list</em></dt>
<dd>
<p>List of annotations to remove. Use "FILTER" to remove all filters or
"FILTER/SomeFilter" to remove a specific filter. Similarly, "INFO" can
be used to remove all INFO tags and "FORMAT" to remove all FORMAT tags
except GT. To remove all INFO tags except "FOO" and "BAR", use
"^INFO/FOO,INFO/BAR" (and similarly for FORMAT and FILTER).
"INFO" can be abbreviated to "INF" and "FORMAT" to "FMT".</p>
</dd>
</dl>
</div>
<div class="paragraph">
<p><strong>Examples:</strong></p>
</div>
<div class="listingblock">
<div class="content">
<pre> # Remove three fields
bcftools annotate -x ID,INFO/DP,FORMAT/DP file.vcf.gz
# Remove all INFO fields and all FORMAT fields except for GT and PL
bcftools annotate -x INFO,^FORMAT/GT,FORMAT/PL file.vcf
# Add ID, QUAL and INFO/TAG, not replacing TAG if already present
bcftools annotate -a src.bcf -c ID,QUAL,+TAG dst.bcf
# Carry over all INFO and FORMAT annotations except FORMAT/GT
bcftools annotate -a src.bcf -c INFO,^FORMAT/GT dst.bcf
# Annotate from a tab-delimited file with six columns (the fifth is ignored),
# first indexing with tabix. The coordinates are 1-based.
tabix -s1 -b2 -e2 annots.tab.gz
bcftools annotate -a annots.tab.gz -h annots.hdr -c CHROM,POS,REF,ALT,-,TAG file.vcf
# Annotate from a tab-delimited file with regions (1-based coordinates, inclusive)
tabix -s1 -b2 -e3 annots.tab.gz
bcftools annotate -a annots.tab.gz -h annots.hdr -c CHROM,FROM,TO,TAG input.vcf
# Annotate from a bed file (0-based coordinates, half-closed, half-open intervals)
bcftools annotate -a annots.bed.gz -h annots.hdr -c CHROM,FROM,TO,TAG input.vcf
# Transfer the INFO/END tag, matching by POS,REF,ALT and ID. This example assumes
# that INFO/END is already present in the VCF header.
bcftools annotate -a annots.tab.gz -c CHROM,POS,~ID,REF,ALT,INFO/END input.vcf
# For more examples see http://samtools.github.io/bcftools/howtos/annotate.html</pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="call">bcftools call <em>[OPTIONS]</em> <em>FILE</em></h3>
<div class="paragraph">
<p>This command replaces the former <strong>bcftools view</strong> caller. Some of the original
functionality has been temporarily lost in the process of transition under
<a href="http://github.com/samtools/htslib">htslib</a>, but will be added back on popular
demand. The original calling model can be invoked with the <strong>-c</strong> option.</p>
</div>
<div class="sect3">
<h4 id="_file_format_options">File format options:</h4>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>--no-version</strong></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-o, --output</strong> <em>FILE</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-O, --output-type</strong> <em>b</em>|<em>u</em>|<em>z</em>|<em>v</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>--ploidy</strong> <em>ASSEMBLY</em>[<em>?</em>]<a id="ploidy"></a></dt>
<dd>
<p>predefined ploidy, use <em>list</em> (or any other unused word) to print a list
of all predefined assemblies. Append a question mark to print the actual
definition. See also <strong>--ploidy-file</strong>.</p>
</dd>
<dt class="hdlist1"><strong>--ploidy-file</strong> <em>FILE</em></dt>
<dd>
<p>ploidy definition given as a space/tab-delimited list of
CHROM, FROM, TO, SEX, PLOIDY. The SEX codes are arbitrary and
correspond to the ones used by <strong><a href="#samples_file">--samples-file</a></strong>.
The default ploidy can be given using the starred records (see
below), unlisted regions have ploidy 2. The default ploidy definition is</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> X 1 60000 M 1
X 2699521 154931043 M 1
Y 1 59373566 M 1
Y 1 59373566 F 0
MT 1 16569 M 1
MT 1 16569 F 1
* * * M 2
* * * F 2</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-r, --regions</strong> <em>chr</em>|<em>chr:pos</em>|<em>chr:from-to</em>|<em>chr:from-</em>[,…​]</dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-R, --regions-file</strong> <em>file</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-s, --samples</strong> <em>LIST</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-S, --samples-file</strong> <em>FILE</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-t, --targets</strong> <em>LIST</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-T, --targets-file</strong> <em>FILE</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>--threads</strong> <em>INT</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
</dl>
</div>
</div>
<div class="sect3">
<h4 id="_inputoutput_options">Input/output options:</h4>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-A, --keep-alts</strong></dt>
<dd>
<p>output all alternate alleles present in the alignments even if they do not
appear in any of the genotypes</p>
</dd>
<dt class="hdlist1"><strong>-f, --format-fields</strong> <em>list</em></dt>
<dd>
<p>comma-separated list of FORMAT fields to output for each sample. Currently
GQ and GP fields are supported. For convenience, the fields can be given
as lower case letters. Prefixed with "^" indicates a request for tag
removal of auxiliary tags useful only for calling.</p>
</dd>
<dt class="hdlist1"><strong>-F, --prior-freqs</strong> <em>AN</em>,<em>AC</em></dt>
<dd>
<p>take advantage of prior knowledge of population allele frequencies. The
workflow looks like this:</p>
</dd>
</dl>
</div>
<div class="listingblock">
<div class="content">
<pre> # Extract AN,AC values from an existing VCF, such 1000Genomes
bcftools query -f'%CHROM\t%POS\t%REF\t%ALT\t%AN\t%AC\n' 1000Genomes.bcf | bgzip -c > AFs.tab.gz
# If the tags AN,AC are not already present, use the +fill-tags plugin
bcftools +fill-tags 1000Genomes.bcf | bcftools query -f'%CHROM\t%POS\t%REF\t%ALT\t%AN\t%AC\n' | bgzip -c > AFs.tab.gz
tabix -s1 -b2 -e2 AFs.tab.gz
# Create a VCF header description, here we name the tags REF_AN,REF_AC
cat AFs.hdr
##INFO=<ID=REF_AN,Number=1,Type=Integer,Description="Total number of alleles in reference genotypes">
##INFO=<ID=REF_AC,Number=A,Type=Integer,Description="Allele count in reference genotypes for each ALT allele">
# Now before calling, stream the raw mpileup output through `bcftools annotate` to add the frequencies
bcftools mpileup [...] -Ou | bcftools annotate -a AFs.tab.gz -h AFs.hdr -c CHROM,POS,REF,ALT,REF_AN,REF_AC -Ou | bcftools call -mv -F REF_AN,REF_AC [...]</pre>
</div>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-G, --group-samples</strong> <em class="TAG:">FILE</em>|<em>-</em></dt>
<dd>
<p>by default, all samples are assumed to come from a single population. This option allows to group samples
into populations and apply the HWE assumption within but not across the populations. <em>FILE</em> is a tab-delimited
text file with sample names in the first column and group names in the second column. If <em>-</em> is
given instead, no HWE assumption is made at all and single-sample calling is performed. (Note that
in low coverage data this inflates the rate of false positives.) The <strong>-G</strong> option requires the presence of
per-sample FORMAT/QS or FORMAT/AD tag generated with <strong>bcftools mpileup -a QS</strong> (or <strong>-a AD</strong>).</p>
</dd>
<dt class="hdlist1"><strong>-g, --gvcf</strong> <em>INT</em></dt>
<dd>
<p>output also gVCF blocks of homozygous REF calls. The parameter <em>INT</em> is the
minimum per-sample depth required to include a site in the non-variant
block.</p>
</dd>
<dt class="hdlist1"><strong>-i, --insert-missed</strong> <em>INT</em></dt>
<dd>
<p>output also sites missed by mpileup but present in <strong>-T, --targets-file</strong>.</p>
</dd>
<dt class="hdlist1"><strong>-M, --keep-masked-ref</strong></dt>
<dd>
<p>output sites where REF allele is N</p>
</dd>
<dt class="hdlist1"><strong>-V, --skip-variants</strong> <em>snps</em>|<em>indels</em></dt>
<dd>
<p>skip indel/SNP sites</p>
</dd>
<dt class="hdlist1"><strong>-v, --variants-only</strong></dt>
<dd>
<p>output variant sites only</p>
</dd>
</dl>
</div>
</div>
<div class="sect3">
<h4 id="_consensusvariant_calling_options">Consensus/variant calling options:</h4>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-c, --consensus-caller</strong></dt>
<dd>
<p>the original <strong>samtools</strong>/<strong>bcftools</strong> calling method (conflicts with <strong>-m</strong>)</p>
</dd>
<dt class="hdlist1"><strong>-C, --constrain</strong> <em>alleles</em>|<em>trio</em></dt>
<dd>
<div class="dlist">
<dl>
<dt class="hdlist1"><em>alleles</em></dt>
<dd>
<p>call genotypes given alleles. See also <strong>-T, --targets-file</strong>.</p>
</dd>
<dt class="hdlist1"><em>trio</em></dt>
<dd>
<p>call genotypes given the father-mother-child constraint. See also
<strong>-s, --samples</strong> and <strong>-n, --novel-rate</strong>.</p>
</dd>
</dl>
</div>
</dd>
<dt class="hdlist1"><strong>-m, --multiallelic-caller</strong></dt>
<dd>
<p>alternative model for multiallelic and rare-variant calling designed to
overcome known limitations in <strong>-c</strong> calling model (conflicts with <strong>-c</strong>)</p>
</dd>
<dt class="hdlist1"><strong>-n, --novel-rate</strong> <em>float</em>[,…​]</dt>
<dd>
<p>likelihood of novel mutation for constrained <strong>-C</strong> <em>trio</em> calling. The trio
genotype calling maximizes likelihood of a particular combination of
genotypes for father, mother and the child
P(F=i,M=j,C=k) = P(unconstrained) * Pn + P(constrained) * (1-Pn).
By providing three values, the mutation rate Pn is set explicitly for SNPs,
deletions and insertions, respectively. If two values are given, the first
is interpreted as the mutation rate of SNPs and the second is used to
calculate the mutation rate of indels according to their length as
Pn=<em>float</em>*exp(-a-b*len), where a=22.8689, b=0.2994 for insertions and
a=21.9313, b=0.2856 for deletions [pubmed:23975140]. If only one value is
given, the same mutation rate Pn is used for SNPs and indels.</p>
</dd>
<dt class="hdlist1"><strong>-p, --pval-threshold</strong> <em>float</em></dt>
<dd>
<p>with <strong>-c</strong>, accept variant if P(ref|D) < <em>float</em>.</p>
</dd>
<dt class="hdlist1"><strong>-P, --prior</strong> <em>float</em></dt>
<dd>
<p>expected substitution rate, or 0 to disable the prior. Only with <strong>-m</strong>.</p>
</dd>
<dt class="hdlist1"><strong>-t, --targets</strong> <em>file</em>|<em>chr</em>|<em>chr:pos</em>|<em>chr:from-to</em>|<em>chr:from-</em>[,…​]</dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-X, --chromosome-X</strong></dt>
<dd>
<p>haploid output for male samples (requires PED file with <strong>-s</strong>)</p>
</dd>
<dt class="hdlist1"><strong>-Y, --chromosome-Y</strong></dt>
<dd>
<p>haploid output for males and skips females (requires PED file with <strong>-s</strong>)</p>
</dd>
</dl>
</div>
</div>
</div>
<div class="sect2">
<h3 id="cnv">bcftools cnv <em>[OPTIONS]</em> <em>FILE</em></h3>
<div class="paragraph">
<p>Copy number variation caller, requires a VCF annotated with the Illumina’s
B-allele frequency (BAF) and Log R Ratio intensity (LRR) values. The HMM
considers the following copy number states: CN 2 (normal), 1 (single-copy
loss), 0 (complete loss), 3 (single-copy gain).</p>
</div>
<div class="sect3">
<h4 id="_general_options">General Options:</h4>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-c, --control-sample</strong> <em>string</em></dt>
<dd>
<p>optional control sample name. If given, pairwise calling is performed
and the <strong>-P</strong> option can be used</p>
</dd>
<dt class="hdlist1"><strong>-f, --AF-file</strong> <em>file</em></dt>
<dd>
<p>read allele frequencies from a tab-delimited file with the columns CHR,POS,REF,ALT,AF</p>
</dd>
<dt class="hdlist1"><strong>-o, --output-dir</strong> <em>path</em></dt>
<dd>
<p>output directory</p>
</dd>
<dt class="hdlist1"><strong>-p, --plot-threshold</strong> <em>float</em></dt>
<dd>
<p>call <strong>matplotlib</strong> to produce plots for chromosomes with quality at least <em>float</em>,
useful for visual inspection of the calls. With <strong>-p 0</strong>, plots for all chromosomes will be
generated. If not given, a <strong>matplotlib</strong> script will be created but not called.</p>
</dd>
<dt class="hdlist1"><strong>-r, --regions</strong> <em>chr</em>|<em>chr:pos</em>|<em>chr:from-to</em>|<em>chr:from-</em>[,…​]</dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-R, --regions-file</strong> <em>file</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-s, --query-sample</strong> <em>string</em></dt>
<dd>
<p>query sample name</p>
</dd>
<dt class="hdlist1"><strong>-t, --targets</strong> <em>LIST</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
<dt class="hdlist1"><strong>-T, --targets-file</strong> <em>FILE</em></dt>
<dd>
<p>see <strong><a href="#common_options">Common Options</a></strong></p>
</dd>
</dl>
</div>
</div>
<div class="sect3">
<h4 id="_hmm_options">HMM Options:</h4>
<div class="dlist">
<dl>
<dt class="hdlist1"><strong>-a, --aberrant</strong> <em>float</em>[,<em>float</em>]</dt>
<dd>
<p>fraction of aberrant cells in query and control. The hallmark of
duplications and contaminations is the BAF value of heterozygous markers
which is dependent on the fraction of aberrant cells. Sensitivity to
smaller fractions of cells can be increased by setting <strong>-a</strong> to a lower value. Note
however, that this comes at the cost of increased false discovery rate.</p>
</dd>
<dt class="hdlist1"><strong>-b, --BAF-weight</strong> <em>float</em></dt>
<dd>
<p>relative contribution from BAF</p>
</dd>
<dt class="hdlist1"><strong>-d, --BAF-dev</strong> <em>float</em>[,<em>float</em>]</dt>
<dd>
<p>expected BAF deviation in query and control, i.e. the noise observed
in the data.</p>
</dd>
<dt class="hdlist1"><strong>-e, --err-prob</strong> <em>float</em></dt>
<dd>
<p>uniform error probability</p>
</dd>
<dt class="hdlist1"><strong>-l, --LRR-weight</strong> <em>float</em></dt>
<dd>
<p>relative contribution from LRR. With noisy data, this option can have big effect
on the number of calls produced. In truly random noise (such as in simulated data),
the value should be set high (1.0), but in the presence of systematic noise
when LRR are not informative, lower values result in cleaner calls (0.2).</p>
</dd>