A C++ interface for key next generation sequencing file formats. This library provides an API for handilng SAM, BAM, CRAM, VCF, BCF, BED, intervals and interval_list files.

The implementation is currently incomplete, but is under development. The APIs are free to change until we reach version 1.

• Project website: http://broadinstitute.github.io/gamgee/
• Developer docs: http://broadinstitute.github.io/gamgee/doxygen/

Gamgee is licensed under the MIT License

If you need detailed instructions, read our blog post on how to set up your development environment.

You'll need the latest version of Boost installed in your system.

$ hub clone broadinstitute/gamgee         # simple git clone also works here

Gamgee is configured to use CMake for better integration with the CLion IDE. We recommend an out-of-source build. From your Gamgee root directory, create a build directory:

$ mkdir build/

Navigate to that directory to complete the initial CMake setup:

$ cd build/
$ cmake ..

If building on the Broad servers, you will need extra arguments:

$ cmake .. -DCMAKE_C_COMPILER=`which gcc` -DCMAKE_CXX_COMPILER=`which g++`

After the setup of the build configuration and makefiles, build Gamgee by executing make from the build/ directory:

$ make

By default, CMake will execute the most recent explicitly specified build configuration (release/debug). To specify a build configuration use:

$ make release

or

$ make debug

for the release or debug configurations, respectively.

• To clean your build, use

  $ make clean
  

• If building on the Broad cluster you will need these dotkits

reuse -q .boost-1.55.0 reuse -q .fftw-3.3.4 reuse -q GCC-4.9 reuse -q CMake ``` NOTE: the CMake dotkit is only availble for systems running RHEL 6 or higher. For other systems, you will have to compile your own version of CMake from the latest source

Gamgee comes with an extensive suite of unit tests. To run all tests simply do:

$ make run_test

1. Download the latest version of the CLion IDE from here

2. Click through the walk-through and set up your preferences as desired.

3. At the startup menu, select "Import Project From Sources"

4. Navigate to the Gamgee repo directory and select it.

5. CLion will inform you that "Directory gamgee contains CMakeLists.txt". Choose "Open Project".

6. CLion may not recognize all of the namespaces in the code until you execute a build from the IDE. Select "Build" from the Run menu or click the build button in the upper right (green down arrow with ones and zeros).

7. If CLion still can't find all dependencies, go to File > Invalidate Caches / Restart... This will restart CLion. Reindexing files and references may take a minute or two.

NOTE: Using CMake from CLion uses a different build directory than using CMake from the command line.