otherDb <otherDb>Track types that show pairwise alignments often need to declare the other species/assembly included in the alignment. Types that use this setting include bed, chain, netAlign, psl and snake.
Example:
otherDb mm10
This example sets the second assembly in the alignment to the mouse mm10 assembly.
otherTwoBitUrl <url/relativePath>For pairwise alignment tracks this can specify where to find the query sequence This setting can be used in psl, bigPsl, chain, and bigChain tracks.
Example:
-otherTwoBitUrl https://hgdownload.soe.ucsc.edu/goldenPath/hg38/bigZips/hg38.2bit+
otherTwoBitUrl https://hgdownload.gi.ucsc.edu/goldenPath/hg38/bigZips/hg38.2bit
origAssembly <db>NOT FOR HUBS.
The original assembly version for which the dataset was generated. Datasets generated by mapping to one genome assembly may prove useful enough to map to a more recent assembly. Ideally datasets will be regenerated to map to the new assemblies coordinates, but sometimes this is not practical or expedient. Therefore, the dataset may have its genome coordinates "lifted over" to the more recent assembly. In some cases this results in an inferior but nevertheless useful representation. Such datasets should have their original assembly defined with this setting.
@@ -2213,31 +2213,31 @@ scores greater than or equal to 900 above will display in black.searchIndex <str> Specifies the list of field names on which a index has been made.
When a user enters a string in the position search box of the browser,
this index will be searched to find that name, and if the string is in
the index, the user will either be navigated to that position in the
browser, or if there are more than one matches of that string,
will be give a list of the positions to choose from. See HERE
for instructions on how to build an index for a bigBed file.
The searchIndex setting requires the input BED data to be
case-senstive sorted (sort -k1,1 -k2,2n), where
newer versions of the tool bedToBigBed (available
- here)
+ here)
are enhanced to catch improper input.
Example:
searchIndex name
searchTrix <url/relativePath>Specifies the URL to a TRIX file that maps free text to a set of indices that are assumed to have indicies in the associated bigBed file. See here for instructions on how to build a TRIX file and a Searchable Track Hub Quick Start Guide here.
Example:
searchTrix url or relative path
logo
dynseq display on the bigWig help page.
Example:
logo on
logoMaf <url/relativePath>The argument to logoMaf is the path to a MAF alignment (either a table or bigMaf). If set and zoomed into base level, the wiggle will be drawn as a sequence logo calculated by counting the number of each nucleotide aligned to that base, which will be scaled by the value in the wiggle.
Example:
-logoMaf https://hgdownload.soe.ucsc.edu/goldenPath/hg38/multiz470way/multiz470way.bigMaf+
logoMaf https://hgdownload.gi.ucsc.edu/goldenPath/hg38/multiz470way/multiz470way.bigMaf
mouseOverFunction <noAverage>Limit mouse over value display to only display the fundamental values without any averaging of multiple data points. Display will show "zoom in to see values" when fundamental individual values can not be shown. Useful for tracks where averaging values together is not a valid operation.
Example:
mouseOverFunction noAverage
This microarray dataset refers to groupings
defined in the "gnfHumanAtlas2Groups" stanza of the
makeDb/hgCgiData/Human/microarrayGroups.ra file.
extraDetailsTable <url/relativePath>This setting was renamed June 2022. Please use detailsStaticTable instead.
Provides a template to a tab separated text file where $<fieldName> strings will be substituted for data in the bigBed and displayed as an HTML table. For an example of this, please see the following text file: - http://hgdownload.soe.ucsc.edu/gbdb/hg38/gnomAD/v3.1/variants/v3.1.genomes.popTable.txt, where + http://hgdownload.gi.ucsc.edu/gbdb/hg38/gnomAD/v3.1/variants/v3.1.genomes.popTable.txt, where the strings such as "${AC_afr}" will be substituted for the data in that field for the particular item from the bigBed.
Note that the same size table is displayed for every item of the bigBed, even if there is missing data in that field for a particular item. For variable size tables, please see detailsDynamicTable.
extraTableFields <fieldName1|table title,fieldName2|table title,...>This setting was renamed June 2022. Please use detailsDynamicTable instead.
Tells the system that the data in <fieldName1,...> contains an encoded table @@ -4345,31 +4345,31 @@
| annot3 | val3 |
detailsStaticTable <url/relativePath>Provides a template to a tab separated text file where $<fieldName> strings will be substituted for data in the bigBed and displayed as an HTML table. For an example of this, please see the following text file: - http://hgdownload.soe.ucsc.edu/gbdb/hg38/gnomAD/v3.1/variants/v3.1.genomes.popTable.txt, where + http://hgdownload.gi.ucsc.edu/gbdb/hg38/gnomAD/v3.1/variants/v3.1.genomes.popTable.txt, where the strings such as "${AC_afr}" will be substituted for the data in that field for the particular item from the bigBed.
Note that the same size table is displayed for every item of the bigBed, even if there is missing data in that field for a particular item. For variable size tables, please see detailsDynamicTable.
detailsDynamicTable <fieldName1|table title,fieldName2|table title,...>Tells the system that the data in <fieldName1,...> contains an encoded table that should be turned into a standard HTML table on the details page for that item. If @@ -6594,59 +6594,59 @@ sortOrder cell=+ view=+ type bed 3 html TrackDescription.html track myViewPeaks parent myMultiViewComposite shortLabel Peaks view PK visibility pack type bigBed 12 + track myFirstPeakSubtrack parent myViewPeaks on shortLabel Peak One longLabel Peak One Long - bigDataUrl https://hgdownload.soe.ucsc.edu/gbdb/hg38/bbi/ENCODE4/TFrPeakClusters.bb + bigDataUrl https://hgdownload.gi.ucsc.edu/gbdb/hg38/bbi/ENCODE4/TFrPeakClusters.bb subGroups cell=CD14 view=PK track mySecondPeakSubtrack parent myViewPeaks on shortLabel Peak Two longLabel Peak Two Long - bigDataUrl https://hgdownload.soe.ucsc.edu/gbdb/hg38/bbi/ENCODE4/TFrPeakClusters.bb + bigDataUrl https://hgdownload.gi.ucsc.edu/gbdb/hg38/bbi/ENCODE4/TFrPeakClusters.bb subGroups cell=A1GM12 view=PK track myViewSignals parent myMultiViewComposite shortLabel Peaks view SIG visibility pack type bigWig track myFirstSignalsSubtrack parent myViewSignals on shortLabel Sig One longLabel Sig One Long - bigDataUrl https://hgdownload.soe.ucsc.edu/gbdb/hg38/bbi/wgEncodeRegDnase/wgEncodeRegDnaseUwK562Signal.bw + bigDataUrl https://hgdownload.gi.ucsc.edu/gbdb/hg38/bbi/wgEncodeRegDnase/wgEncodeRegDnaseUwK562Signal.bw subGroups cell=CD14 view=SIG track mySecondSignalsSubtrack parent myViewSignals on shortLabel Sig Two longLabel Sig Two Long - bigDataUrl https://hgdownload.soe.ucsc.edu/gbdb/hg38/bbi/wgEncodeRegDnase/wgEncodeRegDnaseUwK562Signal.bw + bigDataUrl https://hgdownload.gi.ucsc.edu/gbdb/hg38/bbi/wgEncodeRegDnase/wgEncodeRegDnaseUwK562Signal.bw subGroups cell=A1GM12 view=SIG
Similar to the example above, except this example shows a composite track containing two views, one with bigBeds and one with bigBeds, all inside of a superTrack.
In some instances, data from multiple tracks is so closely
related that it makes sense to view it as a single track. The
premiere example of this is the signal overlay
track (i.e. "multiWig"). Signal overlay tracks display the signal
data from several subtracks combined in several different ways, making it