DreamLake
Browse docs

Panels and views

Bind a source's fields to a view: cameras in videoStack, joint traces in lineChart, or labeled intervals in timeline. This is the sources/panels API, separate from Dataset views.

Built-in views

ViewField kindsResult
videoStackvideo, image, explicitly selected fileMedia tiles with shared time.
frameStackframesCamera sequences loaded at the cursor time.
lineChartseriesNumeric traces selected by feature or dimension.
timelinecues, supported annotation filesLabeled time intervals.
fieldsCataloganyField names, kinds and metadata.
placeholder3dpose3d, pointcloudA description of the available 3D data.

gridLayout groups panels; autoLayout chooses them from the catalog. placeholder3d shows metadata only. Use Dataset views or the 3D component for interactive scenes.

videoStack

Select cameras with fields. A wildcard is matched against the field catalog.

yaml
- view: videoStack
  source: ep
  fields: ["observation.images.*"]
  columns: 2
  gap: 6
  showRecTimestamp: true
  showLive: false
  showLabel: true
  showResolution: true
  overlays:
    - { field: "*joints.json", format: handJoints, on: observation.images.ego }
    - { field: "*subtasks*.json", format: subtasks }

Overlays select annotation files in the same source. Supported formats are handJoints, subtasks and raw; see their data shapes. on limits an overlay to a matching camera. This folder example shows cameras sharing a cursor:

Loading fields…
Code FilesystemFolderSpec.tsx

frameStack

Uses a frame payload's frameAt(index) function to load images for the cursor time. Select fields and configure the grid:

yaml
- view: frameStack
  source: ep
  fields: ["camera*"]
  columns: 2
  gap: 6

See the UMI and egocentric examples for source formats that provide frame sequences.

lineChart

Use series to style each trace and select dimensions. A complete feature selects all its columns; [feature, dimension] selects one. Dimension patterns such as [observation.state, "left_*"] select a group.

yaml
- view: lineChart
  source: ep
  title: Left waist
  caption: Joint angle
  lineWidth: 2
  height: 240
  yRange: [-2, 2]
  unitHint: Command and observation in radians
  maxPoints: 2000
  series:
    - { field: [action, left_waist], label: Command }
    - {
        field: [observation.state, left_waist],
        label: Observation,
        dash: "3 2.4",
      }
Loading fields…
Code LineChartSpec.tsx

fields: [action, observation.state] is the shorter form when each feature should use automatic styling. Series options are label, color, dash, width, opacity and ghost. Widths are non-scaling CSS pixels: the chart defaults to 2px, and a series width overrides the panel's lineWidth. Keep references readable with dash and opacity. activeLineWidth has the same floor behavior as the component API; it changes emphasis styling but does not enable pointer identification itself.

Panel optionDefaultMeaning
lineWidth2Default trace width in CSS pixels; overridden by series width.
activeLineWidthbase × 1.65Active width, never thinner than the resolved base. Zero base widths stay hidden.
height180Number of pixels or a CSS length in grid layout.
yRangeautomaticExplicit numeric domain.
title, caption, unitHintomittedChart labels.
showMidlinechart defaultControls the chart's central gridline.
disabledfalseDisplays the unavailable-signal state.
maxPoints2000Sampling hint passed to the adapter.
timeRangeomitted{ from, to } read window passed to the adapter.

This wrapper forwards the options above. Other EpisodeLineChart props are not automatically schema options; use the component directly when you need those controls.

timeline

Bind cue fields with tracks. An annotation file can instead specify format: subtasks to convert labeled intervals into blocks.

yaml
- view: timeline
  source: ep
  tracks:
    - { field: task_index, label: Task }
    - { field: "*subtasks*.json", format: subtasks, label: Subtasks }
  trackRowHeight: 28
  minZoom: 1
  maxZoom: 20
Loading fields…
Code TimelineSpec.tsx

fieldsCatalog

Use the catalog to inspect field references, kinds and dimension names before writing bindings.

yaml
- view: fieldsCatalog
  source: ep
  title: Available fields
Loading fields…
Code FieldsCatalogSpec.tsx

Writing your own panel

Implement a view with the catalog, bound reader, shared cursor and panel config:

ts
interface View {
  name: string;
  kinds: string[];
  rows?: boolean;
  component: ComponentType<ViewProps>;
}

interface ViewProps {
  fields: Field[];
  read: (ref: string, query?: ReadQuery) => Promise<Payload>;
  timeline?: Timeline | null;
  cursor?: TimeCursor;
  config: Record<string, unknown>;
}

This view lists numeric field names without reading their values:

tsx
import { registerView } from "@dreamlake/viz/schema-viz";
import type { View, ViewProps } from "@dreamlake/viz/schema-viz";

function SignalList({ fields }: ViewProps) {
  return (
    <ul>
      {fields
        .filter((field) => field.kind === "series")
        .map((field) => (
          <li key={field.ref}>{field.label ?? field.ref}</li>
        ))}
    </ul>
  );
}

const signalList: View = {
  name: "signalList",
  kinds: ["series"],
  component: SignalList,
};

registerView(signalList);

Select it with { view: "signalList", source: "ep" }. For data, call read(ref, { timeRange, maxPoints }) and handle loading/errors. For shared interaction, use cursor.time, cursor.setHover(time), cursor.setHover(null) and cursor.seek(time).

Views may also be supplied through extensions.views; see registration behavior.

Auto-layout

Omit panels, or add { view: autoLayout, source: ep }, to generate the following panels from a source's catalog:

  1. Video and image fields in one videoStack.
  2. Frame sequences in one frameStack.
  3. Pose and point-cloud fields in a placeholder3d panel.
  4. Cue fields in one timeline.
  5. One lineChart per numeric field, grouped in a grid when there is more than one.

Opaque file fields are omitted from this default. Select them explicitly when they belong in a panel.

Auto-laying out…
Code AutoLayoutSpec.tsx