92af4b0363b70062f69a5730648b20bd8e52a317 braney Mon Aug 31 13:34:03 2026 -0700 Drop bed from searchIndex and searchTrix, and deprecate pslSequence instead of deleting it This is the reverse of the earlier passes. Instead of asking what a type list is missing, it asks which declared type nothing supports. searchIndex and searchTrix both declared bed. Neither works on a SQL bed table. The trackDb read for searchIndex is at bigBedFind.c:270 and it then needs a bbi file, from bigDataUrl or from the table's fileName, which a plain bed table does not have. searchTrix has two readers: bigBedFind.c:312 reads it from trackDb on the bigBed path, while hgFind.c:2393 reads it from hgFindSpec, which is how a SQL track gets trix search. Native usage agrees, with zero bed tracks for either setting. searchIndex also gains bigPsl, bigGenePred and bigBarChart, and searchTrix gains bigGenePred, all of which have real usage. pslSequence was deleted outright in 0e4e0c0af65. It is obsolete, but deleting the row was the wrong way to say so. 118 psl and 6 bigPsl native tracks set it, and so do three public-hub bigPsl tracks. hubCheck takes its vocabulary from this page, so with no row those hub authors would be told the setting "is not recognized. Check for typos", with a spelling suggestion, which is the wrong advice for a setting they took from our own documentation. The row is back at level-deprecated, which makes hubCheck say "is deprecated" instead, the way it already does for canPack, useScore, metadata and noInherit. Verified by running hubCheck against both spellings of the page. The library blurb is restored too, rewritten to say the setting is obsolete and to map its three values onto baseColorDefault, which replaced it in 8d32ba75938 in 2006. chainMinScore is deliberately left alone. It was proposed for deletion on the grounds that nothing reads it. Nothing does, but our own automation writes it: asmHubChainNetTrackDb.pl:101 and chainNetCompositeTrackDb.pl:186 emit "chainMinScore 5000" into the chainNet composite stanza, and findScores.pl converts -minScore into it. 40,920 native bed stanzas and 16 chain tracks carry it today. It records the minScore the chains were built with. Removing its documentation would leave those stanzas with an undocumented setting. changes.html gains a row for the type lists corrected across all three of these commits, and its existing pslSequence row is rewritten: it said the setting was removed, which is no longer what happened. Since the earlier commit has not shipped to the RR, no reader ever saw the "Removed" wording. trackDbSettings.yaml and .json are regenerated, and now hold 263 settings. refs #37908 diff --git src/hg/htdocs/goldenPath/help/trackDb/trackDbHub.v3.html src/hg/htdocs/goldenPath/help/trackDb/trackDbHub.v3.html index fc59ea703fb..b220e727fb4 100755 --- src/hg/htdocs/goldenPath/help/trackDb/trackDbHub.v3.html +++ src/hg/htdocs/goldenPath/help/trackDb/trackDbHub.v3.html @@ -1,1874 +1,1877 @@
This page describes all of the settings one might use in creating a track or assembly hub. Hubs display your own data in the Genome Browser by hosting your files on a web server and connecting them with a simple text configuration file, giving you more control and permanence than custom tracks. This initial section touches on the files and settings needed in creating a hub before providing a listing of settings separated by track type.
For those new to creating hubs: Our Hub Basics page provides a simple introduction to creating hubs.
For returning readers: We keep a list of changes to the trackDb specification below.
All hubs must include a top-level hub.txt file. This file contains general settings that identify your hub in our internal databases and in the Genome Browser interface. The URL to the hub.txt is used to load your hub. Our Hub Basics describes how to create a hub.txt. A full listing of hub.txt settings can be found in the General hub configuration settings section below.
If your hub contains tracks on a single genome assembly, then you can put all of the
hub, genome, and track configuration settings into a single file with
useOneFile.
A genomes.txt is only necessary if you are NOT using the useOneFile setting
as described below. When using useOneFile, one only needs
to include the genome line. This line will reference
a UCSC assembly name (e.g. hg38) or a GenBank assembly available through our
GenArk repository
beginning with GCF or GCA (e.g. GCF_000891275.1). If an assembly is not available in GenArk,
request it.
If your hub contains tracks for more than one
genome, you will need to define a genomes.txt. A full listing of
genomes.txt settings, including those needed for an assembly hub, settings can be found in the Assembly hub "genome" settings section below.
useOneFile on for hubs with only one genome
If your hub is only displaying one genome, one can use the useOneFile on setting
to put all hub, genome, and track configuration settings into a single file.
Load a working example here.
This document describes how to set dataset display characteristics using "track database" or "trackDb" settings through name-value pair associations used in a Track Hub's trackDb.txt file.
The text file format for trackDb settings starts by creating a text block, or "stanza", for each track dataset. These stanzas should be structured according to the following format specification:
track name. Additional
lines will contain further "setting" names followed
by "values" of one or more words of numbers.
track line and a stanza ends
with a blank line.
track names, although there are some
settings that include periods in the name, e.g. filter.fieldName.
Here is an example:
track myFirstTrack
type bigBed 3
bigDataUrl myFirstTrack.bb
shortLabel Example Data
longLabel The data in this track is format "bigBed 3".
Every track stanza should have these five settings
(track type bigDataUrl shortLabel longLabel).
The first line's track key value (myFirstTrack) is the
identifier for the dataset given to the Browser and it must be
unique for each track within your data hub. After the track key,
the most important setting is the type key. This value
(bigBed 3) tells the Browser the type of format the
data is in, defines how to display it, and determines
which options are available for fine control of that display.
For some configurable features, like filters, an additional
period or plus may be needed (bigBed 5 .) or (bigBed 9 +).
Running hubCheck on your hub.txt file identifies errors in settings, file
paths, and formatting that could prevent your hub from loading correctly. Download hubCheck from the utilities download page and
see the hubCheck
documentation and related
blog post
for more information on validating hubs.
Hubs also support the use of include statements, allowing one to insert a file containing a set of trackDb stanzas into a primary trackDb. Use this when you have the same track across several assemblies, or several large, complex tracks.
Assembly hubs can display novel genome assemblies and annotations in the UCSC Genome Browser. Note: Many genome assemblies available in GenBank are also available in our GenArk repository. If an assembly is not available in GenArk, but is available in GenBank, request it. However, if your genome assembly is not yet publicly available, you can make a custom assembly hub. To create an assembly hub, refer to our Assembly Hub User Guide or our Quick Start Guide to Assembly Hubs.
The remainder of this document is divided into the following sections and should be used as a ready reference. Settings are colored based on their support level:
| required | required settings |
| base | common settings supported at other sites |
| deprecated | settings that are being retired (replacement is listed in the details section) |
| new | new settings not yet assigned a level (may be replaced) |
| full | other settings |
See the list of changes to see recent additions.
track |
type |
shortLabel |
longLabel |
bigDataUrl <url/relativePath> |
html |
visibility |
meta |
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> |
refUrl <url> |
bigDataIndex <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> |
doWiggle on |
|
Additional settings found in the "Item or region tracks" section are also available for displaying bam tags. maxWindowCoverage, maxWindowToDraw, |
Example of a bam track
|
type bigBarChart |
barChartBars <label1 label2...> |
bigDataUrl <url/relativePath>
|
barChartColors <color1 color2...>
|
barChartLabel <label>
|
barChartMaxSize <small/medium/large>
|
barChartSizeWindows <largeMax> <smallMin>
|
barChartStretchToItem on
|
barChartFacets on
|
barChartMatrixUrl <url>
|
barChartStatsUrl on
|
singleCellColumnNames off
|
barChartMerge on
|
barChartMetric <metric>
|
barChartUnit <unit>
|
barChartCategoryUrl <url/relativePath>
|
barChartSampleUrl <url/relativePath>
|
barChartBarMinPadding <num>
|
barChartBarMinWidth <num>
|
maxLimit <maximum-bar-value>
|
|
Additional settings defined in other sections are also available for displaying bigBarChart tracks. labelFields, defaultLabelFields url urlLabel urls |
Example of a bigBarChart track
|
type bigBed <3-12> [+/.] |
bigDataUrl <url/relativePath> |
itemRgb on |
colorFields default="<label>" <fieldName>="<label>" ...
|
colorByStrand <red,green,blue>
<red,green,blue> |
denseCoverage <maxVal> |
labelOnFeature <on/off> |
extraDetailsTable <url/relativePath>
|
extraTableFields <fieldName1|table title,fieldName2|table title,...>
|
detailsStaticTable <url/relativePath>
|
detailsDynamicTable <fieldName1|table title,fieldName2|table title,...>
|
detailsScript.<plotType>.<fieldName> <jsonConfig>
|
exonArrows <on/off> |
exonNumbers <on/off> |
scoreFilter <low>[:<high>]scoreFilterLimits <low>[:<high>] |
maxItems <integer> |
maxWindowCoverage <integer> |
maxWindowToDraw <integer> |
minGrayLevel <1-9> |
noScoreFilter on |
spectrum onscoreMax <integer>scoreMin <integer> |
style <heatmap> |
thickDrawItem <off/on> |
decorator.* |
searchIndex <str> |
searchTrix <url/relativePath> |
labelFields <fieldName[,fieldName]> |
defaultLabelFields <fieldName[,fieldName]> |
labelSeparator <text> |
filter.<fieldName> <default integer>filterByRange.<fieldName> <off/on>filterLimits.<fieldName> <low>[:<high>] |
filterText.<fieldName> <default search string>filterType.<fieldName> <wildcard/regexp> |
filterValues.<fieldName> <value1,value2,value3...>filterValuesDefault.<fieldName> <value1,value2,value3...>filterType.<fieldName> <single/singleList/multiple/multipleListOr/multipleListAnd/multipleListOnlyOr/multipleListOnlyAnd> |
filterBy <field1:title=[+]opt1a...> [field2:title=[+]opt2a...] |
filterLabel.<fieldName> <label> |
filterPriority.<fieldName> <number> |
highlight.<fieldName> <default integer>highlightByRange.<fieldName> <off/on>highlightLimits.<fieldName> <low>[:<high>] |
highlightText.<fieldName> <default search string>highlightType.<fieldName> <wildcard/regexp> |
highlightValues.<fieldName> <value1,value2,value3...>highlightValuesDefault.<fieldName> <value1,value2,value3...>highlightType.<fieldName> <single/singleList/multiple/multipleListOr/multipleListAnd/multipleListOnlyOr/multipleListOnlyAnd> |
highlightColor <#hexcolor> |
highlightPriority.<fieldName> <number> |
type bigChain targetDb |
bigDataUrl <url/relativePath> |
linkDataUrl <url/relativePath> |
otherTwoBitUrl <url/relativePath> |
chainColor <scheme> |
chainNormScoreAvailable <yes/no> |
baseColorUseSequence < <extFile {seqTable} <extFile> /
hgPcrResult / lfExtra / nameIsSequence / seq1Seq2 / ss / 2bit > |
baseColorDefault <diffBases/diffCodons/itemBases/itemCodons/genomicCodons> |
indelDoubleInsert <off/on>indelQueryInsert <off/on>indelPolyA <off/on> |
type bigGenePred |
bigDataUrl <url/relativePath> |
intronGap <#bases> |
baseColorDefault <diffBases/diffCodons/itemBases/itemCodons/genomicCodons> |
labelFields <fieldName[,fieldName]> |
defaultLabelFields <fieldName[,fieldName]> |
labelSeparator <text> |
|
Additional settings defined in other sections are also available for displaying bigGenePred tracks. decorator |
type bigInteract |
bigDataUrl <url/relativePath>
|
interactDirectional <true/offsetSource/offsetTarget/clusterSource/clusterTarget>
|
interactUp <true/false>
|
detailsBoxesEnabled <true/false>
|
interactMultiRegion <true/padding>
|
endsVisible two
|
|
Additional settings defined in other sections are also available for displaying bigInteract tracks. maxHeightPixels scoreMin spectrum, |
Example of a bigInteract track
|
type bigNarrowPeak |
bigDataUrl <url/relativePath> |
pValueFilterqValueFiltersignalFilter |
type bigPsl |
bigDataUrl <url/relativePath> |
baseColorUseCds <given> |
baseColorUseSequence < <extFile {seqTable} <extFile> /
hgPcrResult / lfExtra / nameIsSequence / seq1Seq2 / ss > |
baseColorDefault <diffBases/diffCodons/itemBases/itemCodons/genomicCodons> |
baseColorTickColor <lighterShade/contrastingColor> |
showDiffBasesAllScales on |
indelDoubleInsert <off/on>indelQueryInsert <off/on>indelPolyA <off/on> |
pslSequence <no/all/different> |
showCdsAllScales on |
showCdsMaxZoom <basesPerPixel> |
showDiffBasesMaxZoom <basesPerPixel> |
labelFields <fieldName[,fieldName]> |
defaultLabelFields <fieldName[,fieldName]> |
labelSeparator <text> |
otherTwoBitUrl <url/relativePath> |
|
Additional settings defined in other sections are also available for displaying bigPsl tracks. decorator |
type halSnake |
bigDataUrl <url/relativePath> |
showSnpWidth <integer> |
otherSpecies <otherSpecies> |
type vcfTabix |
bigDataUrl <url/relativePath> |
bigDataIndex <url/relativePath> |
Related settings:
hapClusterEnabled <true|false> |
hapClusterMethod <centerWeighted|fileOrder|treeFile url> |
hapClusterColorBy <altOnly|function|refAlt|base> |
geneTrack <track> |
hapClusterTreeAngle <triangle|rectangle> |
hapClusterHeight <N> |
Related settings:
applyMinQual <true|false> |
minQual <Q> |
minFreq <F> |
vcfDoFilter <on/off> |
vcfDoQual <on/off> |
vcfDoMaf <on/off> |
sampleMetadataFile <url> |
|
Additional settings found in the "Item or region tracks" section are also available for displaying Variant Call Format tracks. maxWindowCoverage maxWindowToDraw |
|
Example of a VCF track
|
type vcfPhasedTrio |
bigDataUrl <url/relativePath> |
vcfChildSample <sampleName|altName> |
bigDataIndex <url/relativePath> |
vcfParentSamples <sampleName|altName,sampleName|altName> |
vcfUseAltSampleNames <on/off> |
geneTrack <track> |
vcfDoFilter <on/off> |
vcfDoQual <on/off> |
vcfDoMaf <on/off> |
|
Additional settings found in the "Item or region tracks" section are also available for displaying Variant Call Format tracks. maxWindowCoverage maxWindowToDraw |
|
Example of a VCF Phased Trio track
|
superTrack on show |
parent <superTrack> |
|
Example of a Supertrack
|
container multiWig |
parent <containerTrack> |
aggregate <transparentOverlay/stacked/solidOverlay/none> |
showSubtrackColorOnUi on |
|
Example of an Aggregate track
|
This section describes hub and assembly configuration settings. It is recommended
to use the useOneFile setting, which allows all hub configuration settings
to be placed in a single file without the need for separate
hub.txt, genomes.txt, or trackDb.txt files.
hub <str> |
shortLabel <str> |
longLabel <str> |
genomesFile <url/relativePath> |
email <email address> |
descriptionUrl <url/relativePath> |
useOneFile <on> |
|
Example of an opening hub stanza
|
| Setting | For Types | Notes |
|---|---|---|
metadata
|
all | |
noInherit | all | |
useScore |
bed, bigBed, bigGenePred, psl, bigPsl | Replaced with spectrum, which sets the same flag and takes the same type list. |