Integrated Genome Browser /

Filename Size Date modified Message
core
developmentPlugins
distribution
doc
galaxy
main
optionalPlugins
plugins
tools/LuceneIndexing
4.4 KB
13.7 KB
3.5 KB
3.3 KB
3.7 KB
2.0 KB
1.1 KB
1.4 KB
2.0 KB
54.0 KB
361 B
179 B
1.9 KB
1.8 KB
26 B

Integrated Genome Browser

The Integrated Genome Browser (IGB, pronounced ig-bee) is a fast, free, and highly interactive desktop genome browser ideal for exploring and understanding large-scale data sets from genomics. Originally developed at Affymetrix, IGB is now open source software.

IGB is also an extensible visual analytics platform. Developers can use IGB to create new interactive visualizations and visual analysis functions called IGB Apps.

To get IGB, clone this repository or download an IGB installer for your platform.

See:


Command-line quick start

To build and run from the command line:

  1. Clone the team repository to your desktop.
  2. Inside the local copy, check out the branch you wish to build. Check out release_candidate to get the released (or soon to be released) version of IGB.
  3. Build IGB using maven. Skip tests to save time.
  4. Run IGB using the run_igb script for your platform.

Ex)

git clone https://bitbucket.org/lorainelab/integrated-genome-browser
cd integrated-genome-browser
git checkout release_candidate
mvn clean install -DskipTests=true
run_igb.sh

The preceding commands:

  • Create IGB executable igb_exe.jar, used by the run scripts to run IGB. Contains all dependencies required to run IGB.
  • Copy IGB jar files (artifacts) to your local maven cache, useful you are developing IGB Apps.

IGB and IGB Apps use semantic versioning. Different IGB versions can co-exist in your local maven cache.


To get help


Developing IGB Apps

IGB runs in an OSGi container, which supports adding and removing pluggable Apps while IGB is running. For OSGi tutorials written by IGB Developers, see:


To contribute

Use fork-and-branch workflow:

  1. Fork the team repository.
  2. Create branches specific to the changes you want to make, push to your fork.
  3. Issue pull requests to the team repository's master branch.

See: