LinearWiggleDisplay
Auto-generated config schema for the current JBrowse release — see the
config guide for concepts. Provided by the wiggle
plugin.
View source.
Example usage
Minimal QuantitativeTrack config. See the
quantitative track guide for all
adapter and display options:
{
type: 'QuantitativeTrack',
trackId: 'coverage',
name: 'Coverage',
assemblyNames: ['hg38'],
adapter: { type: 'BigWigAdapter', uri: 'https://example.com/coverage.bw' },
}
Taller track, log scale, custom color:
{
type: 'QuantitativeTrack',
trackId: 'coverage',
name: 'Coverage',
assemblyNames: ['hg38'],
adapter: { type: 'BigWigAdapter', uri: 'https://example.com/coverage.bw' },
displayDefaults: {
height: 200,
scaleType: 'log',
color: 'darkgreen',
},
}
See the Config slots section below for all available configuration fields.
configuration for the wiggle (quantitative/numeric) display showing XY plot, density, line, or scatter renderings
These are display-level slots: set them inside a track's displays to change
its defaults (setting them at the track top level has no effect). The object
shorthand displayDefaults: { key: value } is equivalent to the full
displays: [{ type: 'LinearWiggleDisplay', displayId: '...', key: value }]
array form — see
configuring displays.
Related links
- Adapter: BedGraphAdapter
- Adapter: BedGraphTabixAdapter
- Adapter: BigWigAdapter
- Adapter: GCContentAdapter
- Extended by: SharedGCContentDisplay
- State model: runtime API
- Guide: config.json format
- Guide: Cookbook
- Guide: Custom track and display types
- Guide: Defaults for all tracks
- Guide: Display settings
- Guide: Hi-C track
- Guide: Quantitative track
- Guide: Quantitative tracks
- Guide: Structural variants (Cancer GIAB)
- Guide: Tracks
Config slots
These slots go on a display entry:
"displays": [{ "type": "LinearWiggleDisplay", ... }], or in the track's
displayDefaults when this
is its default display. Slot types (fileLocation, frozen, ...) are explained
in the config slot types reference. Slots a
base configuration contributes are listed here too, so this table is the whole
surface.
| Slot | Description |
|---|---|
defaultRenderingstringEnum (xyplot, density, line, linecenter, scatter) = 'xyplot' | Default rendering type: xyplot, density, line, linecenter, or scatter. |
heightnumber = 100 | Default height of the track |
useBicolorboolean = true | When true (the default), positive scores use posColor and negative use negColor; when false, all bars use the single color slot. Setting color alone, with no posColor/negColor/useBicolor, turns this off for you. |
colorcolor = '#0068d1' | Single fill CSS color for the wiggle bars; a wiggle colors per signal, not per feature, so jexl callbacks do not apply. Set alone it implies useBicolor false; alongside posColor/negColor it goes unused. Density rendering always draws from posColor. |
scoreRulesfrozen = [] | Not in the shared wiggle fields: MultiLinearWiggleDisplay spreads those and stacks a plot box per row, so one rule list has no single axis to sit on there. |
minimalTicksboolean = false | Draw only the min/max Y-axis ticks advanced |
minScorenumber = Number.MIN_VALUE | Fixed minimum score bound. The default (Number.MIN_VALUE) is a sentinel meaning "unset, use autoscale" advanced |
maxScorenumber = Number.MAX_VALUE | Fixed maximum score bound. The default (Number.MAX_VALUE) is a sentinel meaning "unset, use autoscale" advanced |
scaleTypestringEnum (linear, log, symlog) = 'linear' | Scale type. "log" cannot represent 0 or negative scores and floors the domain above them; "symlog" is log-like away from zero and linear through it, so a track whose scores touch or cross 0 keeps them |
autoscalestringEnum (local, localsd, localpercentile) = 'localpercentile' | Autoscale type: "local" uses the min/max in the visible region, "localsd" uses mean ± numStdDev standard deviations, "localpercentile" uses the numQuantile-th percentile score as the max (robust to skewed/peaky data) |
numStdDevnumber = 3 | Number of standard deviations to use for the localsd autoscale type advanced |
displayCrossHatchesboolean = false | Rule the score axis with horizontal cross hatches at the tick positions — the config form of the score menu's "Show cross hatches". Ignored by the density rendering types, which spend color rather than height on the score and so have no axis to rule |
symlogConstantnumber = 0 | Width of symlog's linear region around zero. The default 0 means "derive from the domain" (a thousandth of its largest magnitude). Setting it to 1 makes symlog exactly log(x+1), which flattens anything living below 1 — set it near the smallest score you need to tell apart instead advanced |
posColorcolor = '#0068d1' | Fill color for positive scores, used when useBicolor is true (the default) |
negColorcolor = '#e01e26' | Fill color for negative scores, used when useBicolor is true (the default) |
bicolorPivotnumber = 0 | Pivot value for bicolor mode advanced |
numQuantilenumber = 0.99 | Percentile used to clip outliers for the localpercentile autoscale type (e.g. 0.99 clips the outermost 1% of each sign). Positive and negative extents are computed independently and anchored at 0, so a sparse minority tail (e.g. phyloP acceleration) stays visible; all-positive data pins the min at 0 advanced |
scatterPointSizemaybeNumber = 2 promotable | Point height in px for scatterplot ("scatter"/"multiscatter") rendering. Unset (the default) follows the session-wide default for this display type, falling back to 2 advanced |
lineWidthmaybeNumber = 1 promotable | Line thickness in px for line ("line"/"multiline") rendering. Unset (the default) follows the session-wide default for this display type, falling back to 1 advanced |
maxGapMultiplenumber = 0 | Interpolated line ("linecenter"/"multilinecenter"/"multirowlinecenter") only: break the line where consecutive points sit further apart than this multiple of the track's own mean point spacing, instead of drawing one long chord across the hole. Scaled to the data rather than a fixed bp distance so it holds at every zoom. 0 disables breaking (the pre-existing behavior, one connected line throughout) advanced |
summaryScoreModestringEnum (max, min, avg, whiskers) = 'whiskers' | choose whether to use max/min/average or whiskers which combines all three into the same rendering |
fetchSizeLimitnumber = 1_000_000 | maximum data to attempt to download for a given track, used if adapter doesn't specify one advanced |
forceLoadboolean = false | Declarative equivalent of the "Force load" button on the "too much data" banner: when true the display always renders, however large the region or dense the features. Off by default (the gate guards against huge downloads). Set it on a view no one can interact with — an embedded / notebook view, or a screenshot — where the region is known and you want it drawn without a click. advanced |