This project is in an early stage of development. It is subject to change without warning. Do not use this code for production work.
GATK 4 (codename Hellbender)
The public parts of the next generation of GATK/Picard methods engine and tools.
This project is in a pre-alpha development stage and is not yet ready for general use.
If you are looking for the current version of GATK to use in production work, please see the GATK website, where you can download a precompiled executable, read documentation, ask questions and receive technical support.
The git-lfs plugin. Run
git lfs initafter installing, followed by
git lfs pullto download the large files. We recommend v0.6.0 but newer versions may also work.
To build and run all tests, run
gradle check. Test report is in
To only build, run
To run all tests, run
What will happen depends on the value of the
CLOUD environment variable: if it's
false or unset then only local tests are run. If it's
mandatory then it'll run only the cloud tests.
To run a single test class, run something like this,
gradle test -Dtest.single=ReadUtilsUnitTest.
To run tests and compute coverage reports, run
gradle jacocoTestReport. The report is then in
build/reports/jacoco/test/html/index.html. (IntelliJ 14 has a good coverage tool that is preferable for development).
To run the main program, run
Note: for faster gradle operations, add
org.gradle.daemon=true to your
~/.gradle/gradle.properties file. This will keep a gradle daemon running in the background and avoid the ~6s gradle start up time on every command.
General guidelines for Hellbender developers
Do not put private or restricted data into the repo.
Try to keep datafiles under 100kb in size. Larger test files should go into
src/test/resources/large, and must be
git lfsby running
git lfs track <file>on each new large file before commit.
Hellbender is BSD licensed. The license is in the top level LICENSE.TXT file. Do not add any additional license text or accept files with a license included in them.
Each tool should have at least one good end-to-end integration test with a check for expected output, plus high-quality unit tests for all non-trivial utility methods/classes used by the tool. Although we have no specific coverage target, coverage should be extensive enough that if tests pass, the tool is guaranteed to be in a usable state.
All newly written code must have good test coverage (>90%).
All bug fixes must be accompanied by a regression test.
All pull requests must be reviewed before merging to master (even documentation changes).
Don't issue or accept pull requests that introduce warnings. Warnings must be addressed or suppressed.
Don't issue or accept pull requests that significantly decrease coverage (less than 1% decrease is sort of tolerable).
clone()unless you really know what you're doing. If you do override it, document thoroughly. Otherwise, prefer other means of making copies of objects.
toString()for anything other than human consumption (ie. don't base the logic of your code on results of
For logging, use org.apache.logging.log4j.Logger
We mostly follow the Google Java Style guide: http://google-styleguide.googlecode.com/svn/trunk/javaguide.html
Git: Don't push directly to master - make a pull request instead.
Git: Rebase and squash commits when merging.
If you push to master or mess the commit history, you owe us 1 growler or tasty snacks at happy hour. If you break the master build, you owe 3 growlers (or lots of tasty snacks). Beer may be replaced by wine (in the color and vintage of buyer's choosing) in proportions of 1 growler = 1 bottle.
We use Travis-CI as our continuous integration provider.
- Before merging any branch make sure that all required tests pass on travis.
- Every travis build will upload the test results to our hellbender google bucket. A link to the uploaded report will appear at the very bottom of the travis log. Look for the line that says
See the test report at.
If TestNG itself crashes there will be no report generated.
Certain Hellbender tools may optionally generate plots if R is installed. We recommend R v3.1.3 if you want to produce plots. If you are uninterested in plotting, R is still required by several of the unit tests. Plotting is currently untested and should be viewed as a convinience rather than a primary output.
R installation is not part of the gradle build. See http://cran.r-project.org/ for general information on installing R for your system.
- for ubuntu see these ubuntu specific instructions
- for OSX we recommend installation through homebrew
brew tap homebrew/science brew install R
The plotting R scripts require certain R packages to be installed. You can install these by running
scripts/install_R_packages.R. Either run it as superuser to force installation into the sites library or run interactively and create a local library.
sudo Rscript scripts/install_R_packages.R
Creating a Hellbender project in the IntelliJ IDE:
Ensure that you have
gradleand the Java 8 JDK installed
Install the TestNG plugin (in preferences)
Clone the Hellbender repository using git
In IntelliJ, go to File -> "Import Project"
Select the root directory of your Hellbender clone, then "Ok"
Select "Import project from external model", then "Gradle", then "Next"
Ensure that "Gradle project" points to the build.gradle file in the root of your Hellbender clone
Select "Use local gradle distribution", and enter your Gradle home directory in the "Gradle home" box. This will be the directory that contains the
bindirectory where the actual gradle executable (not merely a symlink to it!) lives. For example, if the actual gradle executable is
/usr/local/Cellar/gradle/2.2.1/libexec/bin/gradle, you would enter
/usr/local/Cellar/gradle/2.2.1/libexec/as your gradle home directory.
After downloading project dependencies, IntelliJ should open a new window with your Hellbender project
In File -> "Project Structure" -> "Project", set the "Project SDK" to your Java 1.8 JDK, and "Project language level" to 8 (you may need to add your Java 8 JDK under "Platform Settings" -> SDKs if it isn't there already). Then click "Apply"/"Ok".
Setting up debugging in IntelliJ
Follow the instructions above for creating an IntelliJ project for Hellbender
Go to Run -> "Edit Configurations", then click "+" and add a new "Application" configuration
Set the name of the new configuration to something like "Hellbender debug"
For "Main class", enter
Ensure that "Use classpath of module:" is set to use the "hellbender" module's classpath
Enter the Hellbender arguments for the command you want to debug in "Program Arguments"
Set breakpoints, etc., as desired, then select "Run" -> "Debug" -> "Hellbender debug" to start your debugging session
In future debugging sessions, you can simply adjust the "Program Arguments" in the "Hellbender debug" configuration as needed
Updating the Intellij project when dependencies change
If there are dependency changes in
build.gradle it is necessary to refresh the gradle project. This is easily done with the following steps.
- Open the gradle tool window ( "View" -> "Tool Windows" -> "Gradle" )
- Click the refresh button in the Gradle tool window. It is in the top left of the gradle view and is represented by two blue arrows.
Uploading Archives to Sonatype
To upload snapshots to sonatype you'll need the following:
You must have a registered account on the sonatype JIRA (and be approved as a hellbender uploader)
You need to configure several additional properties in your
*If you want to upload a release instead of a snapshot you will additionally need to have access to the hellbender signing key and password
#needed for snapshot upload sonatypeUsername=<your sonatype username> sonatypePassword=<your sonatype password> #needed for signing a release signing.keyId=<hellbender key id> signing.password=<hellbender key password> signing.secretKeyRingFile=/Users/<username>/.gnupg/secring.gpg
To perform an upload, use
Currently all builds are considered snapshots. The archive name is based off of