The maximum width of the visible region, configured in bases. Default is 500000.
The id of an element on the page whose contents will be replaced with the Dalliance instance
when it starts up.
String used as a key for session persistance. It should be unique amongst all Dalliance
instances served from a given domain. Not relevant if noPersist is true.
This defines the reference genome coordinate system for the browser. It's principally used when
querying the DAS registry to find relevant datasources. It is also needed to correctly re-map data
between coordinate systems. A typical configuration looks like:
The speciesName field can be a human-readable label, and isn't used when querying the
registry. taxon should be an integer identified from the NCBI Taxonomyauth and version should, as far as possible, match authority and version strings used
in the DAS Registry.
The ucscName field is optional, but should be filled in with the UCSC genome browser name of the assembly
if it is defined. This enables track-hub support to work properly.
If true, attempt to change the title of the web browser window to reflect the species name being displayed. Generally not
wanted for embedded browsers.
URL from which static browser resources should be downloaded (CSS, images, help
is http://www.biodalliance.org/release-X.Y code where X.Y represents the
current major and minor release numbers. The uiPrefix option is a (deprecated)
The maximum number of web-workers to us when fetching data. If set to 0, the web worker system
is disabled and all data fetching will be performed on the main UI thread. Using workers generally
improves responsiveness but may increase resource usage.
Fully disables Dalliance's built-in session management. When the page is reloaded, everything will be
reset to the configuration passed to the Browser constructor.
Disable storing the current location in the session-management system. All other options (notably,
current track configurations are preserved). This is useful if you are embedding little feature-centric
browser instances into a larger application (e.g. a database with one page per gene).
Do not add the standard "tier tab" labels. Intended for very lightweight embedded browser instances/
Array of CSS color strings used as background colors. Dalliance cycles through the available
colours in order. In the special case of this property being set to null, tiers
will have transparent backgrounds. This is only recommended if there's a specific reason
for letting the background show through.
Maximum height, in CSS pixels, that the Dalliance component can grow to (default 500).
Attempt to fit the Dalliance component to the containing window, making allowances for other content on the page.
The default location of the vertical guideline. Valid values are center, left, right,
As of Dalliance 0.9, there is rudimentary support for UCSC-style
track hubs, so long as they're server over HTTP and support CORS. These can be configured with:
...and will appear as extra tabs in the track-addition user interface.
Dalliance can do on-the-fly coordinate system mapping. The set of available mappings is configured by the chains property, which takes a map of mapping names to mapping definitions, e.g.:
You can use arbitrary strings as names for mappings. When configuring a track in the sources array, you can specify which mapping to use, e.g.:
Each mapping definition has the following properties:
URI to access alignment data.
Currently supported values are "bigbed", which specifies a bigBed-encoded version of the chain file
format, produced by the chain2bed utility. If type is not specified, alignment-DAS is assumed. Alignment DAS support is deprecated as of
Dalliance 0.12. Please contact Thomas Down for more details if you really need it.
Support credentials when accessing the alignment data.
The coordinate system that this mapping is from (it is assumed to be) to the default coordinate system of the browser. This is important, because it controls what gets presented if the user is prompted to choose a coordinate system when the user manually adds data. If possible, the ucscName of the coordinate system should also be specified -- if so, coordinate system mapping will be automatically supported when interacting with track-hubs which provide data for more than one genome assembly.