Service note: Geraldine is on vacation this week; other members of GSA will be responding to questions, but they have a lot of work besides this, so be aware that responses may be a little slower than usual. Thank you for your patience.

UnifiedGenotyper queue extension

Johan_DahlbergJohan_Dahlberg Posts: 36Member

It says in the "ExampleUnifiedGenotyper" qscript that it runs an incomplete version of the UnifiedGenotyper. I have a two questions about this.

  • I cannot find the org.broadinstitute.sting.queue.extensions.gatk.UnifiedGenotyper class, is this not in the public source or am I blind?
  • Does the "incomplete" in the script starting comment mean that this extension is incomplete in its functionality? Or is it something else that is incomplete in its nature?

Basically I'm wondering if there are any pitfalls for me if I start using the example script as a base for my own variant calling qscript.

Post edited by Johan_Dahlberg on

Best Answer

  • kshakirkshakir Posts: 3 mod
    Answer ✓

    Most of the queue.extensions are generated classes once you run 'ant'. The generated classes are Queue compatible versions of the walker command arguments. Instead of looking at the generated scala file you can find the same or better argument descriptions in the the gatkdocs for each walker.

    The 'incomplete' status of the script means that it is only a technical example, and will need to be tweaked for your specific requirements in your calling pipeline. Feel free to explore different command line options with the UG. For example using Queue you can create two instances of the UG and test using with BAQ and without. As for what UG commands you should be using, see the UG gatkdocs and the Best Practices for an overall description of where the UG fits in a calling pipeline.

Answers

Sign In or Register to comment.