Releases: mgymrek/lobstr-code
Releases · mgymrek/lobstr-code
v4.0.6
Since 4.0.0:
- Long-awaited fix handling the case when read group IDs are replicated across BAM files input to
allelotype
. allelotype
now recognizes either_.bai
or_.bam.bai
BAM index files.- Added option
--dont-include-pl
toallelotype
, which creates VCFs with no PL field, greatly reducing their size. - Added option
--gridk
toallelotype
, which controls how many possible alleles are considered when computing genotype likelihoods. - Added VCF fields PQ and DPA.
- Bug fix for precision error leading to low quality scores for high coverage heterozygous sites.
Fix bug in quality scores for high coverage sites
Intermediate bug fix release.
v4.0.4
v4.0.0 (beta)
The major change for this version is the ability for allelotype
to take in BAM files from external aligners, mainly from BWA-MEM. This allows STR genotyping across large panels of samples that already have existing alignments for only a fraction of the computational cost of running the whole lobSTR pipeline.
v3.0.3
Minor fixes since v3.0.2:
- Changed copyright dates
- Cleaned up python scripts
- Add check to allelotyper to test whether period is in range
- Scripts to install test reference and lobSTR hg19 reference
- Checks in lobstr_index.py to make sure required binaries are installed
v3.0.2
v2.0.8
v2.0.7
v2.0.5, small fixes
This release contains mostly small fixes, and importantly updates how we package releases so that binaries should now be statically linked.