Integrated Genome Browser /

Filename Size Date modified Message
core
developmentPlugins
distribution
doc
galaxy
main
optionalPlugins
plugins
tools/LuceneIndexing
4.4 KB
Ignore emacs temp & backup files, ignore Mac hidden directory .DS_Store
13.7 KB
global application of formatting
3.5 KB
updated NOTICES.txt to give credit to install4j
3.6 KB
Correct link syntax to on-line class
10.9 KB
2.0 KB
updated gradle for new build server config
1.1 KB
added parallel builds for the maven build
1.4 KB
added parallel builds for the maven build
2.0 KB
added parallel builds for the maven build
56.2 KB
Merged master into IGBF-1196-Cache-Clean
361 B
work
179 B
updated launch scripts to remove max heap argument
1.9 KB
updated launch scripts to remove max heap argument
1.8 KB
updated launch scripts to remove max heap argument
26 B
added gradle settings file

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
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.

Note that IGB runs as modular OSGi bundles within an OSGi container. When IGB launches, the OSGi container may load these bundles to a local bundle cache directory named for the IGB version. To ensure that only the newest, most recently built code is used, delete the bundle cache directory for the version you want to run. See .igb in your user home directory.


To get help

Visit the Bioviz help page


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: