LaneRows
Auto-generated from the config schema in the source. See the config guide for concepts. Provided by the linear-comparative-view plugin. View source.
The multi-way synteny display's rows: one lane per assembly below the
anchor, so a lane is always an assembly and the object takes no field. It
is the arrangement a reader gives the lanes, by assembly name, and writing
it changes only the members stated. sort
lists the lanes that stack first, in order, the rest following densest-first
so a ribbon chain through adjacent lanes is cut as late as possible; kept
names the lanes drawn, empty drawing the track's lanes or every lane.
Haplotype lanes read off a graph follow by structure instead, below any
lanes sort pins, so lanes whose deletions and insertions against the
anchor match sit together, in an order worked out once per window. Lanes
take no tree.
Example usage
{
type: 'MultiWaySyntenyDisplay',
rows: { sort: ['GCF_000346465.2', 'poplar'], kept: ['GCF_000346465.2', 'poplar', 'citrus'] },
}Config slots
A setting written to it names members one by one: a member left out stays as it is, and null resets one. 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 |
|---|---|
sortstringArray of strings or numbers = [] |
The lanes that stack first, by assembly name, in this order; the rest follow densest-first. |
labelsstringMap = {} |
A label drawn for a lane in place of its assembly name, by assembly name. Where the lane labels draw is labels.lanes. |
keptstringArray of strings or numbers = [] |
The lanes drawn, by assembly name: it selects rather than narrows, replacing the track's lanes and able to add a lane the track does not configure. Empty draws the track's lanes, or every lane where it configures none. |