ebanks bf935a6ab1 1. Fixed bug in PrimaryBaseSecondaryBaseSymmetry code (not checking for null before trying to access object's methods) which was causing Integration Tests to fail. ... 2. Retired allele frequency range from UG, which wasn't very useful. git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@2113 348d0f76-0448-11de-a6fe-93d51630548a		2009-11-23 01:31:48 +00:00
..
annotator	Fixed the sample mix-up bug Kiran discovered, and added a unit test in the VCF reader class (Thanks for the good example files Kiran). Also renamed the toStringRepresentation function to toStringEncoding, and added a matching method in VCFGenotypeRecord.	2009-11-19 18:17:47 +00:00
concordance	Fixed the sample mix-up bug Kiran discovered, and added a unit test in the VCF reader class (Thanks for the good example files Kiran). Also renamed the toStringRepresentation function to toStringEncoding, and added a matching method in VCFGenotypeRecord.	2009-11-19 18:17:47 +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
genotyper	1. Fixed bug in PrimaryBaseSecondaryBaseSymmetry code (not checking for null before trying to access object's methods) which was causing Integration Tests to fail.	2009-11-23 01:31:48 +00:00
indels	Another case of reordering of read groups blowing up checksums.	2009-11-13 00:07:35 +00:00
recalibration	Added the old recalibrator integration tests to the refactored recalibrator sitting in playground.	2009-11-19 22:43:28 +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