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.
- BioViz Web site with platform-specific installers
- Searchable on-line User's Guide
- IGB programming on-line class
- IGB Channel on YouTube with video tutorials and demos
- IGB Jira Issue Tracker site describes development plans
- Article describing Integrated Genome Browser: Visual analytics platform for genomics
Command-line quick start
To build and run from the command line:
- Clone the team repository to your desktop.
- Inside the local copy, check out the branch you wish to build. Review branch names to identify currently released version of IGB.
- Build IGB using maven. Skip tests to save time.
- Run IGB using the run_igb script for your platform.
Note: Instructions above assume you have Java installed on your computer. See Download section for platform-specific installers, which come with IGB and Java together.
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, including third party libraries, required to run IGB.
- Copy IGB jar files (artifacts) to your local maven cache, useful you are developing IGB Apps.
- Run IGB
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 Developer alumni, see:
- Stackleader.com blog posts on OSGI
Use fork-and-branch workflow:
- Fork the team repository.
- Create branches specific to the changes you want to make, push to your fork.
- Issue pull requests to the team repository's master branch from the branch on your fork.