ebanks 6a37090529 Output changes for VCF and UG: ... 1. Don't cap q-scores at 99 2. Scale SLOD to allow more resolution in the output 3. UG outputs weighted allele balance (AB) and on-off genotype (OO) info fields for het genotype calls (works for joint estimation model and SSG) git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@2011 348d0f76-0448-11de-a6fe-93d51630548a		2009-11-10 16:31:31 +00:00
..
concordance	Based on feedback from Kiran, we know uniquify sample names as sample.rodName (instead of sample.1, sample.2, ...)	2009-11-10 02:41:37 +00:00
fasta	a fix for a bug Andrey discovered: in read-based interval traversals we're dupplicating reads in rare cases. The problem was that to accomidate a bug in SAM JDK indexing, we were forced to add one to the stop of our QueryOverlapping() calls to ensure we always got all of the overlapping reads.	2009-11-05 05:26:33 +00:00
filters	VariantFilteration now accepts a VCF rod in addition to an input geli. It will then annotate this VCF file with filtering information in the INFO field too. --OnlyAnnotate will not write in filtering output	2009-11-10 13:24:58 +00:00
genotyper	Output changes for VCF and UG:	2009-11-10 16:31:31 +00:00
indels	Rev'ing Picard, which includes the update to get all the reads in the query region (GSA-173). With it come a bunch of fixes, including retiring the FourBaseRecaller code, and updated md5 for some walker tests.	2009-09-30 20:37:59 +00:00
recalibration	Rev'ing Picard, which includes the update to get all the reads in the query region (GSA-173). With it come a bunch of fixes, including retiring the FourBaseRecaller code, and updated md5 for some walker tests.	2009-09-30 20:37:59 +00:00
DepthOfCoverageIntegrationTest.java	bug fixes to LIBS and LIBH following ultra-aggressive regression testing across 454, solid, and solexa	2009-09-09 15:36:12 +00:00
PrintReadsWalkerTest.java	A big fix for MergingSamRecordIterator, where we weren't correctly handling the comparisons of SAMRecords correctly (we weren't applying the new reference index first, so sometimes the MT contig would be ID 23, sometimes 24 in different records).	2009-10-02 19:35:35 +00:00