We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.
If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!
Test-drive the GATK tools and Best Practices pipelines on Terra
Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.
Introducing a new forum support policy
Hello! My name is Tiffany; I manage the frontline team that supports GATK and some other software and services developed by the Data Sciences Platform (DSP) at the Broad, like Terra, FireCloud, and WDL. Our team's mission is to provide high-quality support to everyone who uses our tools, with the ultimate goal of enabling all of you to use them effectively. In practice that means we answer your questions on the forum, we develop and maintain many of the resource workspaces in Terra, and we work closely with the DSP User Education team members who write documentation and develop materials for workshops. (We love meeting forum members in person at workshops!)
I wanted to let you know that we're rolling out a new support policy for GATK, and I'd like to explain where this is coming from.
We've been facing a mounting challenge over the past few years: the amount of GATK support requests we get is starting to exceed our capacity, mainly because the scope of the GATK and the size of its user community have both expanded substantially over time.
To put things into perspective, the GATK forum was launched in 2012 to a few hundred users.
The first blog post, dated July 2012, was the release notes for GATK 2.0, in which HaplotypeCaller was introduced as a “New tool”. Crazy, right? (Please, nobody mention ReduceReads, or Geraldine will start crying). Since then, GATK has gone from covering a single primary use case (germline short variants, involving about 10 main tools) to an assortment of pipelines that covers all germline and somatic variant classes (including copy number and structural variation) plus several side uses like mitochondrial variants. Meanwhile, we estimate that at least 60,000 people use or have used the GATK, with about 2,000 new people joining the community every quarter.
As a result, we are seeing on average seventy-two questions a week, often with spikes of even higher numbers following new GATK releases. Here is some data from five weeks this past summer; each bar is a week, with the colors showing the breakdown of questions per day.
During this whole time, we've had just one person dedicated full-time to answering forum questions. It used to be Geraldine, then Sheila, and now it's Bhanu, who has been doing a heroic job since she joined us last year. But today, the volume of incoming requests (and in many cases, the rising level of complexity of the questions) is simply too great for a single person to address, even with occasional reinforcements from others on our team.
We are deeply humbled by the fact that so many people are using GATK, and there is nothing our little frontline team cares about more than providing the best support that we possibly can. So we looked at what we could do to deliver the highest level of quality and service given the constraints we're operating under.
So far, we’ve been focused on addressing all questions as quickly as possible. That might sound great in principle, but the downside is that we're spending time on questions that are either already addressed in the documentation (though the answers are not always easy to find) or pertain to unsupported use cases that take a lot of digging and may not even be answerable without some analysis work. Meanwhile, we're not prioritizing questions (or bug reports) that have a disproportionately high impact (either in terms of severity, urgency or number of people affected). Yet we feel that the research community as a whole would be better served if we were to prioritize those problems. That's why we decided to develop a new support policy that sets some clear priorities and spells out more explicitly what we are able to support versus what we will leave to the community to discuss and hopefully resolve.
In my next blog post, I'll explain a bit more how this will work in practice, to set clear expectations so no one feels left in the lurch. In the meantime, let me know if you have any concerns; I'm open to tweaking the policy as needed so I'd love to get your feedback as we roll this out.
Thanks for reading and being a part of this community!