Mark DePristo 251983b8fb Add GATK-wide command line argument to control the maximum runtime allowed for the GATK ... -- Providing this optional argument -maxRuntime (in -maxRuntimeUnits units) causes the GATK to exit gracefully when the max. runtime has been exceeded. By cleanly I mean that the engine simply stops at the next available cycle in the walker as through the end of processing had been reached. This means that all output files are closed properly, etc. -- Emits an info message that looks like "INFO 10:36:52,723 MicroScheduler - Aborting execution (cleanly) because the runtime has exceeded the requested maximum 10.0000 s". Otherwise there's currently no way to differentiate a truly completed run from a timelimit exceeded run, which may be a useful thing for a future update -- Resolves GSA-630 / GATK max runtime to deal with bad LSA calling? -- Added new JIRA entry for Ami to restart chr1 macarthur with this argument set to -maxRuntime 1 -maxRuntimeUnits DAYS to see if we can do all of chr1 in one weekend.		2012-10-26 13:18:34 -04:00
..
net/sf	Cleanup of VCF header lines and constants, BCF2 bugfixes	2012-06-21 15:16:31 -04:00
org/broadinstitute/sting	Add GATK-wide command line argument to control the maximum runtime allowed for the GATK	2012-10-26 13:18:34 -04:00