<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://manual.genomeview.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thomas+Admin</id>
	<title>GenomeView Manual - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://manual.genomeview.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thomas+Admin"/>
	<link rel="alternate" type="text/html" href="https://manual.genomeview.org/Special:Contributions/Thomas_Admin"/>
	<updated>2026-05-27T21:11:57Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.6</generator>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Supported_versions&amp;diff=13023</id>
		<title>Supported versions</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Supported_versions&amp;diff=13023"/>
		<updated>2017-11-28T16:17:02Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Currently available versions:&lt;br /&gt;
&lt;br /&gt;
{|  &lt;br /&gt;
! Version&lt;br /&gt;
! Webstart&lt;br /&gt;
! Applet*&lt;br /&gt;
! JavaScript embedding&lt;br /&gt;
! EOL&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gvN36.jnlp N36(stable,webstart)]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| November 2018&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2400.jnlp 2400 (stable,webstart)]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| November 2014&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2250.jnlp 2250]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| August 2014&lt;br /&gt;
|- &lt;br /&gt;
|[http://genomeview.org/start/gv2170.jnlp 2170 (experimental)]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| --&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2144.jnlp 2144]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| May 2014&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2126.jnlp 2126]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| February 2014&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/gv2082.jnlp 2082 (experimental)]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| --&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2020.jnlp 2020]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv1983.jnlp 1983]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv1939.jnlp 1939]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv1912.jnlp 1912]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[[File:yes.png]]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Support offered on a best effort basis&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[[File:no.png]]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Support offered on a low priority best effort basis&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The developers of GenomeView offer a limited best-effort support for recent versions free of charge. Unfortunately, as this is a free product, we cannot guarantee anything. If you need a guaranteed service level agreement, [mailto:thomas@genomeview.org contact the project manager] and we will work out a solution.&lt;br /&gt;
&lt;br /&gt;
We intend to provide one year support for newly released versions.&lt;br /&gt;
&lt;br /&gt;
EOL: End of Life: After this data we cannot guarantee that this version will continue to run. Files may be archived from the server and so on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you need continued support for a particular feature or version past its EOL, you should [mailto:thomas@genomeview.org contact the project manager] for more information. We can work together to find a solution.&lt;br /&gt;
&lt;br /&gt;
Note: Since March 2013, the support for the applet version has become a very low priority. There are too many platform/browser compatibility issues and we have too few resources to deal with all of them.&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Talk:Command_line_options&amp;diff=13022</id>
		<title>Talk:Command line options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Talk:Command_line_options&amp;diff=13022"/>
		<updated>2014-06-03T15:26:34Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Blanked the page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=13021</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=13021"/>
		<updated>2014-06-03T15:16:13Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC|align=right}}&lt;br /&gt;
&lt;br /&gt;
Welcome to the GenomeView manual. These pages aim to answer any questions you may have as an end-user, a platform-user or as a contributing developer.&lt;br /&gt;
&lt;br /&gt;
This documentation is open for anyone to contribute to, just click the edit-button near the top and you can help make this a better resource for everyone. Due to increasing vandalism we were forced to shutdown anonymous editing and account sign-up. '''If you like an account, please drop a note to support@genomeview.org'''. &lt;br /&gt;
&lt;br /&gt;
Feel free to copy documentation from the old manual to here, there are still some pages that need to be transferred and we're happy with any help you can spare.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[Quick start|Getting started with GenomeView in 5 minutes]] ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=User manual}}&lt;br /&gt;
These manual pages describe how to use GenomeView and how to prepare your data to be usable in GenomeView.&lt;br /&gt;
&lt;br /&gt;
[[Starting GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Preparing and loading data]] -- [[Preloaded data]]&lt;br /&gt;
&lt;br /&gt;
[[Navigation]] -- [[Keyboard short-cuts]]&lt;br /&gt;
&lt;br /&gt;
[[Visualizations]]&lt;br /&gt;
&lt;br /&gt;
[[Search for...]]&lt;br /&gt;
&lt;br /&gt;
[[Manipulating and configuring the views]]&lt;br /&gt;
&lt;br /&gt;
[[Editing annotations]]&lt;br /&gt;
&lt;br /&gt;
[[Exporting data and saving changes]]&lt;br /&gt;
&lt;br /&gt;
[[More functionality with plugins]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Getting help}}&lt;br /&gt;
&lt;br /&gt;
[[Frequently asked questions]]&lt;br /&gt;
&lt;br /&gt;
[[I have a problem, help me, please]]&lt;br /&gt;
&lt;br /&gt;
[[Report a bug or request a feature]]&lt;br /&gt;
&lt;br /&gt;
[[Supported versions]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Platform-user manual}}&lt;br /&gt;
These manual pages describe how to integrate GenomeView with your web-based platform or how to communicate with GenomeView from 3-rd party software. &lt;br /&gt;
&lt;br /&gt;
[[Using GenomeView from the command-line]]&lt;br /&gt;
&lt;br /&gt;
[[Integration]]&lt;br /&gt;
&lt;br /&gt;
[[Session files]] -- [[Configuration options]]&lt;br /&gt;
&lt;br /&gt;
[[Communicating with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Programming with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up authentication and encryption]]&lt;br /&gt;
&lt;br /&gt;
[[Making a plugin]]&lt;br /&gt;
&lt;br /&gt;
[[Integrating GenomeView as an editor]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up a Genome Explorer repository]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Developer manual}}&lt;br /&gt;
These pages are aimed towards contributors to GenomeView and developers who work directly on the GenomeView code.&lt;br /&gt;
&lt;br /&gt;
Currently most of this documentation lives on [https://sourceforge.net/p/genomeview/wiki/ Sourceforge].&lt;br /&gt;
&lt;br /&gt;
[[Unit test example data files]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=13020</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=13020"/>
		<updated>2014-06-03T15:15:46Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC|align=right}}&lt;br /&gt;
&lt;br /&gt;
Welcome to the GenomeView manual. These pages aim to answer any questions you may have as an end-user, a platform-user or as a contributing developer.&lt;br /&gt;
&lt;br /&gt;
This documentation is open for anyone to contribute to, just click the edit-button near the top and you can help make this a better resource for everyone. '''Due to increasing vandalism we were forced to shutdown anonymous editing and account sign-up'''. If you like an account, please drop a note to support@genomeview.org. &lt;br /&gt;
&lt;br /&gt;
Feel free to copy documentation from the old manual to here, there are still some pages that need to be transferred and we're happy with any help you can spare.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[Quick start|Getting started with GenomeView in 5 minutes]] ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=User manual}}&lt;br /&gt;
These manual pages describe how to use GenomeView and how to prepare your data to be usable in GenomeView.&lt;br /&gt;
&lt;br /&gt;
[[Starting GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Preparing and loading data]] -- [[Preloaded data]]&lt;br /&gt;
&lt;br /&gt;
[[Navigation]] -- [[Keyboard short-cuts]]&lt;br /&gt;
&lt;br /&gt;
[[Visualizations]]&lt;br /&gt;
&lt;br /&gt;
[[Search for...]]&lt;br /&gt;
&lt;br /&gt;
[[Manipulating and configuring the views]]&lt;br /&gt;
&lt;br /&gt;
[[Editing annotations]]&lt;br /&gt;
&lt;br /&gt;
[[Exporting data and saving changes]]&lt;br /&gt;
&lt;br /&gt;
[[More functionality with plugins]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Getting help}}&lt;br /&gt;
&lt;br /&gt;
[[Frequently asked questions]]&lt;br /&gt;
&lt;br /&gt;
[[I have a problem, help me, please]]&lt;br /&gt;
&lt;br /&gt;
[[Report a bug or request a feature]]&lt;br /&gt;
&lt;br /&gt;
[[Supported versions]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Platform-user manual}}&lt;br /&gt;
These manual pages describe how to integrate GenomeView with your web-based platform or how to communicate with GenomeView from 3-rd party software. &lt;br /&gt;
&lt;br /&gt;
[[Using GenomeView from the command-line]]&lt;br /&gt;
&lt;br /&gt;
[[Integration]]&lt;br /&gt;
&lt;br /&gt;
[[Session files]] -- [[Configuration options]]&lt;br /&gt;
&lt;br /&gt;
[[Communicating with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Programming with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up authentication and encryption]]&lt;br /&gt;
&lt;br /&gt;
[[Making a plugin]]&lt;br /&gt;
&lt;br /&gt;
[[Integrating GenomeView as an editor]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up a Genome Explorer repository]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Developer manual}}&lt;br /&gt;
These pages are aimed towards contributors to GenomeView and developers who work directly on the GenomeView code.&lt;br /&gt;
&lt;br /&gt;
Currently most of this documentation lives on [https://sourceforge.net/p/genomeview/wiki/ Sourceforge].&lt;br /&gt;
&lt;br /&gt;
[[Unit test example data files]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=13019</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=13019"/>
		<updated>2014-06-03T15:10:29Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Undo revision 13006 by 151.252.42.26 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
==General considerations==&lt;br /&gt;
To present your data in GenomeView optimally, there are a number of things you have to keep in mind.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Indexing===&lt;br /&gt;
Please follow the recommendation in the [[recommended file formats]] page.&lt;br /&gt;
&lt;br /&gt;
You will want to &amp;lt;a href=&amp;quot;/content/preparing-fasta-files&amp;quot;&amp;gt;index your reference sequence&amp;lt;/a&amp;gt; to reduce loading times.&lt;br /&gt;
&lt;br /&gt;
You may want to index annotation files, but this is not recommended unless they are over 10 Mb when compressed with gzip because you will loose structural information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;To load an indexed file, you point GenomeView to the main file and GenomeView will try to find the index by itself. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Compression===&lt;br /&gt;
&amp;lt;p&amp;gt;GenomeView supports GZIP compression transparently on all non-indexed file formats, i.e. compression and indexing are mutually exclusive. However as part of the indexing process, many file formats will be compressed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Short read data&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Depending on what information you want to get out of the visualization, there are basically two ways to load short read data. The first one is the &amp;lt;a href=&amp;quot;/content/short-read-track&amp;quot;&amp;gt;Short Read Track&amp;lt;/a&amp;gt; which will give you a detailed view with all individual reads. The second one is the &amp;lt;a href=&amp;quot;/content/pile-track&amp;quot;&amp;gt;Pile up track&amp;lt;/a&amp;gt; which will give a more of a summary view/ coverage plot based on your sequence reads. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-short-read-alignments&amp;quot;&amp;gt;Instructions to prepare data for the short read track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-pileup&amp;quot;&amp;gt;Instructions to prepare data for the pile up track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start link==&lt;br /&gt;
The fastest and simplest way to get started and with integrating GenomeView with your data is by directly constructing a webstart link.&lt;br /&gt;
&lt;br /&gt;
The default launch URL is located at http://genomeview.org/start/launch.jnlp. If you require a specific version, there are stable URLs available from the [[supported versions]] page.&lt;br /&gt;
&lt;br /&gt;
The next step is constructing your URL to load sequence and features. Below a sample URL, which will load some sequence with annotation and some short reads. It will start with the [100000,200000] region visible.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--position 100000:200000 --url http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.fasta http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.gff.gz http://www.broadinstitute.org/software/genomeview/demo/c_elegans/uwgs-rw_L2_FC6218_3.CHROMOSOME_IV.sorted.bam.bai&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pasting this URL in your browser will start GenomeView with data from C. elegans loaded.&lt;br /&gt;
&lt;br /&gt;
[[Command line options]] to GenomeView can be added after the question mark after the installation URL.&lt;br /&gt;
&lt;br /&gt;
The formalized version of the integration URL looks like this:&lt;br /&gt;
&lt;br /&gt;
 http://genomeview.org/start/launch.jnlp?[command line options for GenomeView separated with spaces]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Important:''' You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start session (recommended)==&lt;br /&gt;
A [[session file]] is a text file that contains instructions for GenomeView on which data to load and how to configure itself. &lt;br /&gt;
&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
==Embedding GenomeView as an applet==&lt;br /&gt;
&amp;lt;div style=&amp;quot;color:red&amp;quot;&amp;gt;Support for the applet version of GenomeView is currently on hold due to ever changing Java support from the various browser and OS vendors. It is impossible to maintain any semblance of stability. All of the material below may or may not work.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The key code that needs to be included in the body of your web page is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://www.java.com/js/deployJava.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://genomeview.org/start/genomeview.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot;&amp;amp;gt;&lt;br /&gt;
    	var gv_url		= null;&lt;br /&gt;
     	var gv_config	= 'http://genomeview.org/jsdemo/democonfig.txt';    &lt;br /&gt;
     	var gv_extra	= null;&lt;br /&gt;
       	var gv_location	= null;&lt;br /&gt;
        startGV(gv_url,gv_location,gv_config,gv_extra,500,400);&lt;br /&gt;
&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The &amp;lt;code&amp;gt;gv_url&amp;lt;/code&amp;gt; can be used to pre-load a reference sequence. This file will be loaded first and only then will GenomeView proceed with loading additional data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The configuration file you want to use, can be specified using the &amp;lt;code&amp;gt;gv_config&amp;lt;/code&amp;gt; option.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;All other data that you want to have loaded can be specified in a space separated list in &amp;lt;code&amp;gt;gv_extra&amp;lt;/code&amp;gt;. These data sets will be loaded in parallel.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The location that will initially be visible, can be set by &amp;lt;code&amp;gt;gv_location&amp;lt;/code&amp;gt;. The position is in the format &amp;amp;lt;entry&amp;amp;gt;:&amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt; The entry part is optional can be omitted in which case it becomes &amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Note: we strongly recommend you use the genomeview.js we provide as that's the one we keep up to date with progressing releases.&amp;lt;/em&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=13018</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=13018"/>
		<updated>2014-06-03T15:10:10Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Undo revision 13007 by 134.91.140.76 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
I loved your blog article. Really Cool. aaccddgedddgdaek&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start link==&lt;br /&gt;
The fastest and simplest way to get started and with integrating GenomeView with your data is by directly constructing a webstart link.&lt;br /&gt;
&lt;br /&gt;
The default launch URL is located at http://genomeview.org/start/launch.jnlp. If you require a specific version, there are stable URLs available from the [[supported versions]] page.&lt;br /&gt;
&lt;br /&gt;
The next step is constructing your URL to load sequence and features. Below a sample URL, which will load some sequence with annotation and some short reads. It will start with the [100000,200000] region visible.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--position 100000:200000 --url http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.fasta http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.gff.gz http://www.broadinstitute.org/software/genomeview/demo/c_elegans/uwgs-rw_L2_FC6218_3.CHROMOSOME_IV.sorted.bam.bai&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pasting this URL in your browser will start GenomeView with data from C. elegans loaded.&lt;br /&gt;
&lt;br /&gt;
[[Command line options]] to GenomeView can be added after the question mark after the installation URL.&lt;br /&gt;
&lt;br /&gt;
The formalized version of the integration URL looks like this:&lt;br /&gt;
&lt;br /&gt;
 http://genomeview.org/start/launch.jnlp?[command line options for GenomeView separated with spaces]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Important:''' You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start session (recommended)==&lt;br /&gt;
A [[session file]] is a text file that contains instructions for GenomeView on which data to load and how to configure itself. &lt;br /&gt;
&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
==Embedding GenomeView as an applet==&lt;br /&gt;
&amp;lt;div style=&amp;quot;color:red&amp;quot;&amp;gt;Support for the applet version of GenomeView is currently on hold due to ever changing Java support from the various browser and OS vendors. It is impossible to maintain any semblance of stability. All of the material below may or may not work.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The key code that needs to be included in the body of your web page is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://www.java.com/js/deployJava.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://genomeview.org/start/genomeview.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot;&amp;amp;gt;&lt;br /&gt;
    	var gv_url		= null;&lt;br /&gt;
     	var gv_config	= 'http://genomeview.org/jsdemo/democonfig.txt';    &lt;br /&gt;
     	var gv_extra	= null;&lt;br /&gt;
       	var gv_location	= null;&lt;br /&gt;
        startGV(gv_url,gv_location,gv_config,gv_extra,500,400);&lt;br /&gt;
&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The &amp;lt;code&amp;gt;gv_url&amp;lt;/code&amp;gt; can be used to pre-load a reference sequence. This file will be loaded first and only then will GenomeView proceed with loading additional data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The configuration file you want to use, can be specified using the &amp;lt;code&amp;gt;gv_config&amp;lt;/code&amp;gt; option.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;All other data that you want to have loaded can be specified in a space separated list in &amp;lt;code&amp;gt;gv_extra&amp;lt;/code&amp;gt;. These data sets will be loaded in parallel.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The location that will initially be visible, can be set by &amp;lt;code&amp;gt;gv_location&amp;lt;/code&amp;gt;. The position is in the format &amp;amp;lt;entry&amp;amp;gt;:&amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt; The entry part is optional can be omitted in which case it becomes &amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Note: we strongly recommend you use the genomeview.js we provide as that's the one we keep up to date with progressing releases.&amp;lt;/em&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=13017</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=13017"/>
		<updated>2014-06-03T15:09:58Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Undo revision 13008 by 118.174.199.77 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
I loved your blog article. Really Cool. aaccddgedddgdaek&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start session (recommended)==&lt;br /&gt;
A [[session file]] is a text file that contains instructions for GenomeView on which data to load and how to configure itself. &lt;br /&gt;
&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
==Embedding GenomeView as an applet==&lt;br /&gt;
&amp;lt;div style=&amp;quot;color:red&amp;quot;&amp;gt;Support for the applet version of GenomeView is currently on hold due to ever changing Java support from the various browser and OS vendors. It is impossible to maintain any semblance of stability. All of the material below may or may not work.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The key code that needs to be included in the body of your web page is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://www.java.com/js/deployJava.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://genomeview.org/start/genomeview.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot;&amp;amp;gt;&lt;br /&gt;
    	var gv_url		= null;&lt;br /&gt;
     	var gv_config	= 'http://genomeview.org/jsdemo/democonfig.txt';    &lt;br /&gt;
     	var gv_extra	= null;&lt;br /&gt;
       	var gv_location	= null;&lt;br /&gt;
        startGV(gv_url,gv_location,gv_config,gv_extra,500,400);&lt;br /&gt;
&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The &amp;lt;code&amp;gt;gv_url&amp;lt;/code&amp;gt; can be used to pre-load a reference sequence. This file will be loaded first and only then will GenomeView proceed with loading additional data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The configuration file you want to use, can be specified using the &amp;lt;code&amp;gt;gv_config&amp;lt;/code&amp;gt; option.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;All other data that you want to have loaded can be specified in a space separated list in &amp;lt;code&amp;gt;gv_extra&amp;lt;/code&amp;gt;. These data sets will be loaded in parallel.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The location that will initially be visible, can be set by &amp;lt;code&amp;gt;gv_location&amp;lt;/code&amp;gt;. The position is in the format &amp;amp;lt;entry&amp;amp;gt;:&amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt; The entry part is optional can be omitted in which case it becomes &amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Note: we strongly recommend you use the genomeview.js we provide as that's the one we keep up to date with progressing releases.&amp;lt;/em&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=13016</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=13016"/>
		<updated>2014-06-03T15:09:44Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Undo revision 13010 by 78.38.101.2 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
I loved your blog article. Really Cool. aaccddgedddgdaek&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
==Embedding GenomeView as an applet==&lt;br /&gt;
&amp;lt;div style=&amp;quot;color:red&amp;quot;&amp;gt;Support for the applet version of GenomeView is currently on hold due to ever changing Java support from the various browser and OS vendors. It is impossible to maintain any semblance of stability. All of the material below may or may not work.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The key code that needs to be included in the body of your web page is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://www.java.com/js/deployJava.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://genomeview.org/start/genomeview.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot;&amp;amp;gt;&lt;br /&gt;
    	var gv_url		= null;&lt;br /&gt;
     	var gv_config	= 'http://genomeview.org/jsdemo/democonfig.txt';    &lt;br /&gt;
     	var gv_extra	= null;&lt;br /&gt;
       	var gv_location	= null;&lt;br /&gt;
        startGV(gv_url,gv_location,gv_config,gv_extra,500,400);&lt;br /&gt;
&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The &amp;lt;code&amp;gt;gv_url&amp;lt;/code&amp;gt; can be used to pre-load a reference sequence. This file will be loaded first and only then will GenomeView proceed with loading additional data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The configuration file you want to use, can be specified using the &amp;lt;code&amp;gt;gv_config&amp;lt;/code&amp;gt; option.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;All other data that you want to have loaded can be specified in a space separated list in &amp;lt;code&amp;gt;gv_extra&amp;lt;/code&amp;gt;. These data sets will be loaded in parallel.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The location that will initially be visible, can be set by &amp;lt;code&amp;gt;gv_location&amp;lt;/code&amp;gt;. The position is in the format &amp;amp;lt;entry&amp;amp;gt;:&amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt; The entry part is optional can be omitted in which case it becomes &amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Note: we strongly recommend you use the genomeview.js we provide as that's the one we keep up to date with progressing releases.&amp;lt;/em&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=13015</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=13015"/>
		<updated>2014-06-03T15:09:08Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Reverted edits by Thomas Admin (talk) to last revision by 78.38.101.2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
I loved your blog article. Really Cool. aaccddgedddgdaek&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=13014</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=13014"/>
		<updated>2014-06-03T15:08:37Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Undo revision 13006 by 151.252.42.26 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
==General considerations==&lt;br /&gt;
To present your data in GenomeView optimally, there are a number of things you have to keep in mind.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Indexing===&lt;br /&gt;
Please follow the recommendation in the [[recommended file formats]] page.&lt;br /&gt;
&lt;br /&gt;
You will want to &amp;lt;a href=&amp;quot;/content/preparing-fasta-files&amp;quot;&amp;gt;index your reference sequence&amp;lt;/a&amp;gt; to reduce loading times.&lt;br /&gt;
&lt;br /&gt;
You may want to index annotation files, but this is not recommended unless they are over 10 Mb when compressed with gzip because you will loose structural information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;To load an indexed file, you point GenomeView to the main file and GenomeView will try to find the index by itself. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Compression===&lt;br /&gt;
&amp;lt;p&amp;gt;GenomeView supports GZIP compression transparently on all non-indexed file formats, i.e. compression and indexing are mutually exclusive. However as part of the indexing process, many file formats will be compressed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Short read data&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Depending on what information you want to get out of the visualization, there are basically two ways to load short read data. The first one is the &amp;lt;a href=&amp;quot;/content/short-read-track&amp;quot;&amp;gt;Short Read Track&amp;lt;/a&amp;gt; which will give you a detailed view with all individual reads. The second one is the &amp;lt;a href=&amp;quot;/content/pile-track&amp;quot;&amp;gt;Pile up track&amp;lt;/a&amp;gt; which will give a more of a summary view/ coverage plot based on your sequence reads. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-short-read-alignments&amp;quot;&amp;gt;Instructions to prepare data for the short read track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-pileup&amp;quot;&amp;gt;Instructions to prepare data for the pile up track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;br /&gt;
&lt;br /&gt;
Very nice site!&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=I_have_a_problem,_help_me,_please&amp;diff=12988</id>
		<title>I have a problem, help me, please</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=I_have_a_problem,_help_me,_please&amp;diff=12988"/>
		<updated>2014-01-03T15:48:02Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;We are happy to help you resolve any issues you may have while using GenomeView.&lt;br /&gt;
&lt;br /&gt;
== [[Frequently asked questions]] ==&lt;br /&gt;
Please check the [[Frequently asked questions]] first, maybe your problem has been encountered before.&lt;br /&gt;
&lt;br /&gt;
== [https://sourceforge.net/p/genomeview/bugs-and-other-requests/new/ Submit a support ticket] ==&lt;br /&gt;
&lt;br /&gt;
If you are still having trouble loading your data or you think you found a bug or you want to request a feature please [https://sourceforge.net/p/genomeview/bugs-and-other-requests/new/ log a ticket] with the following information:&lt;br /&gt;
&lt;br /&gt;
    Detailed description of your problem.&lt;br /&gt;
    Include the [[log file]] from the problematic GenomeView run. &lt;br /&gt;
    Which version of GV are you running?&lt;br /&gt;
    What operating system? OS X, Windows, Linux, ...?&lt;br /&gt;
    Which version of Java are you running?&lt;br /&gt;
    List step-by-step instructions on how to reproduce the problem.&lt;br /&gt;
    Provide us with access to the data files that are problematic. (optional)&lt;br /&gt;
&lt;br /&gt;
We need this information to help you as quickly as possible. If the problem is data specific and you can't share the data with us, there is likely very little we can do for you.&lt;br /&gt;
&lt;br /&gt;
If you don't want to login to Sourceforge, you can [mailto:support@genomeview.org e-mail the team] with the above information&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Supported_versions&amp;diff=10130</id>
		<title>Supported versions</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Supported_versions&amp;diff=10130"/>
		<updated>2013-11-18T23:07:17Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Currently available versions:&lt;br /&gt;
&lt;br /&gt;
{|  &lt;br /&gt;
! Version&lt;br /&gt;
! Webstart&lt;br /&gt;
! Applet*&lt;br /&gt;
! JavaScript embedding&lt;br /&gt;
! EOL&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2400.jnlp 2400 (stable,webstart)]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| November 2014&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2250.jnlp 2250]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| August 2014&lt;br /&gt;
|- &lt;br /&gt;
|[http://genomeview.org/start/gv2170.jnlp 2170 (experimental)]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| --&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2144.jnlp 2144]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| May 2014&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2126.jnlp 2126]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:yes.png]]&lt;br /&gt;
| February 2014&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/gv2082.jnlp 2082 (experimental)]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| --&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv2020.jnlp 2020]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv1983.jnlp 1983]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv1939.jnlp 1939]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|- &lt;br /&gt;
| [http://genomeview.org/start/gv1912.jnlp 1912]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| [[File:no.png]]&lt;br /&gt;
| Discontinued&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[[File:yes.png]]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Support offered on a best effort basis&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[[File:no.png]]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Support offered on a low priority best effort basis&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The developers of GenomeView offer a limited best-effort support for recent versions free of charge. Unfortunately, as this is a free product, we cannot guarantee anything. If you need a guaranteed service level agreement, [mailto:thomas@genomeview.org contact the project manager] and we will work out a solution.&lt;br /&gt;
&lt;br /&gt;
We intend to provide one year support for newly released versions.&lt;br /&gt;
&lt;br /&gt;
EOL: End of Life: After this data we cannot guarantee that this version will continue to run. Files may be archived from the server and so on.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you need continued support for a particular feature or version past its EOL, you should [mailto:thomas@genomeview.org contact the project manager] for more information. We can work together to find a solution.&lt;br /&gt;
&lt;br /&gt;
Note: Since March 2013, the support for the applet version has become a very low priority. There are too many platform/browser compatibility issues and we have too few resources to deal with all of them.&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=10129</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=10129"/>
		<updated>2013-11-18T23:06:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC|align=right}}&lt;br /&gt;
&lt;br /&gt;
Welcome to the GenomeView manual. These pages aim to answer any questions you may have as an end-user, a platform-user or as a contributing developer.&lt;br /&gt;
&lt;br /&gt;
This documentation is completely open for anyone to contribute to, just click the edit-button near the top and you can help make this a better resource for everyone.&lt;br /&gt;
&lt;br /&gt;
Feel free to copy documentation from the old manual to here, there are still some pages that need to be transferred and we're happy with any help you can spare.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[Quick start|Getting started with GenomeView in 5 minutes]] ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=User manual}}&lt;br /&gt;
These manual pages describe how to use GenomeView and how to prepare your data to be usable in GenomeView.&lt;br /&gt;
&lt;br /&gt;
[[Starting GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Preparing and loading data]] -- [[Preloaded data]]&lt;br /&gt;
&lt;br /&gt;
[[Navigation]] -- [[Keyboard short-cuts]]&lt;br /&gt;
&lt;br /&gt;
[[Visualizations]]&lt;br /&gt;
&lt;br /&gt;
[[Search for...]]&lt;br /&gt;
&lt;br /&gt;
[[Manipulating and configuring the views]]&lt;br /&gt;
&lt;br /&gt;
[[Editing annotations]]&lt;br /&gt;
&lt;br /&gt;
[[Exporting data and saving changes]]&lt;br /&gt;
&lt;br /&gt;
[[More functionality with plugins]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Getting help}}&lt;br /&gt;
&lt;br /&gt;
[[Frequently asked questions]]&lt;br /&gt;
&lt;br /&gt;
[[I have a problem, help me, please]]&lt;br /&gt;
&lt;br /&gt;
[[Report a bug or request a feature]]&lt;br /&gt;
&lt;br /&gt;
[[Supported versions]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Platform-user manual}}&lt;br /&gt;
These manual pages describe how to integrate GenomeView with your web-based platform or how to communicate with GenomeView from 3-rd party software. &lt;br /&gt;
&lt;br /&gt;
[[Using GenomeView from the command-line]]&lt;br /&gt;
&lt;br /&gt;
[[Integration]]&lt;br /&gt;
&lt;br /&gt;
[[Session files]] -- [[Configuration options]]&lt;br /&gt;
&lt;br /&gt;
[[Communicating with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Programming with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up authentication and encryption]]&lt;br /&gt;
&lt;br /&gt;
[[Making a plugin]]&lt;br /&gt;
&lt;br /&gt;
[[Integrating GenomeView as an editor]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up a Genome Explorer repository]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Developer manual}}&lt;br /&gt;
These pages are aimed towards contributors to GenomeView and developers who work directly on the GenomeView code.&lt;br /&gt;
&lt;br /&gt;
Currently most of this documentation lives on [https://sourceforge.net/p/genomeview/wiki/ Sourceforge].&lt;br /&gt;
&lt;br /&gt;
[[Unit test example data files]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_authentication_and_encryption&amp;diff=10128</id>
		<title>Setting up authentication and encryption</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_authentication_and_encryption&amp;diff=10128"/>
		<updated>2013-11-18T22:58:42Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Authentication&amp;lt;/h2&amp;gt;&lt;br /&gt;
GenomeView supports BasicAuth for webservers&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To create pasword files you can use htpasswd:&lt;br /&gt;
http://httpd.apache.org/docs/2.0/programs/htpasswd.html&lt;br /&gt;
&lt;br /&gt;
 htpasswd -c /location/of/.htpasswd username&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Explanation how to setup .htaccess to a folder:&lt;br /&gt;
http://httpd.apache.org/docs/2.2/howto/htaccess.html#auth&lt;br /&gt;
&lt;br /&gt;
 AuthUserFile /location/of/.htpasswd&lt;br /&gt;
 AuthType Basic&lt;br /&gt;
 AuthName “My Files&amp;quot;&lt;br /&gt;
 Require valid-user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Important is that you put the password file outside the document root that is accessible through the web.&lt;br /&gt;
&lt;br /&gt;
That should get you up and running.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Encryption&amp;lt;/h2&amp;gt;&lt;br /&gt;
GenomeView support SSL encrypted connections. It will use the certificate that is presented, but it will not verify the integrity of the key-chain.&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_authentication_and_encryption&amp;diff=10127</id>
		<title>Setting up authentication and encryption</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_authentication_and_encryption&amp;diff=10127"/>
		<updated>2013-11-18T22:51:15Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Authentication&amp;lt;/h2&amp;gt;&lt;br /&gt;
GenomeView supports BasicAuth for webservers&lt;br /&gt;
&lt;br /&gt;
Explanation how to setup .htaccess to a folder:&lt;br /&gt;
http://httpd.apache.org/docs/2.2/howto/htaccess.html#auth&lt;br /&gt;
&lt;br /&gt;
To create pasword files you can use htpasswd:&lt;br /&gt;
http://httpd.apache.org/docs/2.0/programs/htpasswd.html&lt;br /&gt;
&lt;br /&gt;
Important is that you put the password file outside the document root that is accessible through the web.&lt;br /&gt;
&lt;br /&gt;
That should get you up and running.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Encryption&amp;lt;/h2&amp;gt;&lt;br /&gt;
GenomeView support SSL encrypted connections. It will use the certificate that is presented, but it will not verify the integrity of the key-chain.&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10126</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10126"/>
		<updated>2013-11-18T21:58:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL' or alternatively you can call 'setInstructAllInstancesGV()'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the specified command line options.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| trackGV(trackname)&lt;br /&gt;
| Scroll vertically to make sure the named track is visible.&lt;br /&gt;
|- &lt;br /&gt;
| configGV(key=value)&lt;br /&gt;
| Set a single configuration option.&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. This could be used to check whether there is already a GenomeView instance launched and based on that information start an instance or load the data into the existing one.&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10125</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10125"/>
		<updated>2013-11-18T21:44:02Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL' or alternatively you can call 'setInstructAllInstancesGV()'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the specified command line options.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. This could be used to check whether there is already a GenomeView instance launched and based on that information start an instance or load the data into the existing one.&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10124</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10124"/>
		<updated>2013-11-18T21:22:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL' or alternatively you can call 'setInstructAllInstancesGV()'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. This could be used to check whether there is already a GenomeView instance launched and based on that information start an instance or load the data into the existing one.&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10123</id>
		<title>Session files</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10123"/>
		<updated>2013-11-18T20:34:18Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Body */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Session files allow you to organize a large number of data files and config options in a single file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An example session file:&lt;br /&gt;
 http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&lt;br /&gt;
&lt;br /&gt;
You can use 'View source', or something similar, in your browser to see the actual file structure. It is a plain text file with on each line a file that needs to be loaded.&lt;br /&gt;
&lt;br /&gt;
==File structure ==&lt;br /&gt;
&lt;br /&gt;
===Header===&lt;br /&gt;
Make sure the file starts with a line that contains the words 'GenomeView' and 'session'. These two words have to be on the first line!&lt;br /&gt;
&lt;br /&gt;
We recommend:&lt;br /&gt;
 ##GenomeView session&lt;br /&gt;
&lt;br /&gt;
This header is used to detect the file format by GenomeView.&lt;br /&gt;
&lt;br /&gt;
=== Body ===&lt;br /&gt;
&lt;br /&gt;
The remainder of the file contains lines that have various instructions to load data, configure GenomeView or load plugins. The table below has an overview of all options.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
!Instruction*&lt;br /&gt;
!Value&lt;br /&gt;
|-&lt;br /&gt;
|CONFIG&lt;br /&gt;
|URL or local file path to the configuration file. This line should be the first in the session file, otherwise some data may not have the correct configuration file when initializing.&lt;br /&gt;
|-&lt;br /&gt;
|DATA**	&lt;br /&gt;
|URL or local file path for a data file. This file will be loaded. You do not need to specify the index, GenomeView will look for it in the same folder.&lt;br /&gt;
|-&lt;br /&gt;
|PREFIX	&lt;br /&gt;
|URL or local file path prefix. The value of this instructions will be prepended to any DATA, PLUGIN or CONFIG pairs that follow this instruction. A PREFIX values is only valid for subsequent DATA, PLUGIN and CONFIG pairs. This can to simplify loading many files from multiple locations. To reset the PREFIX, you can use an empty value. You can use multiple PREFIX instructions through-out the session, they will each be valid for the following DATA, PLUGIN and CONFIG instructions, until reset with an alternative value.&lt;br /&gt;
|-&lt;br /&gt;
|OPTION	&lt;br /&gt;
|Key=value definition of a single configuration option. This is suited to override a few config options as needed.&lt;br /&gt;
|-&lt;br /&gt;
|ALIAS	[identifier]=[display name]. &lt;br /&gt;
|Add an additional synonym for an Entry (chromosome). This can be useful if your data has different identifiers for the same sequence in different files. Multiple identifiers names can point to the same display name, in that case the data from all those identifiers will be projected onto a single entry.&lt;br /&gt;
|-&lt;br /&gt;
|LOCATION&lt;br /&gt;
|Set the visible location to the specified location. The location needs to be specified [entry]:[start position]-[end position].&lt;br /&gt;
|-&lt;br /&gt;
|PLUGIN	&lt;br /&gt;
|Allows you to request the user to automatically install a plugin. The plugin needs to be specified as a URL to the zip file. You can use relative names in conjunction with the PREFIX parameter&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 ** The legacy keywords C, U and F will continue to work.&lt;br /&gt;
&lt;br /&gt;
Each of the lines should be organized like this:&lt;br /&gt;
 instruction[tab, colon or space]value&lt;br /&gt;
&lt;br /&gt;
For example, all of these are valid ways to specify a file&lt;br /&gt;
 DATA	http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/annotation.gff&lt;br /&gt;
 DATA:http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/operon.gff&lt;br /&gt;
&lt;br /&gt;
===Example session file===&lt;br /&gt;
&lt;br /&gt;
 ##GenomeView session -- DO NOT DELETE THIS LINE&lt;br /&gt;
 CONFIG http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/tbconfig.txt&lt;br /&gt;
 ALIAS MT_H37RV_V2=MyTBGenome&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 PREFIX http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/&lt;br /&gt;
 DATA annotation.gff&lt;br /&gt;
 DATA operon.gff&lt;br /&gt;
 DATA sRNA.gff&lt;br /&gt;
 DATA rRNA.gff&lt;br /&gt;
 PREFIX&lt;br /&gt;
 PLUGIN http://www.broadinstitute.org/software/genomeview/resources/save2pdf-1.1.zip&lt;br /&gt;
&lt;br /&gt;
== Starting a session with a launch URL ==&lt;br /&gt;
&lt;br /&gt;
Important: You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
== Hiding the session URL ==&lt;br /&gt;
Typically you don't even have to expose this URL and you can use a simple PHP script index.php that redirects to that location.&lt;br /&gt;
For example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;header(&amp;quot;Location: http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&amp;quot;);&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10090</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10090"/>
		<updated>2013-11-15T23:40:15Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL' or alternatively you can call 'setInstructAllInstancesGV()'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. This could be used to check whether there is already a GenomeView instance launched and based on that information start an instance or load the data into the existing one.&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10089</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10089"/>
		<updated>2013-11-15T23:39:01Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL' or alternatively you can call 'setInstructAllInstancesGV()'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10088</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10088"/>
		<updated>2013-11-15T23:38:39Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10087</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10087"/>
		<updated>2013-11-15T23:38:14Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
rkup here&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10086</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10086"/>
		<updated>2013-11-15T23:38:00Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Controlling GenomeView using JavaScript (recommended) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Enter the HTML ma&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
rkup here&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10085</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10085"/>
		<updated>2013-11-15T23:37:47Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
Include the GenomeView javascript file into your HTML page&lt;br /&gt;
 &amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
By default the instructions will only work with the GenomeView instance that was launched from the same page with launchGV() instruction. To override this behavior you can set the instanceID to 'ALL'&lt;br /&gt;
 &amp;lt;script&amp;gt;instanceID='ALL'&amp;lt;/script&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Enter the HTML ma&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(command line)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
rkup here&lt;br /&gt;
&lt;br /&gt;
== Examples ==&lt;br /&gt;
&lt;br /&gt;
=== launchGV(command line)===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10084</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10084"/>
		<updated>2013-11-15T23:35:03Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
&lt;br /&gt;
Enter the HTML ma&lt;br /&gt;
{| &lt;br /&gt;
! Instruction&lt;br /&gt;
! Description&lt;br /&gt;
|- &lt;br /&gt;
| launchGV(url)&lt;br /&gt;
| Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;. See &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| loadGV(url)&lt;br /&gt;
| Load the data at the specified url&lt;br /&gt;
|- &lt;br /&gt;
| unloadGV()&lt;br /&gt;
| Unload all data that is currently loaded&lt;br /&gt;
|- &lt;br /&gt;
| sessionGV(url)&lt;br /&gt;
| Load the GenomeView session at the specified URL&lt;br /&gt;
|- &lt;br /&gt;
| positionGV(position)&lt;br /&gt;
| Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt;&lt;br /&gt;
|- &lt;br /&gt;
| isAlive(callback)&lt;br /&gt;
| Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&lt;br /&gt;
|- &lt;br /&gt;
| setInstanceID(id)&lt;br /&gt;
| Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&lt;br /&gt;
|- &lt;br /&gt;
| setInstructAllInstancesGV&lt;br /&gt;
| Any commands after this function call will be send to all GenomeView instances&lt;br /&gt;
|}&lt;br /&gt;
rkup here&lt;br /&gt;
&amp;lt;p&amp;gt;Deprecated legacy instructions.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;startGV(gv_url,gv_loc, gv_config,gv_extra,a_width,a_height )&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Start regular applet with the parameters described above&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;startMiniGV(gv_url,gv_loc, gv_config,gv_extra,a_width,a_height )&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Start minimal applet with the parameters as described above. The minimal applet has no side bar and no menu&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Controlling GenomeView webstart using JavaScript&amp;lt;/h2&amp;gt;&lt;br /&gt;
Include the GenomeView javascript file&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
In java script, set &amp;lt;code&amp;gt;instanceID='ALL'&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Assuming there is a GenomeView webstart instance started, You can now use the java script methods described above to manipulate it.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10083</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10083"/>
		<updated>2013-11-15T23:21:19Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It is '''important''' that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using JavaScript (recommended)==&lt;br /&gt;
We have a &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo&amp;quot;&amp;gt;demo page set up&amp;lt;/a&amp;gt; that showcases the various aspects you may want to use when embedding GenomeView as an applet into your web platform.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Supported instruction set, see the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo&amp;quot;&amp;gt; demo page&amp;lt;/a&amp;gt; for examples on how to use them.&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;launchGV(url)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;. See &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;loadGV(url)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;unloadGV()&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;sessionGV(url)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;positionGV(position)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;isAlive(callback)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;setInstanceID(id)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;setInstructAllInstancesGV&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Any commands after this function call will be send to all GenomeView instances&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Deprecated legacy instructions.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;startGV(gv_url,gv_loc, gv_config,gv_extra,a_width,a_height )&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Start regular applet with the parameters described above&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;startMiniGV(gv_url,gv_loc, gv_config,gv_extra,a_width,a_height )&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Start minimal applet with the parameters as described above. The minimal applet has no side bar and no menu&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Controlling GenomeView webstart using JavaScript&amp;lt;/h2&amp;gt;&lt;br /&gt;
Include the GenomeView javascript file&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
In java script, set &amp;lt;code&amp;gt;instanceID='ALL'&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Assuming there is a GenomeView webstart instance started, You can now use the java script methods described above to manipulate it.&lt;br /&gt;
&lt;br /&gt;
==Controlling GenomeView using a port==&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10082</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10082"/>
		<updated>2013-11-15T23:09:31Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Setting up the configuration file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning. These should be one row per session, i.e. per data set.&lt;br /&gt;
&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for session, should be reasonably short and informative people&lt;br /&gt;
# display image for session, this should be a URL&lt;br /&gt;
# description text for individual session, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
An example row could be:&lt;br /&gt;
{|&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis&lt;br /&gt;
|http://genomeview.org/manual/images/6/69/Gv_logo-96px.png&lt;br /&gt;
|Fusobacterium nucleatum animalis is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;http://myuniversity.org/fusobacterium/Fuso_animalis.session&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setting up the configuration file ==&lt;br /&gt;
In order to work with the new repository file, you need to create a config file that specifies where GenomeView has to look for it.&lt;br /&gt;
&lt;br /&gt;
The key options you need to set are:&lt;br /&gt;
 # Make sure the Genome Explorer is enabled&lt;br /&gt;
 general:enableGenomeExplorer=true&lt;br /&gt;
 # Point GenomeView to your repository&lt;br /&gt;
 external:repository=&amp;lt;URL&amp;gt;&lt;br /&gt;
 # Provide display names for the repository identifier you used in the first column&lt;br /&gt;
 external:repository:labels=&amp;lt;repository identifier&amp;gt;:&amp;lt;repository display name&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For each repository identifier you also need to fill out the description field:&lt;br /&gt;
 external:repository:description:&amp;lt;repository identifier&amp;gt;=&amp;lt;long HTML formatted description&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;external:repository=http://myuniversity.org/my/repository/file.txt&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 external:repository:labels=fusobac:Fusobacterium Repository&lt;br /&gt;
 external:repository:description:fusobac=Welcome to the Fusobacterium GenomeView portal. Blah blah blah...&lt;br /&gt;
&lt;br /&gt;
== Setting up launch URL ==&lt;br /&gt;
The final step is to start GenomeView with this configuration file. Suppose you make the config file available at &amp;lt;nowiki&amp;gt;http://myuniversity.org/my/repository/config.txt&amp;lt;/nowiki&amp;gt;, then the launch URL would be:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--config http://myuniversity.org/my/repository/config.txt&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10081</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10081"/>
		<updated>2013-11-15T23:07:39Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Setting up the configuration file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning. These should be one row per session, i.e. per data set.&lt;br /&gt;
&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for session, should be reasonably short and informative people&lt;br /&gt;
# display image for session, this should be a URL&lt;br /&gt;
# description text for individual session, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
An example row could be:&lt;br /&gt;
{|&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis&lt;br /&gt;
|http://genomeview.org/manual/images/6/69/Gv_logo-96px.png&lt;br /&gt;
|Fusobacterium nucleatum animalis is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;http://myuniversity.org/fusobacterium/Fuso_animalis.session&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setting up the configuration file ==&lt;br /&gt;
In order to work with the new repository file, you need to create a config file that specifies where GenomeView has to look for it.&lt;br /&gt;
&lt;br /&gt;
The key options you need to set are:&lt;br /&gt;
 # Make sure the Genome Explorer is enabled&lt;br /&gt;
 general:enableGenomeExplorer=true&lt;br /&gt;
 # Point GenomeView to your repository&lt;br /&gt;
 external:repository=&amp;lt;URL&amp;gt;&lt;br /&gt;
 # Provide display names for the repository identifier you used in the first column&lt;br /&gt;
 external:repository:labels=&amp;lt;repository identifier&amp;gt;:&amp;lt;repository display name&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For each repository identifier you also need to fill out the description field:&lt;br /&gt;
 external:repository:description:&amp;lt;repository identifier&amp;gt;=&amp;lt;long HTML formatted description&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
 external:repository=http://myuniversity.org/my/repository/file.txt&lt;br /&gt;
 external:repository:labels=fusobac:Fusobacterium Repository&lt;br /&gt;
 external:repository:description:fusobac=Welcome to the Fusobacterium GenomeView portal. Blah blah blah...&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10080</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10080"/>
		<updated>2013-11-15T23:07:24Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning. These should be one row per session, i.e. per data set.&lt;br /&gt;
&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for session, should be reasonably short and informative people&lt;br /&gt;
# display image for session, this should be a URL&lt;br /&gt;
# description text for individual session, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
An example row could be:&lt;br /&gt;
{|&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis&lt;br /&gt;
|http://genomeview.org/manual/images/6/69/Gv_logo-96px.png&lt;br /&gt;
|Fusobacterium nucleatum animalis is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;http://myuniversity.org/fusobacterium/Fuso_animalis.session&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Setting up the configuration file ==&lt;br /&gt;
In order to work with the new repository file, you need to create a config file that specifies where GenomeView has to look for it.&lt;br /&gt;
&lt;br /&gt;
The key options you need to set are:&lt;br /&gt;
 # Make sure the Genome Explorer is enabled&lt;br /&gt;
 general:enableGenomeExplorer=true&lt;br /&gt;
 # Point GenomeView to your repository&lt;br /&gt;
 external:repository=&amp;lt;URL&amp;gt;&lt;br /&gt;
 # Provide display names for the repository identifier you used in the first column&lt;br /&gt;
 external:repository:labels=&amp;lt;repository identifier&amp;gt;:&amp;lt;repository display name&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For each repository identifier you also need to fill out the description field:&lt;br /&gt;
 external:repository:description:&amp;lt;repository identifier&amp;gt;=&amp;lt;long HTML formatted description&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
external:repository=http://myuniversity.org/my/repository/file.txt&lt;br /&gt;
external:repository:labels=fusobac:Fusobacterium Repository&lt;br /&gt;
external:repository:description:fusobac=Welcome to the Fusobacterium GenomeView portal. Blah blah blah...&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10079</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10079"/>
		<updated>2013-11-15T22:55:53Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Repository file format */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning. These should be one row per session, i.e. per data set.&lt;br /&gt;
&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for session, should be reasonably short and informative people&lt;br /&gt;
# display image for session, this should be a URL&lt;br /&gt;
# description text for individual session, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
An example row could be:&lt;br /&gt;
{|&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/broadlogo.png&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191 is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/Fuso_animalis_ATCC51191.session&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10078</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10078"/>
		<updated>2013-11-15T22:55:00Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Repository file format */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning.&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for repository, should be reasonably short and informative people&lt;br /&gt;
# display image for repository, this should be a URL&lt;br /&gt;
# description text, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
An example row could be:&lt;br /&gt;
{|&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/broadlogo.png&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191 is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/Fuso_animalis_ATCC51191.session&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10077</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10077"/>
		<updated>2013-11-15T22:54:34Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Repository file format */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning.&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for repository, should be reasonably short and informative people&lt;br /&gt;
# display image for repository, this should be a URL&lt;br /&gt;
# description text, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
For example &lt;br /&gt;
{|&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/broadlogo.png&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191 is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/Fuso_animalis_ATCC51191.session&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10076</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10076"/>
		<updated>2013-11-15T22:54:01Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Repository file format */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning.&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for repository, should be reasonably short and informative people&lt;br /&gt;
# display image for repository, this should be a URL&lt;br /&gt;
# description text, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
For example &lt;br /&gt;
{-&lt;br /&gt;
|fusobac&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/broadlogo.png&lt;br /&gt;
|Fusobacterium nucleatum animalis ATCC51191 is from a colon sample.  This strain was sequenced at Baylor College of Medicine.&lt;br /&gt;
|http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/Fuso_animalis_ATCC51191.session&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10075</id>
		<title>Setting up a Genome Explorer repository</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Setting_up_a_Genome_Explorer_repository&amp;diff=10075"/>
		<updated>2013-11-15T22:53:22Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: Created page with &amp;quot;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the Genome Explorer  == Recipe ==  # Set up a repository file # Set u...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GenomeView allows you to set up a custom repository of genomes that will be loaded as primary view in the [[Genome Explorer]]&lt;br /&gt;
&lt;br /&gt;
== Recipe ==&lt;br /&gt;
&lt;br /&gt;
# Set up a repository file&lt;br /&gt;
# Set up configuration file &lt;br /&gt;
# Make launch URL &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Repository file format ==&lt;br /&gt;
The repository file is a tab-delimited file where each column has a special meaning.&lt;br /&gt;
# repository identifier&lt;br /&gt;
# display name for repository, should be reasonably short and informative people&lt;br /&gt;
# display image for repository, this should be a URL&lt;br /&gt;
# description text, this can be html code.&lt;br /&gt;
# url to the session file.&lt;br /&gt;
&lt;br /&gt;
For example &lt;br /&gt;
 fusobac	Fusobacterium nucleatum animalis ATCC51191	http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/broadlogo.png	Fusobacterium nucleatum animalis ATCC51191 is from a colon sample.  This strain was sequenced at Baylor College of Medicine.	http://www.broadinstitute.org/software/genomeview/supplemental/fusobacterium/Fuso_animalis_ATCC51191.session&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=10074</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Main_Page&amp;diff=10074"/>
		<updated>2013-11-15T22:44:47Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC|align=right}}&lt;br /&gt;
&lt;br /&gt;
Welcome to the GenomeView manual. These pages aim to answer any questions you may have as an end-user, a platform-user or as a contributing developer.&lt;br /&gt;
&lt;br /&gt;
This documentation is completely open for anyone to contribute to, just click the edit-button near the top and you can help make this a better resource for everyone.&lt;br /&gt;
&lt;br /&gt;
Feel free to copy documentation from the old manual to here, there are still some pages that need to be transferred and we're happy with any help you can spare.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== [[Quick start|Getting started with GenomeView in 5 minutes]] ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=User manual}}&lt;br /&gt;
These manual pages describe how to use GenomeView and how to prepare your data to be usable in GenomeView.&lt;br /&gt;
&lt;br /&gt;
[[Starting GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Preparing and loading data]] -- [[Preloaded data]]&lt;br /&gt;
&lt;br /&gt;
[[Navigation]] -- [[Keyboard short-cuts]]&lt;br /&gt;
&lt;br /&gt;
[[Visualizations]]&lt;br /&gt;
&lt;br /&gt;
[[Search for...]]&lt;br /&gt;
&lt;br /&gt;
[[Manipulating and configuring the views]]&lt;br /&gt;
&lt;br /&gt;
[[Editing annotations]]&lt;br /&gt;
&lt;br /&gt;
[[Exporting data and saving changes]]&lt;br /&gt;
&lt;br /&gt;
[[More functionality with plugins]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Getting help}}&lt;br /&gt;
&lt;br /&gt;
[[Frequently asked questions]]&lt;br /&gt;
&lt;br /&gt;
[[I have a problem, help me, please]]&lt;br /&gt;
&lt;br /&gt;
[[Report a bug or request a feature]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:left;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Platform-user manual}}&lt;br /&gt;
These manual pages describe how to integrate GenomeView with your web-based platform or how to communicate with GenomeView from 3-rd party software. &lt;br /&gt;
&lt;br /&gt;
[[Using GenomeView from the command-line]]&lt;br /&gt;
&lt;br /&gt;
[[Integration]]&lt;br /&gt;
&lt;br /&gt;
[[Session files]] -- [[Configuration options]]&lt;br /&gt;
&lt;br /&gt;
[[Communicating with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Programming with GenomeView]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up authentication and encryption]]&lt;br /&gt;
&lt;br /&gt;
[[Making a plugin]]&lt;br /&gt;
&lt;br /&gt;
[[Integrating GenomeView as an editor]]&lt;br /&gt;
&lt;br /&gt;
[[Setting up a Genome Explorer repository]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;float:right;width:49%&amp;quot;&amp;gt;&lt;br /&gt;
{{Box-header|title=Developer manual}}&lt;br /&gt;
These pages are aimed towards contributors to GenomeView and developers who work directly on the GenomeView code.&lt;br /&gt;
&lt;br /&gt;
Currently most of this documentation lives on [https://sourceforge.net/p/genomeview/wiki/ Sourceforge].&lt;br /&gt;
&lt;br /&gt;
[[Unit test example data files]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear:both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=10073</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=10073"/>
		<updated>2013-11-15T22:25:34Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Present your data through a Java Web Start link */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
==General considerations==&lt;br /&gt;
To present your data in GenomeView optimally, there are a number of things you have to keep in mind.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Indexing===&lt;br /&gt;
Please follow the recommendation in the [[recommended file formats]] page.&lt;br /&gt;
&lt;br /&gt;
You will want to &amp;lt;a href=&amp;quot;/content/preparing-fasta-files&amp;quot;&amp;gt;index your reference sequence&amp;lt;/a&amp;gt; to reduce loading times.&lt;br /&gt;
&lt;br /&gt;
You may want to index annotation files, but this is not recommended unless they are over 10 Mb when compressed with gzip because you will loose structural information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;To load an indexed file, you point GenomeView to the main file and GenomeView will try to find the index by itself. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Compression===&lt;br /&gt;
&amp;lt;p&amp;gt;GenomeView supports GZIP compression transparently on all non-indexed file formats, i.e. compression and indexing are mutually exclusive. However as part of the indexing process, many file formats will be compressed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Short read data&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Depending on what information you want to get out of the visualization, there are basically two ways to load short read data. The first one is the &amp;lt;a href=&amp;quot;/content/short-read-track&amp;quot;&amp;gt;Short Read Track&amp;lt;/a&amp;gt; which will give you a detailed view with all individual reads. The second one is the &amp;lt;a href=&amp;quot;/content/pile-track&amp;quot;&amp;gt;Pile up track&amp;lt;/a&amp;gt; which will give a more of a summary view/ coverage plot based on your sequence reads. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-short-read-alignments&amp;quot;&amp;gt;Instructions to prepare data for the short read track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-pileup&amp;quot;&amp;gt;Instructions to prepare data for the pile up track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start link==&lt;br /&gt;
The fastest and simplest way to get started and with integrating GenomeView with your data is by directly constructing a webstart link.&lt;br /&gt;
&lt;br /&gt;
The default launch URL is located at http://genomeview.org/start/launch.jnlp. If you require a specific version, there are stable URLs available from the [[supported versions]] page.&lt;br /&gt;
&lt;br /&gt;
The next step is constructing your URL to load sequence and features. Below a sample URL, which will load some sequence with annotation and some short reads. It will start with the [100000,200000] region visible.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--position 100000:200000 --url http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.fasta http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.gff.gz http://www.broadinstitute.org/software/genomeview/demo/c_elegans/uwgs-rw_L2_FC6218_3.CHROMOSOME_IV.sorted.bam.bai&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pasting this URL in your browser will start GenomeView with data from C. elegans loaded.&lt;br /&gt;
&lt;br /&gt;
[[Command line options]] to GenomeView can be added after the question mark after the installation URL.&lt;br /&gt;
&lt;br /&gt;
The formalized version of the integration URL looks like this:&lt;br /&gt;
&lt;br /&gt;
 http://genomeview.org/start/launch.jnlp?[command line options for GenomeView seperated with spaces]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Important:''' You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start session (recommended)==&lt;br /&gt;
A [[session file]] is a text file that contains instructions for GenomeView on which data to load and how to configure itself. &lt;br /&gt;
&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Embedding GenomeView as an applet==&lt;br /&gt;
&amp;lt;div style=&amp;quot;color:red&amp;quot;&amp;gt;Support for the applet version of GenomeView is currently on hold due to ever changing Java support from the various browser and OS vendors. It is impossible to maintain any semblance of stability. All of the material below may or may not work.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The key code that needs to be included in the body of your web page is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://www.java.com/js/deployJava.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://genomeview.org/start/genomeview.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot;&amp;amp;gt;&lt;br /&gt;
    	var gv_url		= null;&lt;br /&gt;
     	var gv_config	= 'http://genomeview.org/jsdemo/democonfig.txt';    &lt;br /&gt;
     	var gv_extra	= null;&lt;br /&gt;
       	var gv_location	= null;&lt;br /&gt;
        startGV(gv_url,gv_location,gv_config,gv_extra,500,400);&lt;br /&gt;
&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The &amp;lt;code&amp;gt;gv_url&amp;lt;/code&amp;gt; can be used to pre-load a reference sequence. This file will be loaded first and only then will GenomeView proceed with loading additional data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The configuration file you want to use, can be specified using the &amp;lt;code&amp;gt;gv_config&amp;lt;/code&amp;gt; option.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;All other data that you want to have loaded can be specified in a space separated list in &amp;lt;code&amp;gt;gv_extra&amp;lt;/code&amp;gt;. These data sets will be loaded in parallel.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The location that will initially be visible, can be set by &amp;lt;code&amp;gt;gv_location&amp;lt;/code&amp;gt;. The position is in the format &amp;amp;lt;entry&amp;amp;gt;:&amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt; The entry part is optional can be omitted in which case it becomes &amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Note: we strongly recommend you use the genomeview.js we provide as that's the one we keep up to date with progressing releases.&amp;lt;/em&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Integration&amp;diff=10072</id>
		<title>Integration</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Integration&amp;diff=10072"/>
		<updated>2013-11-15T22:24:34Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Present your data through a Java Web Start link */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://genomeview.org/content/integration&lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integrating-genomeview-editor&amp;quot;&amp;gt;Integrating as editor&amp;lt;/a&amp;gt; and &amp;lt;a href=&amp;quot;/content/communicating-genomeview&amp;quot;&amp;gt;Communicating with GenomeView&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This page tries to explain how to integrate GenomeView in your website with your data. You can either make it available through Java Webstart, or as an applet. Whenever possible we recommend using Java Web &lt;br /&gt;
Start as it has better cross-platform and cross-browser support.&lt;br /&gt;
&lt;br /&gt;
==General considerations==&lt;br /&gt;
To present your data in GenomeView optimally, there are a number of things you have to keep in mind.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Indexing===&lt;br /&gt;
Please follow the recommendation in the [[recommended file formats]] page.&lt;br /&gt;
&lt;br /&gt;
You will want to &amp;lt;a href=&amp;quot;/content/preparing-fasta-files&amp;quot;&amp;gt;index your reference sequence&amp;lt;/a&amp;gt; to reduce loading times.&lt;br /&gt;
&lt;br /&gt;
You may want to index annotation files, but this is not recommended unless they are over 10 Mb when compressed with gzip because you will loose structural information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;To load an indexed file, you point GenomeView to the main file and GenomeView will try to find the index by itself. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Compression===&lt;br /&gt;
&amp;lt;p&amp;gt;GenomeView supports GZIP compression transparently on all non-indexed file formats, i.e. compression and indexing are mutually exclusive. However as part of the indexing process, many file formats will be compressed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Short read data&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Depending on what information you want to get out of the visualization, there are basically two ways to load short read data. The first one is the &amp;lt;a href=&amp;quot;/content/short-read-track&amp;quot;&amp;gt;Short Read Track&amp;lt;/a&amp;gt; which will give you a detailed view with all individual reads. The second one is the &amp;lt;a href=&amp;quot;/content/pile-track&amp;quot;&amp;gt;Pile up track&amp;lt;/a&amp;gt; which will give a more of a summary view/ coverage plot based on your sequence reads. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-short-read-alignments&amp;quot;&amp;gt;Instructions to prepare data for the short read track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;a href=&amp;quot;/content/preparing-pileup&amp;quot;&amp;gt;Instructions to prepare data for the pile up track&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start link==&lt;br /&gt;
The fastest and simplest way to get started and with integrating GenomeView with your data is by directly constructing a webstart link.&lt;br /&gt;
&lt;br /&gt;
The default launch URL is located at http://genomeview.org/start/launch.jnlp. For most integration works I would strongly suggest using this installation. If you require a specific version, there are stable URLs available from the [[supported versions]] page.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The next step is constructing your URL to load sequence and features. Below a sample URL, which will load some sequence with annotation and some short reads. It will start with the [100000,200000] region visible.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--position 100000:200000 --url http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.fasta http://www.broadinstitute.org/software/genomeview/demo/c_elegans/IV.gff.gz http://www.broadinstitute.org/software/genomeview/demo/c_elegans/uwgs-rw_L2_FC6218_3.CHROMOSOME_IV.sorted.bam.bai&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pasting this URL in your browser will start GenomeView with data from C. elegans loaded.&lt;br /&gt;
&lt;br /&gt;
[[Command line options]] to GenomeView can be added after the question mark after the installation URL.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;So the formalized version of the integration URL looks like this:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
http://genomeview.org/start/launch.jnlp?[command line options for GenomeView seperated with spaces]&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;Important:&amp;lt;/b&amp;gt;You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
==Present your data through a Java Web Start session (recommended)==&lt;br /&gt;
A [[session file]] is a text file that contains instructions for GenomeView on which data to load and how to configure itself. &lt;br /&gt;
&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Embedding GenomeView as an applet==&lt;br /&gt;
&amp;lt;div style=&amp;quot;color:red&amp;quot;&amp;gt;Support for the applet version of GenomeView is currently on hold due to ever changing Java support from the various browser and OS vendors. It is impossible to maintain any semblance of stability. All of the material below may or may not work.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The key code that needs to be included in the body of your web page is:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://www.java.com/js/deployJava.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot; src=&amp;amp;quot;http://genomeview.org/start/genomeview.js&amp;amp;quot;&amp;amp;gt;&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;amp;lt;script type=&amp;amp;quot;text/javascript&amp;amp;quot;&amp;amp;gt;&lt;br /&gt;
    	var gv_url		= null;&lt;br /&gt;
     	var gv_config	= 'http://genomeview.org/jsdemo/democonfig.txt';    &lt;br /&gt;
     	var gv_extra	= null;&lt;br /&gt;
       	var gv_location	= null;&lt;br /&gt;
        startGV(gv_url,gv_location,gv_config,gv_extra,500,400);&lt;br /&gt;
&amp;amp;lt;/script&amp;amp;gt;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The &amp;lt;code&amp;gt;gv_url&amp;lt;/code&amp;gt; can be used to pre-load a reference sequence. This file will be loaded first and only then will GenomeView proceed with loading additional data.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The configuration file you want to use, can be specified using the &amp;lt;code&amp;gt;gv_config&amp;lt;/code&amp;gt; option.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;All other data that you want to have loaded can be specified in a space separated list in &amp;lt;code&amp;gt;gv_extra&amp;lt;/code&amp;gt;. These data sets will be loaded in parallel.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;The location that will initially be visible, can be set by &amp;lt;code&amp;gt;gv_location&amp;lt;/code&amp;gt;. The position is in the format &amp;amp;lt;entry&amp;amp;gt;:&amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt; The entry part is optional can be omitted in which case it becomes &amp;amp;lt;start position&amp;amp;gt;:&amp;amp;lt;end position&amp;amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;em&amp;gt;Note: we strongly recommend you use the genomeview.js we provide as that's the one we keep up to date with progressing releases.&amp;lt;/em&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10071</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10071"/>
		<updated>2013-11-15T22:23:21Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Configuring track aliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is [http://sourceforge.net/p/genomeview/genomeview-code/ci/master/tree/resources/conf/default.conf available from the code repository] and should be considered the primary source of information regarding configuration options. &lt;br /&gt;
&lt;br /&gt;
== Configuring track order ==&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&lt;br /&gt;
 track:weight:gene=1&lt;br /&gt;
 track:weight:mRNA=2&lt;br /&gt;
 track:weight:CDS=3&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
 track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
 track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
== Configuring track visibility ==&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&lt;br /&gt;
 track:visible:gene=true&lt;br /&gt;
 track:visible:mRNA=false&lt;br /&gt;
 track:visible:CDS=true&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  &amp;lt;nowiki&amp;gt;track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Configuring track aliases==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
 track:alias:gene=All the genes&lt;br /&gt;
 track:alias:mRNA=MRNA track&lt;br /&gt;
 track:alias:CDS=Coding sequence features&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: Track aliases are unrelated to aliases set up in the session file with the ALIAS command. You can make a track alias in a session file with the OPTION command:&lt;br /&gt;
 OPTION track:alias:gene=All the genes&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10070</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10070"/>
		<updated>2013-11-15T22:23:00Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Configuring track visibility */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is [http://sourceforge.net/p/genomeview/genomeview-code/ci/master/tree/resources/conf/default.conf available from the code repository] and should be considered the primary source of information regarding configuration options. &lt;br /&gt;
&lt;br /&gt;
== Configuring track order ==&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&lt;br /&gt;
 track:weight:gene=1&lt;br /&gt;
 track:weight:mRNA=2&lt;br /&gt;
 track:weight:CDS=3&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
 track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
 track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
== Configuring track visibility ==&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&lt;br /&gt;
 track:visible:gene=true&lt;br /&gt;
 track:visible:mRNA=false&lt;br /&gt;
 track:visible:CDS=true&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  &amp;lt;nowiki&amp;gt;track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Configuring track aliases==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
 track:alias:gene=All the genes&lt;br /&gt;
 track:alias:mRNA=MRNA track&lt;br /&gt;
 track:alias:CDS=Coding sequence features&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
 track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: Track aliases are unrelated to aliases set up in the session file with the ALIAS command. You can make a track alias in a session file with the OPTION command:&lt;br /&gt;
 OPTION track:alias:gene=All the genes&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10069</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10069"/>
		<updated>2013-11-15T22:22:30Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Configuring track aliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is [http://sourceforge.net/p/genomeview/genomeview-code/ci/master/tree/resources/conf/default.conf available from the code repository] and should be considered the primary source of information regarding configuration options. &lt;br /&gt;
&lt;br /&gt;
== Configuring track order ==&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&lt;br /&gt;
 track:weight:gene=1&lt;br /&gt;
 track:weight:mRNA=2&lt;br /&gt;
 track:weight:CDS=3&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
 track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
 track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
== Configuring track visibility ==&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&lt;br /&gt;
 track:visible:gene=true&lt;br /&gt;
 track:visible:mRNA=false&lt;br /&gt;
 track:visible:CDS=true&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&lt;br /&gt;
 track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&lt;br /&gt;
&lt;br /&gt;
==Configuring track aliases==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
 track:alias:gene=All the genes&lt;br /&gt;
 track:alias:mRNA=MRNA track&lt;br /&gt;
 track:alias:CDS=Coding sequence features&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
 track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note: Track aliases are unrelated to aliases set up in the session file with the ALIAS command. You can make a track alias in a session file with the OPTION command:&lt;br /&gt;
 OPTION track:alias:gene=All the genes&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10068</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10068"/>
		<updated>2013-11-15T22:22:09Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Configuring track visibility */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is [http://sourceforge.net/p/genomeview/genomeview-code/ci/master/tree/resources/conf/default.conf available from the code repository] and should be considered the primary source of information regarding configuration options. &lt;br /&gt;
&lt;br /&gt;
== Configuring track order ==&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&lt;br /&gt;
 track:weight:gene=1&lt;br /&gt;
 track:weight:mRNA=2&lt;br /&gt;
 track:weight:CDS=3&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
 track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
 track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
== Configuring track visibility ==&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&lt;br /&gt;
 track:visible:gene=true&lt;br /&gt;
 track:visible:mRNA=false&lt;br /&gt;
 track:visible:CDS=true&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
 track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&lt;br /&gt;
 track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&lt;br /&gt;
&lt;br /&gt;
==Configuring track aliases==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:gene=All the genes&lt;br /&gt;
track:alias:mRNA=MRNA track&lt;br /&gt;
track:alias:CDS=Coding sequence features&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: Track aliases are unrelated to aliases set up in the session file with the ALIAS command. You can make a track alias in a session file with the OPTION command:&lt;br /&gt;
 OPTION track:alias:gene=All the genes&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10067</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10067"/>
		<updated>2013-11-15T22:21:52Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Configuring track order */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is [http://sourceforge.net/p/genomeview/genomeview-code/ci/master/tree/resources/conf/default.conf available from the code repository] and should be considered the primary source of information regarding configuration options. &lt;br /&gt;
&lt;br /&gt;
== Configuring track order ==&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&lt;br /&gt;
 track:weight:gene=1&lt;br /&gt;
 track:weight:mRNA=2&lt;br /&gt;
 track:weight:CDS=3&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
 track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
 track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
 track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
== Configuring track visibility ==&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:gene=true&lt;br /&gt;
track:visible:mRNA=false&lt;br /&gt;
track:visible:CDS=true&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Configuring track aliases==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:gene=All the genes&lt;br /&gt;
track:alias:mRNA=MRNA track&lt;br /&gt;
track:alias:CDS=Coding sequence features&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: Track aliases are unrelated to aliases set up in the session file with the ALIAS command. You can make a track alias in a session file with the OPTION command:&lt;br /&gt;
 OPTION track:alias:gene=All the genes&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10066</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10066"/>
		<updated>2013-11-15T21:52:25Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is [http://sourceforge.net/p/genomeview/genomeview-code/ci/master/tree/resources/conf/default.conf available from the code repository] and should be considered the primary source of information regarding configuration options. &lt;br /&gt;
&lt;br /&gt;
== Configuring track order ==&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&lt;br /&gt;
 track:weight:gene=1&lt;br /&gt;
 track:weight:mRNA=2&lt;br /&gt;
 track:weight:CDS=3&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackvisibility&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
== Configuring track visibility ==&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:gene=true&lt;br /&gt;
track:visible:mRNA=false&lt;br /&gt;
track:visible:CDS=true&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Configuring track aliases==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:gene=All the genes&lt;br /&gt;
track:alias:mRNA=MRNA track&lt;br /&gt;
track:alias:CDS=Coding sequence features&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: Track aliases are unrelated to aliases set up in the session file with the ALIAS command. You can make a track alias in a session file with the OPTION command:&lt;br /&gt;
 OPTION track:alias:gene=All the genes&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10065</id>
		<title>Session files</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10065"/>
		<updated>2013-11-15T21:51:58Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Session files allow you to organize a large number of data files and config options in a single file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An example session file:&lt;br /&gt;
 http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&lt;br /&gt;
&lt;br /&gt;
You can use 'View source', or something similar, in your browser to see the actual file structure. It is a plain text file with on each line a file that needs to be loaded.&lt;br /&gt;
&lt;br /&gt;
==File structure ==&lt;br /&gt;
&lt;br /&gt;
===Header===&lt;br /&gt;
Make sure the file starts with a line that contains the words 'GenomeView' and 'session'. These two words have to be on the first line!&lt;br /&gt;
&lt;br /&gt;
We recommend:&lt;br /&gt;
 ##GenomeView session&lt;br /&gt;
&lt;br /&gt;
This header is used to detect the file format by GenomeView.&lt;br /&gt;
&lt;br /&gt;
=== Body ===&lt;br /&gt;
&lt;br /&gt;
The remainder of the file contains lines that have various instructions to load data, configure GenomeView or load plugins. The table below has an overview of all options.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
!Instruction*&lt;br /&gt;
!Value&lt;br /&gt;
|-&lt;br /&gt;
|CONFIG&lt;br /&gt;
|URL or local file path to the configuration file. This line should be the first in the session file, otherwise some data may not have the correct configuration file when initializing.&lt;br /&gt;
|-&lt;br /&gt;
|DATA**	&lt;br /&gt;
|URL or local file path for a data file. This file will be loaded. You do not need to specify the index, GenomeView will look for it in the same folder.&lt;br /&gt;
|-&lt;br /&gt;
|PREFIX	&lt;br /&gt;
|URL or local file path prefix. The value of this instructions will be prepended to any DATA, PLUGIN or CONFIG pairs that follow this instruction. A PREFIX values is only valid for subsequent DATA, PLUGIN and CONFIG pairs. This can to simplify loading many files from multiple locations. To reset the PREFIX, you can use an empty value. You can use multiple PREFIX instructions through-out the session, they will each be valid for the following DATA, PLUGIN and CONFIG instructions, until reset with an alternative value.&lt;br /&gt;
|-&lt;br /&gt;
|OPTION	&lt;br /&gt;
|Key=value definition of a single configuration option. This is suited to override a few config options as needed.&lt;br /&gt;
|-&lt;br /&gt;
|ALIAS	[primary name]=[display name]. &lt;br /&gt;
|Add an additional synonym for an Entry (chromosome). This can be useful if your data has different identifiers for the same sequence in different files. The primary name will be used to connect the data types. Multiple primary names can point to the display name, in that case you can use the aliases to connect multiple different IDs.&lt;br /&gt;
|-&lt;br /&gt;
|LOCATION&lt;br /&gt;
|Set the visible location to the specified location. The location needs to be specified [entry]:[start position]-[end position].&lt;br /&gt;
|-&lt;br /&gt;
|PLUGIN	&lt;br /&gt;
|Allows you to request the user to automatically install a plugin. The plugin needs to be specified as a URL to the zip file. You can use relative names in conjunction with the PREFIX parameter&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 ** The legacy keywords C, U and F will continue to work.&lt;br /&gt;
&lt;br /&gt;
Each of the lines should be organized like this:&lt;br /&gt;
 instruction[tab, colon or space]value&lt;br /&gt;
&lt;br /&gt;
For example, all of these are valid ways to specify a file&lt;br /&gt;
 DATA	http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/annotation.gff&lt;br /&gt;
 DATA:http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/operon.gff&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Important: You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
===Example session file===&lt;br /&gt;
&lt;br /&gt;
 ##GenomeView session -- DO NOT DELETE THIS LINE&lt;br /&gt;
 CONFIG http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/tbconfig.txt&lt;br /&gt;
 ALIAS MT_H37RV_V2=MyTBGenome&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 PREFIX http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/&lt;br /&gt;
 DATA annotation.gff&lt;br /&gt;
 DATA operon.gff&lt;br /&gt;
 DATA sRNA.gff&lt;br /&gt;
 DATA rRNA.gff&lt;br /&gt;
 PREFIX&lt;br /&gt;
 PLUGIN http://www.broadinstitute.org/software/genomeview/resources/save2pdf-1.1.zip&lt;br /&gt;
&lt;br /&gt;
== Starting a session with a launch URL ==&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
== Hiding the session URL ==&lt;br /&gt;
Typically you don't even have to expose this URL and you can use a simple PHP script index.php that redirects to that location.&lt;br /&gt;
For example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;header(&amp;quot;Location: http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&amp;quot;);&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10064</id>
		<title>Communicating with GenomeView</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Communicating_with_GenomeView&amp;diff=10064"/>
		<updated>2013-11-15T21:43:50Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;i&amp;gt;Other topics that may be of interest: &amp;lt;a href=&amp;quot;/content/integration&amp;quot;&amp;gt;Integrating GenomeView as viewer&amp;lt;/a&amp;gt;&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Whatever way of communicating you choose, make sure you enable it in the configuration file!&lt;br /&gt;
&lt;br /&gt;
It is &amp;lt;b&amp;gt;important&amp;lt;/b&amp;gt; that you set &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt; in your configuration file. Only if you add that line to the configuration file you specify, will communication work.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Controlling GenomeView applet using JavaScript&amp;lt;/h2&amp;gt;&lt;br /&gt;
We have a &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo&amp;quot;&amp;gt;demo page set up&amp;lt;/a&amp;gt; that showcases the various aspects you may want to use when embedding GenomeView as an applet into your web platform.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Supported instruction set, see the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo&amp;quot;&amp;gt; demo page&amp;lt;/a&amp;gt; for examples on how to use them.&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;launchGV(url)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Launch GenomeView with the file at the specified url as configuration file. If no url is specified an empty config is loaded with &amp;lt;code&amp;gt;integration:monitorJavaScript=true&amp;lt;/code&amp;gt;. See &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;loadGV(url)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;unloadGV()&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;sessionGV(url)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;positionGV(position)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;isAlive(callback)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Check whether a GenomeView instance is alive. &amp;lt;code&amp;gt;callback&amp;lt;/code&amp;gt; should be a javascript function that you define that will be called by the script and will have a variable &amp;lt;code&amp;gt;isAlive&amp;lt;/code&amp;gt; available that you can use. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testalive.html&amp;quot;&amp;gt;example &amp;lt;/a&amp;gt; for more details&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;setInstanceID(id)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Set the GenomeView instance ID to be used in the next functions calls to the supplied argument. This is useful to communicate with multiple GenomeView instances at once. See the &amp;lt;a href=&amp;quot;http://genomeview.org/jsdemo/testlaunch.html&amp;quot;&amp;gt;example&amp;lt;/a&amp;gt; for more details.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;setInstructAllInstancesGV&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Any commands after this function call will be send to all GenomeView instances&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Deprecated legacy instructions.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;startGV(gv_url,gv_loc, gv_config,gv_extra,a_width,a_height )&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Start regular applet with the parameters described above&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;startMiniGV(gv_url,gv_loc, gv_config,gv_extra,a_width,a_height )&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Start minimal applet with the parameters as described above. The minimal applet has no side bar and no menu&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Controlling GenomeView webstart using JavaScript&amp;lt;/h2&amp;gt;&lt;br /&gt;
Include the GenomeView javascript file&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;script type=&amp;quot;text/javascript&amp;quot; src=&amp;quot;http://genomeview.org/start/genomeview.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
In java script, set &amp;lt;code&amp;gt;instanceID='ALL'&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Assuming there is a GenomeView webstart instance started, You can now use the java script methods described above to manipulate it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Controlling GenomeView using a port&amp;lt;/h2&amp;gt;&lt;br /&gt;
The java script is implemented as a local server that listens on port 2223, so you could alternatively directly control GenomeView by sending instructions to that port.&lt;br /&gt;
&lt;br /&gt;
The format of an instruction is &amp;lt;code&amp;gt;GET /genomeview-ALL/[instruction]/[argument]&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
Load the C. elegans demo instance&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Position the current visible window to 10000-20000&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/position/10000:20000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unload all data:&lt;br /&gt;
&amp;lt;code&amp;gt;GET /genomeview-ALL/unload&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Full working example code in Java&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
Socket gv = new Socket(&amp;quot;localhost&amp;quot;, 2223);&lt;br /&gt;
		PrintWriter pw=new PrintWriter(gv.getOutputStream());&lt;br /&gt;
               /*pw.println(&amp;quot;GET /genomeview-ALL/session/http://www.broadinstitute.org/software/genomeview/demo/c_elegans/session.php&amp;quot;);*/&lt;br /&gt;
                //pw.println(&amp;quot;GET /genomeview-ALL/unload&amp;quot;);&lt;br /&gt;
		pw.println(&amp;quot;GET /genomeview-ALL/position/10000:20000&amp;quot;);&lt;br /&gt;
		pw.flush();&lt;br /&gt;
		gv.close();&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Available instructions:&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table&amp;gt;&lt;br /&gt;
&amp;lt;th&amp;gt;Instruction&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Description&amp;lt;/th&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/load/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the data at the specified url&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/unload (no argument)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Unload all data that is currently loaded&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/session/[URL]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Load the GenomeView session at the specified URL&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GET /genomeview-ALL/position/[position]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Move the visible region to the specified location. The position is in the format &amp;lt;code&amp;gt;[entry]:[start position]:[end position]&amp;lt;/code&amp;gt; The entry part is optional can be omitted in which case it becomes &amp;lt;code&amp;gt;[start position]:[end position]&amp;lt;/code&amp;gt; &amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10063</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10063"/>
		<updated>2013-11-15T21:41:26Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are several places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Config files specified in the session file&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line or start-up URLwith the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is &amp;lt;a href=&amp;quot;http://sourceforge.net/p/genomeview/code/HEAD/tree/genomeview/trunk/resources/conf/default.conf&amp;quot;&amp;gt;available from the code repository&amp;lt;/a&amp;gt;. This file is somewhat documented and can provide you some clues as which configuration options are available.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackorder&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;h2&amp;gt;Configuring track order&amp;lt;/h2&amp;gt;&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:gene=1&lt;br /&gt;
track:weight:mRNA=2&lt;br /&gt;
track:weight:CDS=3&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackvisibility&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Configuring track visibility&amp;lt;/h2&amp;gt;&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:gene=true&lt;br /&gt;
track:visible:mRNA=false&lt;br /&gt;
track:visible:CDS=true&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackalias&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;h2&amp;gt;Configuring track aliases&amp;lt;/h2&amp;gt;&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:gene=All the genes&lt;br /&gt;
track:alias:mRNA=MRNA track&lt;br /&gt;
track:alias:CDS=Coding sequence features&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10062</id>
		<title>Configuration options</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Configuration_options&amp;diff=10062"/>
		<updated>2013-11-15T21:38:50Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages discuss how to configure a number of things using the configuration file.&lt;br /&gt;
&lt;br /&gt;
There are three places from where GenomeView tries to load configuration information. It will look in the specified order.&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configuration supplied on the command line with the --config option&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Personal config file. This can be changed through the menu File -&amp;gt; Configuration.&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Default configuration present within the release package&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The default configuration file is &amp;lt;a href=&amp;quot;http://sourceforge.net/p/genomeview/code/HEAD/tree/genomeview/trunk/resources/conf/default.conf&amp;quot;&amp;gt;available from the code repository&amp;lt;/a&amp;gt;. This file is somewhat documented and can provide you some clues as which configuration options are available.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackorder&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;h2&amp;gt;Configuring track order&amp;lt;/h2&amp;gt;&lt;br /&gt;
To configure the order of tracks you can use the &amp;lt;code&amp;gt;track:weight:XXX&amp;lt;/code&amp;gt; configuration option. This will give a weight to each track and heavier tracks will be placed lower on the screen.&lt;br /&gt;
&lt;br /&gt;
For annotation features you have give the type as XXX. You cannot use the file name method below. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:gene=1&lt;br /&gt;
track:weight:mRNA=2&lt;br /&gt;
track:weight:CDS=3&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. You cannot use the method described above.&lt;br /&gt;
&lt;br /&gt;
Some examples for remote files:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=100&lt;br /&gt;
track:weight:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=200&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will also work with local files:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:weight:W:\thomas\rnaseq.bam=400&lt;br /&gt;
track:weight:W:\thomas\chipseq.bam=500&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackvisibility&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Deciding which method to use depends on the type of data: annotation are by type, other data is by file name.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Configuring track visibility&amp;lt;/h2&amp;gt;&lt;br /&gt;
To configure the initial visibility of tracks you can use the &amp;lt;code&amp;gt;track:visible:XXX&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView whether the track is initially visible or hidden&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:gene=true&lt;br /&gt;
track:visible:mRNA=false&lt;br /&gt;
track:visible:CDS=true&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=true&lt;br /&gt;
track:visible:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=false&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;a name=&amp;quot;trackalias&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;&lt;br /&gt;
&amp;lt;h2&amp;gt;Configuring track aliases&amp;lt;/h2&amp;gt;&lt;br /&gt;
To change the name that appears next to each track to something that is more informative than the fully qualified path name, you can use the &amp;lt;code&amp;gt;track:alias:XXX=ALIAS&amp;lt;/code&amp;gt; configuration option. This will tell GenomeView which name it should display&lt;br /&gt;
&lt;br /&gt;
For annotation features you give the type as XXX. For example:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:gene=All the genes&lt;br /&gt;
track:alias:mRNA=MRNA track&lt;br /&gt;
track:alias:CDS=Coding sequence features&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For any other data type, you have to specify the file file name or URL where the data resides. &lt;br /&gt;
&lt;br /&gt;
Some examples:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF7_dir100.bam=Directional RNA-seq MCF 7&lt;br /&gt;
track:alias:http://www.broadinstitute.org/software/genomeview/demo/idea_challenge/Directional_RNAseq/MCF10_dir75.bam=Shorter (75) directional RNA-seq for MCF 10&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10061</id>
		<title>Session files</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10061"/>
		<updated>2013-11-15T21:03:02Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Example session file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Session files allow you to organize a large number of data files and config options in a single file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An example session file:&lt;br /&gt;
 http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&lt;br /&gt;
&lt;br /&gt;
You can use 'View source', or something similar, in your browser to see the actual file structure. It is a plain text file with on each line a file that needs to be loaded.&lt;br /&gt;
&lt;br /&gt;
==File structure ==&lt;br /&gt;
&lt;br /&gt;
===Header===&lt;br /&gt;
Make sure the file starts with a line that contains the words 'GenomeView' and 'session'. These two words have to be on the first line!&lt;br /&gt;
&lt;br /&gt;
We recommend:&lt;br /&gt;
 ##GenomeView session&lt;br /&gt;
&lt;br /&gt;
This header is used to detect the file format by GenomeView.&lt;br /&gt;
&lt;br /&gt;
=== Body ===&lt;br /&gt;
&lt;br /&gt;
The remainder of the file contains lines that have various instructions to load data, configure GenomeView or load plugins. The table below has an overview of all options.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
!Instruction*&lt;br /&gt;
!Value&lt;br /&gt;
|-&lt;br /&gt;
|CONFIG&lt;br /&gt;
|URL or local file path to the configuration file. This line should be the first in the session file, otherwise some data may not have the correct configuration file when initializing.&lt;br /&gt;
|-&lt;br /&gt;
|DATA**	&lt;br /&gt;
|URL or local file path for a data file. This file will be loaded. You do not need to specify the index, GenomeView will look for it in the same folder.&lt;br /&gt;
|-&lt;br /&gt;
|PREFIX	&lt;br /&gt;
|URL or local file path prefix. The value of this instructions will be prepended to any DATA or CONFIG pairs that follow this instruction. A PREFIX values is only valid for subsequent DATA and CONFIG pairs. This can to simplify loading many files from multiple locations. To reset the PREFIX, you can use an empty value.&lt;br /&gt;
|-&lt;br /&gt;
|OPTION	&lt;br /&gt;
|Key=value definition of a single configuration option. This is suited to override a few config options as needed.&lt;br /&gt;
|-&lt;br /&gt;
|ALIAS	[primary name]=[display name]. &lt;br /&gt;
|Add an additional synonym for an Entry (chromosome). This can be useful if your data has different identifiers for the same sequence in different files. The primary name will be used to connect the data types. Multiple primary names can point to the display name, in that case you can use the aliases to connect multiple different IDs.&lt;br /&gt;
|-&lt;br /&gt;
|LOCATION&lt;br /&gt;
|Set the visible location to the specified location. The location needs to be specified [entry]:[start position]-[end position].&lt;br /&gt;
|-&lt;br /&gt;
|PLUGIN	&lt;br /&gt;
|Allows you to request the user to automatically install a plugin. The plugin needs to be specified as a URL to the zip file. You can use relative names in conjunction with the PREFIX parameter&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 ** The legacy keywords C, U and F will continue to work.&lt;br /&gt;
&lt;br /&gt;
Each of the lines should be organized like this:&lt;br /&gt;
 instruction[tab, colon or space]value&lt;br /&gt;
&lt;br /&gt;
For example, all of these are valid ways to specify a file&lt;br /&gt;
 DATA	http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/annotation.gff&lt;br /&gt;
 DATA:http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/operon.gff&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Important: You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
===Example session file===&lt;br /&gt;
&lt;br /&gt;
 ##GenomeView session -- DO NOT DELETE THIS LINE&lt;br /&gt;
 CONFIG http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/tbconfig.txt&lt;br /&gt;
 ALIAS MT_H37RV_V2=MyTBGenome&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 PREFIX http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/&lt;br /&gt;
 DATA annotation.gff&lt;br /&gt;
 DATA operon.gff&lt;br /&gt;
 DATA sRNA.gff&lt;br /&gt;
 DATA rRNA.gff&lt;br /&gt;
 PREFIX&lt;br /&gt;
 PLUGIN http://www.broadinstitute.org/software/genomeview/resources/save2pdf-1.1.zip&lt;br /&gt;
&lt;br /&gt;
== Starting a session with a launch URL ==&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
== Hiding the session URL ==&lt;br /&gt;
Typically you don't even have to expose this URL and you can use a simple PHP script index.php that redirects to that location.&lt;br /&gt;
For example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;header(&amp;quot;Location: http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&amp;quot;);&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
	<entry>
		<id>https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10060</id>
		<title>Session files</title>
		<link rel="alternate" type="text/html" href="https://manual.genomeview.org/index.php?title=Session_files&amp;diff=10060"/>
		<updated>2013-11-15T21:01:57Z</updated>

		<summary type="html">&lt;p&gt;Thomas Admin: /* Body */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Session files allow you to organize a large number of data files and config options in a single file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
An example session file:&lt;br /&gt;
 http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&lt;br /&gt;
&lt;br /&gt;
You can use 'View source', or something similar, in your browser to see the actual file structure. It is a plain text file with on each line a file that needs to be loaded.&lt;br /&gt;
&lt;br /&gt;
==File structure ==&lt;br /&gt;
&lt;br /&gt;
===Header===&lt;br /&gt;
Make sure the file starts with a line that contains the words 'GenomeView' and 'session'. These two words have to be on the first line!&lt;br /&gt;
&lt;br /&gt;
We recommend:&lt;br /&gt;
 ##GenomeView session&lt;br /&gt;
&lt;br /&gt;
This header is used to detect the file format by GenomeView.&lt;br /&gt;
&lt;br /&gt;
=== Body ===&lt;br /&gt;
&lt;br /&gt;
The remainder of the file contains lines that have various instructions to load data, configure GenomeView or load plugins. The table below has an overview of all options.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
!Instruction*&lt;br /&gt;
!Value&lt;br /&gt;
|-&lt;br /&gt;
|CONFIG&lt;br /&gt;
|URL or local file path to the configuration file. This line should be the first in the session file, otherwise some data may not have the correct configuration file when initializing.&lt;br /&gt;
|-&lt;br /&gt;
|DATA**	&lt;br /&gt;
|URL or local file path for a data file. This file will be loaded. You do not need to specify the index, GenomeView will look for it in the same folder.&lt;br /&gt;
|-&lt;br /&gt;
|PREFIX	&lt;br /&gt;
|URL or local file path prefix. The value of this instructions will be prepended to any DATA or CONFIG pairs that follow this instruction. A PREFIX values is only valid for subsequent DATA and CONFIG pairs. This can to simplify loading many files from multiple locations. To reset the PREFIX, you can use an empty value.&lt;br /&gt;
|-&lt;br /&gt;
|OPTION	&lt;br /&gt;
|Key=value definition of a single configuration option. This is suited to override a few config options as needed.&lt;br /&gt;
|-&lt;br /&gt;
|ALIAS	[primary name]=[display name]. &lt;br /&gt;
|Add an additional synonym for an Entry (chromosome). This can be useful if your data has different identifiers for the same sequence in different files. The primary name will be used to connect the data types. Multiple primary names can point to the display name, in that case you can use the aliases to connect multiple different IDs.&lt;br /&gt;
|-&lt;br /&gt;
|LOCATION&lt;br /&gt;
|Set the visible location to the specified location. The location needs to be specified [entry]:[start position]-[end position].&lt;br /&gt;
|-&lt;br /&gt;
|PLUGIN	&lt;br /&gt;
|Allows you to request the user to automatically install a plugin. The plugin needs to be specified as a URL to the zip file. You can use relative names in conjunction with the PREFIX parameter&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 ** The legacy keywords C, U and F will continue to work.&lt;br /&gt;
&lt;br /&gt;
Each of the lines should be organized like this:&lt;br /&gt;
 instruction[tab, colon or space]value&lt;br /&gt;
&lt;br /&gt;
For example, all of these are valid ways to specify a file&lt;br /&gt;
 DATA	http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/annotation.gff&lt;br /&gt;
 DATA:http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/operon.gff&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Important: You should use the JNLP file we provide as it will integrate the parameters into the start-up parameters of the webstart application.&lt;br /&gt;
&lt;br /&gt;
===Example session file===&lt;br /&gt;
&lt;br /&gt;
 ##GenomeView session -- DO NOT DELETE THIS LINE&lt;br /&gt;
 CONFIG http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/tbconfig.txt&lt;br /&gt;
 ALIAS MT_H37RV_V2=MyTBGenome&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/MT_H37RV_V2.fasta&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/annotation.gff&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/operon.gff&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/sRNA.gff&lt;br /&gt;
 DATA http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/rRNA.gff&lt;br /&gt;
 PLUGIN http://www.broadinstitute.org/software/genomeview/resources/save2pdf-1.1.zip&lt;br /&gt;
&lt;br /&gt;
== Starting a session with a launch URL ==&lt;br /&gt;
The basic set-up to start GenomeView with a [[session file]] is&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;http://genomeview.org/start/launch.jnlp?--session &amp;lt;URL to the session file&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For example&lt;br /&gt;
[http://genomeview.org/start/launch.jnlp?--session%20http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php]&lt;br /&gt;
&lt;br /&gt;
== Hiding the session URL ==&lt;br /&gt;
Typically you don't even have to expose this URL and you can use a simple PHP script index.php that redirects to that location.&lt;br /&gt;
For example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;header(&amp;quot;Location: http://genomeview.org/start/launch.jnlp?--session http://www.broadinstitute.org/software/genomeview/genomes/mtb_h37rv_v2/session.php&amp;quot;);&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thomas Admin</name></author>
	</entry>
</feed>