The remainder of this document is divided into the following sections and should be used as a ready reference.
track |
type |
shortLabel |
longLabel |
bigDataUrl <url/relativePath> |
visibility |
html |
Many settings are valid only for certain types of tracks. Many of these tracks are described below along with settings specific to their types.
type bam |
bigDataUrl <url/relativePath> |
Related settings:
bamColorMode <strand/gray/tag/off> |
bamGrayMode <aliQual/baseQual/unpaired> aliQualRange <min:max> baseQualRange <min:max> |
bamColorTag <XX> |
noColorTag . |
bamSkipPrintQualScore . |
indelDoubleInsert <off/on> indelQueryInsert <off/on> indelPolyA <off/on> |
minAliQual <#> |
Related settings:
pairEndsByName . |
pairSearchRange <#> |
showNames <on/off> |
Additional settings found in the "Item or region tracks" section are also available for displaying bam tags. maxWindowToDraw, |
Example of a bam track
|
type vcfTabIx |
bigDataUrl <url/relativePath> |
Additional settings found in the "Item or region tracks" section are also available for displaying Variant Call Format tracks. maxWindowToDraw |
Example of a VCF track
|
All tracks for a hub are treated as a single group within the Browser. However hub tracks can be further subdivided with into advanced hierarchical organizations. There is even an option to combine the data of multiple remote data files into a single image.
superTrack on |
parent <superTrack> |
Example of a Supertrack
|
compositeTrack on |
parent <composite> [off/on] |
allButtonPair on |
centerLabelsDense <off/on> |
dragAndDrop on |
Example of a Composite track
|
container multiWig |
parent <containerTrack> |
aggregate <transparentOverly/solidOverlay/none> |
showSubtrackColorOnUi on |
Example of an Aggregate track
|