The current GATK version is 3.7-0
Examples: Monday, today, last week, Mar 26, 3/26/04

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Powered by Vanilla. Made with Bootstrap.
GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.
Register now for the upcoming GATK Best Practices workshop, Feb 20-22 in Leuven, Belgium. Open to all comers! More info and signup at http://bit.ly/2i4mGxz

DepthOfCoverage multi-threading

tommycarstensentommycarstensen United KingdomMember Posts: 404 ✭✭✭

Does the walker DepthOfCoverage support multi-threading?

According to the documentation:
http://www.broadinstitute.org/gatk/gatkdocs/org_broadinstitute_sting_gatk_walkers_coverage_DepthOfCoverage.html
"This tool can be run in multi-threaded mode using this option. TreeReducible (-nt)"

When I try with GATK2.5 I get this error message:
"Invalid command line: Argument nt has a bad value: The analysis DepthOfCoverage aggregates results by interval. Due to a current limitation of the GATK, analyses of this type do not currently support parallel execution. Please run your analysis without the -nt option."

Would it work, if I upgraded to 2.7? You upgrade GATK more frequently than I change my under wear, so it is difficult to keep up :) Thanks!

Tagged:

Best Answer

  • Geraldine_VdAuweraGeraldine_VdAuwera Administrator, Dev Posts: 11,127 admin
    Accepted Answer

    Hi Tommy,

    If you don't mind I'll refrain from commenting on your personal hygiene and sartorial habits :)

    But as regards to the issue you're running into: it's not really a version problem. What's happening here is that by default the DoC is set to generate stats averaged over intervals, which is not compatible with multithreading mode. If you pass the --omitIntervalStatistics / -omitIntervals flag this will be disabled and multithreading ability will be restored. We'll look at documenting and/or putting in a workaround to avoid this situation in the future.

    Geraldine Van der Auwera, PhD

Answers

  • Geraldine_VdAuweraGeraldine_VdAuwera Administrator, Dev Posts: 11,127 admin
    Accepted Answer

    Hi Tommy,

    If you don't mind I'll refrain from commenting on your personal hygiene and sartorial habits :)

    But as regards to the issue you're running into: it's not really a version problem. What's happening here is that by default the DoC is set to generate stats averaged over intervals, which is not compatible with multithreading mode. If you pass the --omitIntervalStatistics / -omitIntervals flag this will be disabled and multithreading ability will be restored. We'll look at documenting and/or putting in a workaround to avoid this situation in the future.

    Geraldine Van der Auwera, PhD

  • tommycarstensentommycarstensen United KingdomMember Posts: 404 ✭✭✭

    Thank you! I actually prefer getting an error message instead of occupying multiple processors for a single core job.

Sign In or Register to comment.