gatk-3.8/java/test/org/broadinstitute/sting
kiran ecbc38aff0 If no comp rod is specified, specify the dummy name none so that we still get counts.
git-svn-id: file:///humgen/gsa-scr1/gsa-engineering/svn_contents/trunk@5211 348d0f76-0448-11de-a6fe-93d51630548a
2011-02-07 19:24:52 +00:00
..
alignment Quick fix for Danny Lieber: flesh out the additional functionality required 2011-01-31 05:28:37 +00:00
commandline Fixed long-standing bug reported by Mauricio where @Arguments assigned to 2011-01-12 22:18:24 +00:00
datasources/pipeline Changing testing framework from junit -> testng, for its enhanced configurability. 2010-11-01 21:31:44 +00:00
gatk If no comp rod is specified, specify the dummy name none so that we still get counts. 2011-02-07 19:24:52 +00:00
jna If there's an LSF queue maximum time limit set and the user hasn't specified one for this job, pass on the queue defined maximum limit with the job. 2011-01-31 23:13:09 +00:00
oneoffprojects/walkers Changing testing framework from junit -> testng, for its enhanced configurability. 2010-11-01 21:31:44 +00:00
playground/gatk/walkers Committing the fragment-based calling code. Results look great in all datasets (will show this at 1000G this week with Ryan). Note that this is an intermediate commit. The code needs to be cleaned up and the fragmentation code needs to be moved up into LocusIteratorByState. This should all happen later this week, but I don't want Ryan to have to keep running from my own personal Sting directory. The current crappy implementation adds ~10% to the runtime, but that should all go away in the next iteration. 2011-01-23 05:04:17 +00:00
utils Oops, old local paths committed on accident. 2011-02-04 23:35:56 +00:00
BaseTest.java If there's an LSF queue maximum time limit set and the user hasn't specified one for this job, pass on the queue defined maximum limit with the job. 2011-01-31 23:13:09 +00:00
StingTextReporter.java Cleanup testng listener configuration. 2010-11-15 23:43:14 +00:00
WalkerTest.java More testng fallout: fixing another seemingly 'random' issue arising from an 2011-02-01 15:25:50 +00:00