ebanks d5ab002449 Curiously, it seems I never set the default base quality used by the Genotyper to 10. It's done now. ... git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@2546 348d0f76-0448-11de-a6fe-93d51630548a		2010-01-08 06:02:01 +00:00
..
annotator	-UG's call into VariantAnnotator now uses the full alignment context (as opposed to the filtered one)	2010-01-08 05:40:42 +00:00
concordance	Check for division by 0 in annotations	2010-01-07 19:27:15 +00:00
fasta	moved hard-coded file paths to the oneKGLocation, validationDataLocation, and seqLocation variables setup in the BaseTest.	2009-12-29 07:40:48 +00:00
filters	moved hard-coded file paths to the oneKGLocation, validationDataLocation, and seqLocation variables setup in the BaseTest.	2009-12-29 07:40:48 +00:00
genotyper	Curiously, it seems I never set the default base quality used by the Genotyper to 10. It's done now.	2010-01-08 06:02:01 +00:00
indels	moved hard-coded file paths to the oneKGLocation, validationDataLocation, and seqLocation variables setup in the BaseTest.	2009-12-29 07:40:48 +00:00
recalibration	Tile is now a standard covariate. By default the TileCovariate returns -1 if tile can't be derived from the read's name. Added a new command line option -throwTileException which will force TileCovariate to throw an exception if tile can't be derived for a read. Singleton covariates, such as any read group without tile info, must be skipped over in TableRecalibration so that the sequential formulation doesn't apply the same correction more than once. TileCovariate class has been added to the Early Access package.	2010-01-07 22:51:41 +00:00
DepthOfCoverageIntegrationTest.java	moved hard-coded file paths to the oneKGLocation, validationDataLocation, and seqLocation variables setup in the BaseTest.	2009-12-29 07:40:48 +00:00
PileupWalkerIntegrationTest.java	Now that we changed how deletions are represented, got to update MD5...	2009-12-30 22:00:58 +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