ScoreFieldConfigMixin
Auto-generated @jbrowse/mobx-state-tree API for the current JBrowse release — see pluggable elements for concepts. Built into JBrowse core. View source.
WiggleScoreConfigMixin plus scoreField, for a display that plots one
configured feature field and so declares scoreFieldConfigSchemaFields:
both wiggle displays and the Manhattan plot. LinearMarkDisplay names a
field per mark and composes the base instead.
Members a composed model contributes are listed here too, so these tables are the whole surface.
Getters
| Member | Description | Defined by |
|---|---|---|
scoreFieldstring | The feature field the worker plots on the score axis, score by default. A fetch input: every composing display carries it in its rpcProps(), since the field is read where the features are. | ScoreFieldConfigMixin |
scatterPointSizenumber | WiggleScoreConfigMixin | |
displayCrossHatchesboolean | The configured cross-hatch setting the menu toggles; showCrossHatches is what draws. | WiggleScoreConfigMixin |
isDensityModeboolean | Whether score maps to color instead of height; a display overrides it. | WiggleScoreConfigMixin |
showCrossHatchesboolean | Whether the score-axis cross hatches draw: never in density mode, which has no height axis to rule and no toggle in its menu. | WiggleScoreConfigMixin |
| declaredValueScale | Overridable hook: a value scale the display declares somewhere other than these slots — the mark display's encoding.y. Where it answers, it is the owner and the slots below stand in only for the ends it leaves open, so a scale is read from one place whichever place that is. Default none, which is every display whose axis IS these slots. | ScoreScaleMixin |
scaleTypestring | ScoreScaleMixin | |
autoscaleTypestring | ScoreScaleMixin | |
numStdDevnumber | ScoreScaleMixin | |
minScorenumber | Raw slot value, sentinel intact — see the class comment. | ScoreScaleMixin |
maxScorenumber | Raw slot value, sentinel intact — see the class comment. | ScoreScaleMixin |
defaultScoreDomain[number | undefined, number | undefined] | Overridable hook: what each end of the domain falls back to where the config leaves its bound unset. [undefined, undefined] — the default — means autoscale both ends, which is right for a track whose scores have no absolute meaning (a bigwig's units are its own).A display whose scores are bounded by construction overrides it, so the axis stops being a function of what happens to be on screen: GC content is a fraction, so 0 and 1 are its real limits and mean the same thing at every locus. Autoscaled, the same GC value drew at different heights depending on where the user had panned, and the track could not be read across loci. A hook rather than a config default because the answer can depend on display state — GC's does, on gcMode — and rather than each display re-resolving the sentinels below, which is the one thing that must not be duplicated: config bounds still win, precisely because they are checked before this is consulted. | ScoreScaleMixin |
manualMinScorenumber | undefined | The lower bound the config really sets, undefined at the sentinel. | ScoreScaleMixin |
manualMaxScorenumber | undefined | The upper bound the config really sets, undefined at the sentinel. | ScoreScaleMixin |
minScoreBoundnumber | undefined | Resolved lower bound; undefined means autoscale this end. | ScoreScaleMixin |
maxScoreBoundnumber | undefined | Resolved upper bound; undefined means autoscale this end. | ScoreScaleMixin |
hasManualScoreBoundsboolean | Whether the user has pinned either end, which is a different question from whether either end resolved to a number: defaultScoreDomain fills the sentinels in, so a GC content track answers yes to the second with nothing configured. The score menu asks this one — it gates the "Clear manual min/max" row, and a Clear that writes the sentinels already there is a row that does nothing and never goes away. | ScoreScaleMixin |
valueScalesValueScale[] | Overridable hook (default none): the scales this display draws its y through. A display that answers it gets an axis per band of each, with its cross-hatches, placed by DisplayChrome and renderDisplaySvg, and the ticks derived below. | ScoreScaleMixin |
axesYAxis[] | The axes, one per declared scale whose domain resolved: where each tick lands in the band's own pixel space, through computeYTicks unless the scale brought its own ladder. | ScoreScaleMixin |
Actions
| Member | Description | Defined by |
|---|---|---|
toggleCrossHatches() => void | WiggleScoreConfigMixin | |
setScatterPointSize(val?: number | undefined) => void | WiggleScoreConfigMixin | |
setScaleType(scaleType: string) => void | ScoreScaleMixin | |
setAutoscale(val?: string | undefined) => void | ScoreScaleMixin | |
setMinScore(val?: number | undefined) => void | ScoreScaleMixin | |
setMaxScore(val?: number | undefined) => void | ScoreScaleMixin |