Skip to content

dfci/genome-nexus

This branch is 1 commit ahead of, 330 commits behind genome-nexus/genome-nexus:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Eric MarriottLuke-Sikina
Eric Marriott
and
Dec 5, 2019
ee21e22 Β· Dec 5, 2019
Sep 12, 2019
Aug 16, 2019
Jun 19, 2019
Sep 26, 2019
Feb 28, 2019
Sep 26, 2019
Dec 5, 2019
Dec 5, 2019
Sep 4, 2019
Jan 8, 2016
Sep 5, 2019
Aug 16, 2019
Jun 22, 2018
Aug 15, 2019
Sep 4, 2019
Jul 30, 2019
Apr 11, 2018
Sep 5, 2019
Aug 31, 2018
Jul 17, 2019
Sep 4, 2019
Feb 28, 2019

Repository files navigation

Genome Nexus 🧬

Genome Nexus, a comprehensive one-stop resource for fast, automated and high-throughput annotation and interpretation of genetic variants in cancer. Genome Nexus integrates information from a variety of existing resources, including databases that convert DNA changes to protein changes, predict the functional effects of protein mutations, and contain information about mutation frequencies, gene function, variant effects, and clinical actionability.

Documentation πŸ“–

See the docs

Run πŸ’»

Alternative 1 - run genome-nexus, mongoDB and genome-nexus-vep in docker containers

First, set environment variables for Ensembl Release, VEP Assembly, location of VEP Cache, and species (since a mouse instalation is supported). If these are not, the default values from .env will be set.

The reference genome and Ensembl release must be consistent with a version in genome-nexus-importer/data/. For example grch37_ensembl92, grch38_ensembl92 or grch38_ensembl95:

export REF_ENSEMBL_VERSION=grch38_ensembl92

If you want to setup Genome Nexus for mouse, also set the SPECIES variable to 'mus_musculus'. Also see the docs to create a mouse database.

export SPECIES=mus_musculus

If you would like to do local VEP annotations instead of using the public Ensembl API, please uncomment # gn_vep.region.url=http://localhost:6060/vep/human/region/VARIANT in your application.properties. This will require you to download the VEP cache files for the preferred Ensembl Release and Reference genome, see our documentation on downloading the Genome Nexus VEP Cache. This will take several hours.

# Set local cache dir
export VEP_CACHE=<local_vep_cache>

# GRCh38 or GRCh37
export VEP_ASSEMBLY=GRCh38

Run docker-compose to create images and containers:

docker-compose up --build -d

Run without recreating images:

docker-compose up -d

Run without Genome Nexus VEP:

# Start both the Web and DB (dependency of Web) containers
docker-compose up -d web

Stop and remove containers:

docker-compose down

Alternative 2 - run genome-nexus locally, but mongoDB in docker container

# the genomenexus/gn-mongo images comes with all the required tables imported
# change latest to different version if necessary (only need to run this once)
docker run --name=gn-mongo --restart=always -p 27017:27017 -d genomenexus/gn-mongo:latest 
mvn  -DskipTests clean install
java -jar web/target/web-*.war

Alternative 3 - install mongoDB locally and run with local java

Install mongoDB manually. Then follow instructions in genome-nexus-importer to initialize the database.

After that run this:

mvn clean install
java -jar web/target/web-*.war

Test Status πŸ‘·β€β™€οΈ

branch master rc
status Build Status Build Status

Deploy πŸš€

Deploy

About

Interpreting cancer genomics data 🧬

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 89.5%
  • Jupyter Notebook 10.5%