Class HeatmapScrollingGridSeriesIntensityValues

Series class for visualizing a Heatmap Grid, with API for pushing data in a scrolling manner (append new data on top of existing data).

HeatmapScrollingGridSeriesIntensityValues is optimized for massive amounts of data - here are some reference specs on average PC to give an idea:

  • Scrolling Heatmap Chart with 2 million incoming data points per second (rows: 2048, 1000 columns/s) runs consistently and smoothly with 60 FPS and no stuttering. CPU usage stays easily below 40%.
  • Scrolling Heatmap Chart with 8 million incoming data points per second (rows: 4096, 2000 columns/s) runs consistently and smoothly with 60 FPS and minor stuttering.

HeatmapScrollingGridSeriesIntensityValues max data amount is entirely restricted by the client hardware RAM and more specifically amount of RAM usable by the context running LightningChart JS. If performance suddenly plummets at some approximate data threshold, then it is likely that there is not enough RAM available. Use data cleaning configuration and suitable Axis intervals to adjust to your hardware limitations.

Each cell of the heatmap grid is associated with a numeric intensity value, which can be used in conjuction with a Color look up table (LUT).

Created with addHeatmapScrollingGridSeries.

Frequently used API:

Hierarchy

Properties

_isCursorEnabled: boolean = true

Active state of Cursor

axisX: Axis
axisY: Axis
scale: LinearScaleXY

Scale of the series

Methods

  • Push a Matrix of intensity values into the Heatmap grid. Each value describes one cell in the grid.

    Order of data is selected when creating the series;

    scrollDimension: 'columns' ->

     [
    [
    0, // Intensity value column = 0, row = 0
    0, // Intensity value column = 0, row = 1
    0, // Intensity value column = 0, row = n
    ],
    [
    0, // Intensity value column = 1, row = 0
    0, // Intensity value column = 1, row = 1
    0, // Intensity value column = 1, row = n
    ],
    ]

    scrollDimension: 'rows' ->

     [
    [
    0, // Intensity value row = 0, column = 0
    0, // Intensity value row = 0, column = 1
    0, // Intensity value row = 0, column = n
    ],
    [
    0, // Intensity value row = 1, column = 0
    0, // Intensity value row = 1, column = 1
    0, // Intensity value row = 1, column = n
    ],
    ]

    Example usage:

     // Create x-scrolling intensity heatmap.
    const series = ChartXY.addHeatmapScrollingGridSeries({
    heatmapDataType: 'intensity',
    scrollDimension: 'columns',
    resolution: 5,
    start: { x: 0, y: 0 },
    step: { x: 1, y: 1 },
    })

    // Push a column into heatmap.
    series.addIntensityValues([
    [0, 10, 0, 20, 0]
    ])

    invalidateIntensityValues can trigger warnings when used controversially. In production applications, these can be controlled with warnings.

    Returns

    Object itself for fluent interface.

    Parameters

    • intensityValues: number[][]

      Matrix of intensity values - Each array represents a column or row, and each number represents a cell in the grid.

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Permanently destroy the component.

    To fully allow Garbage-Collection to free the resources used by the component, make sure to remove any references to the component and its children in application code.

    let chart = ...ChartXY()
    let axisX = chart.getDefaultAxisX()
    // Dispose Chart, and remove all references so that they can be garbage-collected.
    chart.dispose()
    chart = undefined
    axisX = undefined

    Returns

    Object itself for fluent interface

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Get whether series is taken into account with automatic scrolling and fitting of attached axes.

    By default, this is true for all series.

    Returns

    true default, axes will take series into account in scrolling and fitting operations. false, axes will ignore series boundaries.

    Returns boolean

  • Get theme effect enabled on component or disabled.

    A theme can specify an Effect to add extra visual oomph to chart applications, like Glow effects around data or other components. Whether this effect is drawn above a particular component can be configured using the setEffect method.

     // Example, disable theme effect from a particular component.
    Component.setEffect(false)

    For the most part, theme effects are enabled by default on most components.

    Theme effect is configured with effect property.

    Returns

    Boolean that describes whether drawing the theme effect is enabled around the component or not.

    Returns boolean

  • Get state of component highlighting.

    In case highlight animations are enabled, this method returns the unanimated highlight value.

    Returns

    Number between 0 and 1, where 1 is fully highlighted.

    Returns number

  • Get boolean flag for whether object should highlight on mouse hover

    Returns

    Boolean for if object should highlight on mouse hover or not.

    Returns boolean

  • Get boolean flag for whether object is currently under mouse or not

    Returns

    Boolean for is object under mouse currently

    Returns boolean

  • Get mouse interactions enabled or disabled. Disabled mouse-interactions will naturally prevent mouse-driven highlighting from ever happening.

    Returns

    Mouse interactions state

    Returns boolean

  • Get number of samples that have been pushed into the scrolling heatmap series. For empty heatmap this will be 0.

    Returns

    Number of samples in the heatmap.

    Returns number

  • Get element visibility.

    Returns

    true when element is set to be visible and false otherwise.

    Returns boolean

  • Invalidate existing and/or add new intensity values in the Heatmap grid. The location along scrolling dimension is identified by a sample index.

    Sample index 0 would reference the first sample in the heatmap, whereas 1 the second sample. This allows, for example, the modification of previously pushed heatmap samples.

    This method is also capable of adding new samples into the heatmap, which happens if the sample index exceeds the currently existing sample count (this can be received with getSampleCount method).

    If this method is used to push new samples into the heatmap in a manner where gaps form between the new samples and previous ones, the gaps are automatically filled by duplicating the previous last heatmap sample!

     // Example, modify last sample pushed to heatmap
    heatmapSeries.invalidateIntensityValues({
    iSample: heatmapSeries.getSampleCount() - 1,
    values: [[0, 0, 0, 0, 0]]
    })
     // Example, update 5 samples starting at sample index 2
    heatmapSeries.invalidateIntensityValues({
    iSample: 2,
    values: [
    [0, 0, 0],
    [0, 0, 0],
    [0, 0, 0],
    [0, 0, 0],
    [0, 0, 0],
    ]
    })

    Returns

    Object itself.

    Parameters

    • arg: {
          iSample: number;
          values: number[][];
      }

      Object with sample index and intensity values parameters.

      • iSample: number
      • values: number[][]

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Remove event listener from dispose event.

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Unsubscribe from Highlight object event. This is called whenever an object is highlighted

    Returns

    True if the unsubscription was successful.

    Parameters

    • token: Token

      Token that was received when subscribing to the event.

    Returns boolean

  • Remove event listener from Mouse Click Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Double Click Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Down Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Drag Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Drag Start Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Drag Stop Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Enter Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Leave Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Move Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Up Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Mouse Wheel Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Touch End Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Touch Move Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Remove event listener from Touch Start Event

    Returns

    True if the listener is successfully removed and false if it is not found

    Parameters

    • token: Token

      Token of event listener which has to be removed

    Returns boolean

  • Set whether series is taken into account with automatic scrolling and fitting of attached axes.

    By default, this is true for all series.

    By setting this to false, any series can be removed from axis scrolling/fitting.

     // Example syntax, remove series from automatic scrolling / fitting.
    LineSeries.setAutoScrollingEnabled(false)

    Returns

    Object itself for fluent interface.

    Parameters

    • enabled: boolean

      true default, axes will take series into account in scrolling and fitting operations. false, axes will ignore series boundaries.

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Disable automatic data cleaning.

     // Example syntax, disable data cleaning.
    series.setDataCleaning(undefined)

    Returns

    Object itself for fluent interface.

    Parameters

    • arg: undefined

      Data cleaning configuration.

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Enable automatic data cleaning by minDataPointCount configuration.

    Specifying minDataPointCount enables lazy cleaning of data that is outside view as long as the remaining data amount doesn't go below the configured threshold.

     // Example syntax for specifying minDataPointCount
    series.setDataCleaning({ minDataPointCount: 10000 })

    Usage of minDataPointCount is recommended in most common applications that require automatic data cleaning. The actual value is often not very particular, just setting it above 0 to enable it is usually enough (lazy data cleaning of out of view data).

     // Example, enable lazy data cleaning of out of view data.
    series.setDataCleaning({ minDataPointCount: 1 })

    Returns

    Object itself for fluent interface.

    Parameters

    • arg: {
          minDataPointCount: undefined | number;
      }

      Data cleaning configuration.

      • minDataPointCount: undefined | number

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Enable automatic data cleaning by maxDataPointCount configuration.

    Specifying maxDataPointCount results in data cleaning always happening exactly when total data amount exceeds the supplied threshold.

     // Example syntax for specifying maxDataPointCount
    series.setDataCleaning({ maxDataPointCount: 10000 })

    maxDataPointCount is usually used in memory limited applications to prevent running out of memory.

    maxDataPointCount is currently only supported by only select series:

    If the feature receives good support and usage from the user base, it might be expanded to all series types in a future release.

    Returns

    Object itself for fluent interface.

    Parameters

    • arg: {
          maxDataPointCount: undefined | number;
      }

      Data cleaning configuration.

      • maxDataPointCount: undefined | number

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Configure draw order of the series.

    The drawing order of series inside same chart can be configured by configuring their seriesDrawOrderIndex. This is a simple number that indicates which series is drawn first, and which last.

    The values can be any JS number, even a decimal. Higher number results in series being drawn closer to the top.

    By default, each series is assigned a running counter starting from 0 and increasing by 1 for each series.

        // Example, create 2 series and configure them to be drawn in reverse order.
    const series1 = ChartXY.addLineSeries()
    .setDrawOrder({ seriesDrawOrderIndex: 1 })
    const series2 = ChartXY.addLineSeries()
    .setDrawOrder({ seriesDrawOrderIndex: 0 })
        // Example, ensure a series is drawn above other series.
    SeriesXY.setDrawOrder({ seriesDrawOrderIndex: 1000 })

    Returns

    Object itself.

    Parameters

    • arg: {
          seriesDrawOrderIndex: number;
      }

      Object with seriesDrawOrderIndex property.

      • seriesDrawOrderIndex: number

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Set theme effect enabled on component or disabled.

    A theme can specify an Effect to add extra visual oomph to chart applications, like Glow effects around data or other components. Whether this effect is drawn above a particular component can be configured using the setEffect method.

     // Example, disable theme effect from a particular component.
    Component.setEffect(false)

    For the most part, theme effects are enabled by default on most components.

    Theme effect is configured with effect property.

    Returns

    Object itself.

    Parameters

    • enabled: boolean

      Theme effect enabled

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Set fill style of heatmap series.

    Supported fill styles:

    PalettedFill:

    Colors heatmap fill by looking color up from LUT based on heatmap intensity values.

     // Example, color look up by intensity values.
    heatmapSeries.setFillStyle(
    new PalettedFill({
    lut: new LUT({
    steps: [
    { value: 0, color: ColorCSS('red') },
    { value: 20, color: ColorCSS('blue') },
    ],
    interpolate: true,
    }),
    }),
    )

    Intensity values are defined when data is pushed in with addIntensityValues method.

    Note, Heatmap doesn't currently support color (fallback color).

    • SolidFill:

    Solid color for all heatmap cells. Supported for debugging purposes mainly.

    emptyFill:

    Disables heatmap fill.

     // Example, hide heatmap fill and show wireframe.
    heatmapSeries
    .setFillStyle(emptyFill)
    .setWireframeStyle(new SolidFill({ color: ColorRGBA(255, 0, 0) }))

    Returns

    Object itself for fluent interface.

    Parameters

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Set state of component highlighting.

     // Example usage

    component.setHighlight(true)

    component.setHighlight(0.5)

    If highlight animations are enabled (which is true by default), the transition will be animated. As long as the component is highlighted, the active highlight intensity will be animated continuously between 0 and the configured value. Highlight animations can be disabled with setAnimationHighlight

    Returns

    Object itself

    Parameters

    • highlight: number | boolean

      Boolean or number between 0 and 1, where 1 is fully highlighted.

    Returns HeatmapScrollingGridSeriesIntensityValues

  • Method for solving the nearest data point from a given coordinate on screen.

     // Example usage, from mouse move event.
    ChartXY.onSeriesBackgroundMouseMove((_, event) => {
    const result = LineSeries.solveNearestFromScreen(event)
    })
     // Example usage, arbitrary coordinate on client coordinate system.
    const result = LineSeries.solveNearestFromScreen({ clientX: 100, clientY: 200 })

    Translating coordinates from other coordinate systems is also possible, see translateCoordinate.

    Returns

    undefined or data structure with solve result information that can also be used for positioning custom cursors.

    Parameters

    • location: CoordinateClient

      Location in HTML client coordinates.

    • Optional interpolate: boolean

    Returns undefined | CursorPoint<Point>

  • Deprecated

    This method signature is deprecated since v4.2.0. Supply CoordinateClient instead.

    Parameters

    • location: Point
    • Optional interpolate: boolean

    Returns undefined | CursorPoint<Point>