WiggleCommonMixin
Auto-generated from the @jbrowse/mobx-state-tree model in the source — see the developer guide for concepts. Provided by the wiggle plugin. View source.
Extends YFieldConfigMixin with the narrowed rpcDataMap, the autoscale
domain and the wiggle-specific config: the origin, rendering type,
aggregate, resolution and the line/gap settings. Extended on this chain
with .props()/.views() rather than a mixin composed in, so no
types.compose layer is added (ADR-041).
Used by LinearWiggleDisplay and gccontent's two GC displays.
Each section ends with the members a composed model contributes, linked to the page that documents them.
Volatiles
1 inherited volatile from one model
Getters
| Member | Description |
|---|---|
resolutionnumber | Points per pixel the fetch asks for, clamped to what the Resolution menu offers: the slot is reachable from a track config, which runs no setter, and 0 there divides by zero inside the adapter. |
rpcDataMapReadonlyMap<number, WiggleDataResult> | The fetched scores, keyed by displayedRegionIndex — the foundation's per-region store, narrowed. |
originnumber | The value bars grow from, which a color scale also reads where its own domain says nothing. |
lineWidthnumber | A line's width, the size slot or 1 px while unset. |
sizenumber | A point's diameter, the size slot or 2 px while unset. |
maxGapMultiplenumber | Interpolated-line gap threshold, as a multiple of the track's own mean point spacing (see gapBreakLimit). 0 keeps one connected line. |
aggregate"max" | "mean" | "min" | |
extent"min-max" | "none" | |
renderingType"density" | "line" | "linecenter" | "scatter" | "xyplot" | |
hasResolutionboolean | Asked of the display's OWN adapter, which for the GC display is the synthesized GCContentAdapter rather than the track's raw sequence adapter — the two diverged when the adapter config moved onto the shared model. It answers the same today, since only BigWigAdapter and MultiWiggleAdapter declare the capability, and the display's adapter is the honest subject: the resolution slot it gates is passed to whatever this display fetches from. |
effectiveExtent"min-max" | "none" | The extent actually drawn. Density maps score to color and has no min-max presentation, so the autoscale domain reads this rather than the raw slot; otherwise the color ramp spans the min and max while the plot paints the aggregate, and the score legend reports a range nothing on screen reaches. Single-wiggle defaults to min-max, so plain "plot type → Density" hit this. |
tooltipShowsMinMaxboolean | Whether a summary bin's tooltip lists its min and max: where they are drawn, or where the bar is one of them rather than the mean. |
autoscaleSourceNamesSet<string> | undefined | Source names to include when computing the autoscale domain; undefined means every fetched source. The wiggle display always fetches all sources and filters client-side, so it overrides this to the visible subset — otherwise a subtree filter that hides sources would leave the Y-axis scaled to the hidden ones. |
scoreRuleValuesnumber[] | Scores the axis must reach whatever the data does, so a rule drawn at one stays on it. [] here and overridden by the display that draws scales.y.rules. |
autoscaleRange[number, number] | undefined | What the sources visible in the settled blocks span, under the autoscale mode. undefined until the view and the data are ready, which is not the [0, 1] a caller falls back to — see visibleStatsRange. |
domain[number, number] | undefined | |
defaultScoreDomain[number | undefined, number | undefined] | The bounds the adapter declares its values lie in, where it declares any (getValueDomain): a GC content track's [0, 1], so its axis reads alike at every locus. Config bounds still win. |
23 inherited getters from 4 models
From YFieldConfigMixin: yField
From WiggleScoreConfigMixin: isDensityMode, axisReachesZero
From ScoreScaleMixin: scaleType, scaleZero, domainQuantile, clipQuantile, symlogConstant, manualMinScore, manualMaxScore, valueScaleNotices, autoscaleGroup, scaleTitle, grid, minimalTicks, scoreRulesDrawn, scoreRules
From ScoreAxisMixin: valueScales, autoscaledDomain, minScoreBound, maxScoreBound, hasManualScoreBounds, axes
Actions
| Member | Description |
|---|---|
| setRpcData | Stage a region as fetched, with this mixin's payload shape — so a test stands up a loaded display in one call. Production goes through ctx.commitRegion. |
selectFeature(feat: WiggleHoveredFeature) => void | |
setResolution(res: number) => void | |
setOrigin(val?: number | undefined) => void | |
| setMark | The plot's mark, and a line's interpolate; any other mark resets interpolate, which only a line reads. |
setAggregate(val: "max" | "mean" | "min") => void | |
setExtent(val: "min-max" | "none") => void | |
setSize(val?: number | undefined) => void |
8 inherited actions from one model
From ScoreScaleMixin: setScaleType, setScaleZero, setDomainQuantile, setMinScore, setMaxScore, setAutoscaleGroup, setGrid, setScoreRules