DotplotDisplay

Auto-generated from the config schema in the source — see the config guide for concepts. Provided by the dotplot-view plugin. View source.

Example usage#

The dot-plot rendering of a SyntenyTrack, for use inside a DotplotView (rather than the two-row LinearSyntenyDisplay or the plain-LGV LGVSyntenyDisplay) — same track config, different display type:

{
  type: 'SyntenyTrack',
  trackId: 'hg38_vs_mm10',
  name: 'hg38 vs mm10',
  assemblyNames: ['hg38', 'mm10'],
  adapter: {
    type: 'PAFAdapter',
    uri: 'https://example.com/hg38_vs_mm10.paf',
    queryAssembly: 'hg38',
    targetAssembly: 'mm10',
  },
  displays: [
    {
      type: 'DotplotDisplay',
      displayId: 'hg38_vs_mm10-DotplotDisplay',
    },
  ],
}

Overview#

Draws a SyntenyTrack as a dot plot inside a DotplotView.

DotplotDisplay - Identifier#

Every DotplotDisplay has a unique displayId, a required top-level field that identifies it (not one of the config slots below).

Related links#

• Adapter: BlastTabularAdapter
• Adapter: ChainAdapter
• Adapter: DeltaAdapter
• Adapter: MashMapAdapter
• Adapter: MCScanAnchorsAdapter
• Adapter: MCScanBlocksAdapter
• Adapter: MCScanSimpleAnchorsAdapter
• Adapter: MultiGenomeIndexedPAFAdapter
• Adapter: MultiGenomePAFAdapter
• Adapter: MultiPairwiseSyntenyAdapter
• Adapter: PAFAdapter
• Adapter: PairwiseIndexedPAFAdapter
• State model: runtime API
• User guide: Dotplot view
• Config guide: Tracks
• Developer guide: Custom track and display types

Retired keys#

An older config may still write these. Each loads without an error, and jbrowse validate reports it as stale.