@@ -93,7 +93,6 @@ Luckily, if you have access to https:// on port 443, then you can use this
## Compilation
FreeBayes requires g++ and the standard C and C++ development libraries.
Additionally, cmake is required for building the BamTools API.
make
@@ -106,6 +105,12 @@ accomplished via
sudo make install
Note that the freebayes-parallel script and the programs on which it depends are
not installed by this command.
Users can optionally build with [BamTools](https://github.com/pezmaster31/bamtools) instead of [SeqLib](https://github.com/walaj/SeqLib). Building with BamTools requires CMake.
make wbamtools
## Usage
@@ -179,7 +184,7 @@ Note that any of the above examples can be made parallel by using the
scripts/freebayes-parallel script. If you find freebayes to be slow, you
should probably be running it in parallel using this script to run on a single
host, or generating a series of scripts, one per region, and run them on a
cluster.
cluster. Be aware that the freebayes-parallel script contains calls to other programs using relative paths from the scripts subdirectory; the easiest way to ensure a successful run is to invoke the freebayes-parallel script from within the scripts subdirectory.
## Calling variants: from fastq to VCF
@@ -404,7 +409,7 @@ As freebayes is haplotype-based, left-alignment is necessary only for the
determination of candidate polymorphic loci. Once such loci are determined,
haplotype observations are extracted from reads where:
1. putative variants lie within `--haplotype-window` bases of each other
1. putative variants lie within `--haplotype-length` bases of each other
(default 3bp),
2. the reference sequence has repeats (e.g. microsatellites or STRs are called
as one haplotype),
@@ -444,7 +449,7 @@ detection window. We can then use these as "basis alleles" for the observation
of haplotypes, considering all other putative variants supported by the